We simply ask that you be innovative without mistakes while working as a team to achieve individual performance goals.

Engineering tradeoffs and stupidity are often indistinguishable if you're unaware of the tradeoffs.

What positive effects do you hope to encourage by holding people accountable for predicted key results? What negative effects do you hope to discourage? What perverse incentives do you create in the process?

TECH RECRUITER TIP: Especially in a small town like Wellington, don't try to talk up your client's culture by talking smack about the culture dip at another org. There's zero up side for you.

To start shedding unattainable software standards, let's: 🛑 Stop thinking of software as homogeneously represented by a small number of unrepresentative companies 🗯 Start being more honest about "real software process" 🛠 Demand more solutions to the real problems!! end/

90% of my job as a senior engineer is giving others the confidence to go with the less-impressive-but-simpler approach.

It looks like Phoenix Framework and Fly.io are shaping up to be a really great combo, the app experience is super responsive. Also awesome to have a really good Liveview example repo: github.com/fly-apps/live_… Kudos Chris McCord and co-conspirators!

Upgrade your Rails apps friends, this one is an important security patch.

🤯 This is just mind-blowing 🤯 ServiceMesh evolution towards Sidecarless with eBPF 🧵

FYI Today's a good day to take (another) look at Nomad 👍 Hashicorp continues to deliver the goods

GitHub supports Hex security advisories now! #MyElixirStatus github.blog/2022-06-27-git…

Verified routes coming soon to a phoenix 1.7 project near you. Thanks to Jason Stiebs for complaining at the right time, and José Valim for the idea! This feature is 🔥🔥🔥. I love it so much!

The thing most hot takes about the "hot new JS infra company job ad" that's going around now is that you only get so many takes at building a good org culture. People are right in saying it's bad for engineers, but it's also a really terrible deal for leadership in the long run.

Today I met with officials in Helsinki, which has had a ~75% drop in road deaths over the last thirty years (including recent years with no ped/cyclist deaths at all). Me: “How much of a role has IT played in reducing crashes?” City official: “Zero. We simply slowed down cars.”

This generalises more than you'd think. I know a few technical decision-makers who have gone to battle with their CFOs to avoid "A once-in-a-lifetime deal on hosting" entirely for this reason.

Its been like a decade but I still wake up some days (like today) and look around at the web we've built and can't believe we effectively lost RSS. To check if my fav tech writers have content I now have to check multiple sites with a non-linear timeline and no inbox.

Oh dear… The extract is pretty damning. AI tooling is getting better at an astounding rate but we’re still in the “teaching computers to copy/ paste insecure GPL code” phase. Buyer beware.