DEV Community

Discussion on: 5 Frustrating Developer Pet Peeves and How to Deal With Them

Collapse
 
resmall profile image
Tiago R. Lammers

It resonates to me. The thing that it really comes down to is this way of thinking of everything as urgent and necessary. Code gets done as an MVP, except you will never have time to fix that code or put tests on it. The MVP isn't actually an MVP but the whole product, it's the BIG BANG release.

What seems difficult for most people to understand, is to think of a product, breaking it into small subsets of functionality. Thinking in user journeys instead of the "whole solution". This is what makes most sense to me.
I really dislike developing lots of features for weeks while nobody is using it in production. I get no feedback from users, plus there might be things broken and we will only find that out on the release day. This is the kind of thing that blows back directly into developers faces.

With time and experience I have learned that when using this "waterfall" process, that is usually disguised as agile, time is being wasted into features that nobody will ever use.