3 ms·
If your developer labor force is interchangeable (you can fire or replace someone easily) then you don't have to care about DX. If your labor force is not so i
by throwawaymaths 2y ago
If your developer labor force is interchangeable (you can fire or replace someone easily) then you don't have to care about DX. If your labor force is not so interchangeable, don't copy the practices of places where that is the case.
- praptak 2y agoIf you can replace someone and not pay a huge ramp up cost then your DX is already great.
- Kirth 2y agoHas anyone ever seen such a place in practice? what were they doing right? I've seen this claimed a few times before but it was always wilful blindness + not measuring anything related.
- cjk2 2y agoOur labour force and developer experience is like a rusty bucket. If we hire any old person quick enough it'll replace the pissed off people leaking out the holes!
- softwaredoug 2y agoI disagree. Create good developer experience, and developers can be "interchangeable" (work on each other's code more easily). Poor developer experience and you'll ensure only that team has any clue how to run their crazy build tools + dev env.
- slowmovintarget 2y agoGood developer experience doesn't make developers interchangeable. It reduces the roadblocks (cognitive, technical, and aesthetic) that makes a developer's job harder, which means those same developers can get their job done more quickly. In product-speak, it makes it more likely your product is adopted broadly. Microsoft used to understand this. Visual Studio, VS Code, and the Linux subsystem for Windows are some of the outcomes of this understanding.
- marcosdumay 2y agoAs a hint, if you think labor in your company is interchangeable, odds are that you are just a bad manager. (Also, notice that I didn't write "knowledgeable" or "development" or any other qualifier there.)
- throwawaymaths 2y agoYes, that's the point.