3 ms·
DevEx Principles: Minimize switching contexts
- nh23423fefe 4y agoYeah, the AI fingers are terrible. More on topic: I try to push this concept at work all the time, but it gets no traction. No one actually cares about devex at work, even though all developers complain about it unknowingly. We essentially have 3 kinds of intake for dev work. Something is broken in prod, something is being developed in qa, or something is being planned/started. This is pretty similar to all the places I've worked. Every one of those intakes is broken. Prod flow is pure slack panic, mass zoom calls, and then demanding RCAs which are immediately memory holed. Development in qa is black box frontend testing producing jira tickets like, "this seems wrong can you investigate?" the loop is not tight or efficient. Upfront everything is under-designed and cross component functionality is never ensured. Its just chaos. I just spent 30 minutes on a call about whether we should have a single point of contact or the whole team, but meanwhile no one knows what we are building. Fake accountability is more important than clarity. Because when "someone" is accountable then you can blame. But actually creating understanding and making developers falling pit of success is never on the radar.