↓ Skip to main content

·139 words

A handy overview of how to hire for developer tooling and how to improve the developer experience at companies from a perspective that recognizes these are socio-technical issues but also needs to get stuff done.

What you’re looking for, I think, is someone who can take “developer experience”and push that forward holistically by whatever way is necessary. The hardest things they will have to do is gain the trust of the entire engineering organization, buy-in for their approach, and deliver perceived value and improvements.

This role is truly a Sociotechnical Engineer, in every sense of the term; they will expose the weaknesses of your company in ways you are not prepared for, and they will challenge the status quo in ways that are painful. Embrace it. Be prepared to grow as much, if not more, than they do.

https://hazelweakly.me/blog/so-you-want-to-hire-for-developer-tooling/#so-you-want-to-hire-for-developer-tooling

Alper Cugun
Author
Alper Cugun

Related

·36 words
I prefer to use contributing factors over the concept of a “root cause” and if people believe an incident has a single cause, usually that also means that they’re not very serious about reliability engineering.

·43 words
We’re seeing a bunch of these posts come around serverless around the time that we too are reconsidering our investment in this area. Lambda has a lot of operational benefits but at larger scales the developer experience just does not keep up.

·35 words
A long post that builds up to async Rust from the ground up and explains how the various bits and pieces work. Really quite the tour de force with a simple conclusion: use Tokio.