PacifyFish

I made the switch over to “customer facing tech savvy person.” Think Sales Engineer, Solutions Architect, Technical Account Manager.

Pays slightly less (until you get 5+ years experience, then tends to catch up if you’re good) but my lord it’s so much less taxing on your brain.

You’ll realize that most customer facing folks may be charismatic, but they aren’t very organized or willing to learn on the job. It’s easy to be top 1% while coming in at 9 and leaving at 5, with plenty of time and mental energy leftover for whatever hobbies you want to pursue. Including programming.

Worth checking out if you feel comfortable communicating verbally for a living.

If you want to chat, feel free to reach out at evan dot hellmuth at gmail dot com

The Wikipedia article states that it’s a cover for a hat, not meant to be worn.

Psychological safety is 10% job security and 90% how comfortable you feel with the people you work with. Simple to understand, hard to make happen - you need to hire well.

How do you manage dev vs prod instances with sequelize? Specifically, do you use migrations for your local dB or just force sync it?

Keep in mind the lockdown is meant to slow spread so the healthcare system doesn't get overloaded, not to stop it.

It is successful in this respect, and IMO a healthy balance of economic slowdown and death toll. We'll probably start reopening (hopefully in stages, so we can monitor impact) in the next ~3 weeks.

I consulted for a company named FlowCrypt last year. Best email encryption UX of any I've seen. Open source and free-for-most business model.

Highly recommend for personal use.

I'd like the power grid staffers to keep doing their jobs thanks very much

At the volume and frequency they need to process, it probably makes sense to do something more complicated than MySQL...

Bitcoin

Here’s one data point: I would not buy a book with thousands of business one-liners such as “know your customer”

What did the author use to make the charts?

Maybe I've missed the boat, but what's the big deal about collecting telemetry?

You already trust Gitlab with everything you store in Gitlab, like source code, which is presumably much more sensitive than the number of times you loaded a page or clicked on a button or whatever.

Is it because the data would be stored with a third party, and you don't trust that third party? If Gitlab trusts the third party, and they're giving you the option to NOT trust the third party and only trust Gitlab, what's the issue?

Why not do a slow rollout, starting at maybe 5% of product. Then you can catch and fix deficiencies without compromising your entire production line, and ratchet up to 10, 15, ... 100% as you gain confidence in the model?

Link? I'm interested in using something like this at work.