cmpaul

``` GET https://mysite.com/?query=all+the+secrets ```

This is awesome. Where do you get this music stream?

Great example of how LLMs are eliminating/simplifying giant swathes of complex tech.

I would love to use this in a project if it could also caption embedded images to produce something for RAG...

Take my money.

What is the magnesium glycinate for?

YES! I worked on the FedEx Enhanced SuperTracker software from 1999-2006, which I believe is the "Version II" you're referencing. The core software was still written in Forth, but we rebuilt the package routing logic in in C, which might be what you're referring to. Very curious to know how you are familiar with all the history, did you work there or at Forth, Inc?

Bingo

Technical aspects aside (and congrats on the achievement!), I love the implications of the author's "Aside":

1. An otherwise inconvenient situation (snowpocalypse) was turned into a learning opportunity. I would've probably turned it into a Netflix binge.

2. People took the time to detail the CPU design in a document. I'm always looking for examples showing the benefits of documenting design (I'm an EM) and it's rare to find one that changes someone's life trajectory. :)

Been using this since my MBP webcam died. Works well, doesn't seem to lag much.

Agreed, could probably have avoided giving away the plot here. The book is definitely worth the read!

Just accept that regret is part of all lives.

So true, and so hard to do.

The invertebrates that live there, likewise, are adapted to these temperatures and fare poorly outside them; bugs cannot regulate their internal heat.

This makes me think that the insects which do survive will be better adapted to the higher temperatures. Hopefully the change is slow enough they have time to adapt. And this is nothing to say about the impact of that adaptation time on other species...

Looking for work? :)

https://jobs.lever.co/hellosign/39ea6c41-8ff8-4c93-b0fd-4a62...

The "short-term car rental hubs... where people who do not own cars can pick up a vehicle and drive for Lyft to earn money" is a nice idea in the short-term. I still think Uber has the right idea long-term with a completely autonomous fleet, but once those hit the market, there will still be a pretty large demand for NON-autonomous vehicles -- take my parents, for instance, who refuse to get into a car not driven by a human.

This feels a little like a troll, but I'll bite. :)

I'm new to management so I'll be the first to admit that I'm not great at it. I do wish I'd had someone to tell me some of these things when I first started, so you could think of this as advice to my younger self. YMMV.

As for whether asking tough questions makes people feel safe, I'd say, "... maybe?" I can think of hard questions that would certainly make me feel less safe. Two things: 1. Asking the question I lead with got me some great info, so I'm going to continue trying this; 2. I'd want to encourage people on my team to feel able to do the same, so I look at this as leading by example.

Author here. The answers were beside the point. The thought I was attempting (perhaps poorly) to convey was that I asked something that felt risky and was rewarded. This was encouraging. What if the rest of my team felt as open to ask questions in which the answer might raise some eyebrows or incur flat out ridicule or judgement from teammates?

Why celebrate hard work just for the sake of work?

Why do hard work at all? My answer would be to risk building something great. I doubt anyone wants to do hard work for the sake of it. Building a culture that rewards honest effort would encourage the same hard work in the future despite risks of failure -- though admittedly it's easy to go overboard in either direction! Use your best judgement here.

Author here. In an attempt at being pithy, this might have been worded poorly. My experience is that rewarding success is the standard approach in most industries, but teams that become accustomed to only being rewarded when they succeed can develop an aversion to failure (and therefore taking risks).

I realize it might also be easy to extrapolate this out to always rewarding a team, no matter what, and I don't want to suggest that in all circumstances... you know if your team put forth an honest effort and should be rewarded despite building something that fails. Definitely don't mean for this to be a hard and fast rule, but more of a tip for encouraging a smart, hard-working team to feel safer taking risks.

I manage the engineering team at HelloSign (YC11) and wrote a little response to Google's team success study that came out a few weeks ago. It tries to answer the question: How the heck do you foster psychological safety in the first place?

HelloSign | San Francisco | React & Symfony PHP | YC11

- Senior Backend Engineer: https://boards.greenhouse.io/hellosign/jobs/88292

- Engineering Manager: https://boards.greenhouse.io/hellosign/jobs/94411

- Lead QA Engineer: https://boards.greenhouse.io/hellosign/jobs/69005

HelloSign has seen tremendous growth over the past two years, primarily through word-of-mouth, and we are now focusing on building out an API that enables anyone to integrate eSignatures directly into their own website. We are funded by some of the top investors in the valley, including Y Combinator, Greylock, Google Ventures, and US Venture Partners. Our goal is simply to be the way people sign documents everywhere.

We are centrally located in downtown San Francisco by Union Square. Currently at 40 employees, we are growing the company deliberately, with an eye towards maintaining a culture that values lifestyle, fun, and continuous improvement (we were recently awarded the Hirepalooza Culture Award for Lifestyle in early 2015!).

Be sure to check us out on Glassdoor too.

HelloSign (YC11) | San Francisco, CA | Remote | Part Time & Full

Hey HackerNews'ers - Chris here with the engineering team at HelloSign. We're looking to fill 3 technical roles this month:

1. Lead QA Engineer: https://boards.greenhouse.io/hellosign/jobs/69005#.Vg1f5BNVh...

2. Senior Platform Engineer: https://boards.greenhouse.io/hellosign/jobs/88292#.Vg1f5BNVh...

3. Engineering Manager: https://boards.greenhouse.io/hellosign/jobs/94411#.Vg1f5RNVh...

More about us:

HelloSign has seen tremendous growth over the past two years, primarily through word-of-mouth, and we are now focusing on building out an API that enables anyone to integrate eSignatures directly into their own website. We are funded by some of the top investors in the valley, including Y Combinator, Greylock, Google Ventures, and US Venture Partners. Our goal is simply to be the way people sign documents everywhere.

We are centrally located in downtown San Francisco by Union Square. Currently at 40 employees, we are growing the company deliberately, with an eye towards maintaining a culture that values lifestyle, fun, and continuous improvement (we were recently awarded the Hirepalooza Culture Award for Lifestyle in early 2015!).

Forth was my first programming language for work from 1999-2004 at FedEx, developing the software used by the courier scanning device the Enhanced SuperTracker (EST) -- which was used in production between 1987 and 2007... 20 years! I still look back fondly on it for battle-hardening me on recursion and the function stack. I still marvel at the ability of the language to "fold in" on itself when compiled, resulting in a miniscule binary footprint. Also, since you define your own "words" (or functions), it supports a DSL approach to coding... no syntax to learn, you write your own!

One of my favorite descriptions of Forth:

"There is no syntax, no redundancy, no typing. There are no errors that can be detected. Forth uses postfix, there are no parentheses. No indentation. Comments are deferred to the documentation. No hooks, no compatibility. Words are never hyphenated. There's no heirarchy. No files. No operating system."

http://www.colorforth.com/1percent.html

EDIT: I survived and currently work at a YC company and do not have a neck-beard.

HelloSign.com | San Francisco, CA

https://www.hellosign.com/info/jobs

HelloSign is a leading provider of eSignatures. We let users sign documents when, where, and how they want, all with the most intuitive user-interface in the industry. It is our mission to make our customers awesome and the same time create an awesome team at HelloSign!

We're hiring for the following positions:

1. DevOps Engineer (U.S. Remote Okay) - https://boards.greenhouse.io/hellosign/jobs/73138#.VZRyDRNVi...

2. Lead QA Engineer - https://boards.greenhouse.io/hellosign/jobs/69005#.VZRyDRNVi...

3. Full-stack Software Engineer - https://boards.greenhouse.io/hellosign/jobs/35126#.VZRyDRNVi...

p.s. Check us out on Glassdoor too!

1. Open JS Console. 2. Copy and paste the following, but don't submit: var n = {seconds: $("#thebutton-timer").val(),prev_seconds: r.thebutton._msgSecondsLeft,tick_time: r.thebutton._tickTime,tick_mac: r.thebutton._tickMac}; 3. Wait for the timer to hit a time you like and hit ENTER to record the timer seconds and tic MAC. 4. Repeat until you're happy with the score. 5. Paste the following into your console and hit ENTER: $.request("press_button", n, function(e) { console.log(e) });

HelloSign.com - https://www.hellosign.com/ - San Francisco, CA

- API Evangelist: https://boards.greenhouse.io/hellosign/jobs/5726#.VRxj0JPF95...

- API Tech Support: https://boards.greenhouse.io/hellosign/jobs/53830#.VRxj0pPF9...

The latest in eSignatures: carrier pigeons. http://info.hellosign.com/avian

Time for Murakami Bingo:

http://www.nytimes.com/interactive/2012/06/01/books/review/0...

I know it's art, but I'm having trouble explaining "Torso of Venus" to my coworkers... :)

The handset used for "call" icons should probably be rethought soon too.

Maybe it's because I'm getting older, but no programming font comes close to Monaco in terms of clarity and character balance and spacing (vertically and horizontally).

Ultimately it comes down to being able to patterns quickly in the code. You can train yourself to do this with any font.