Dev: boss, there are some abnormalities and confusion in the client's specifications.

Boss: So?

Dev: Shouldn't we get clear about them and then start coding?

Boss: No need. We assume and code. Then show them to our clients and then ask for their opinions. We will change again according to their opinion.

Dev: ..

A few months later....

Dev: *seeing so many specifications change and realizing now have to refactor a lot of codes* , FML.

Feels bad dude! Welcome to devRant

@dontPanic hey! Thanks. What do you think a dev should do when he is faced with such tough frustrating situation?

It is their money being wasted though right, so just enjoy coding as usual.

Sounds like my boss.. 😣

I’ve had to deal with this for months now. I’ve come to realize that they are wasting their own money, I have to code anyway, and this way there is at least more work for me in the long run ;p maybe this is what your boss is thinking. We do what they ask and hope they ask for changes = more hours of work = more money.

This is one of those drag it out to earn more money instead of earning personal growth situations.

@angrydev2357 Idk, alcohol maybe?

Around lunch yesterday I came out of an hour long meeting with my boss and client. Under that time non of them knew What They wanted exactly, but they wanted me to do it well and perfect.

Focus on the goal (What problem is the tool supposed to solve) instead of asking the client to design the perfect tool and hand you complete specs for it.

Release early, measure how it is used and get feedback from real users rather than PHBs

Aaah, waterfall, well known for making projects succeed!

We all have been there at least once!

It's now a part of daily life.

This is pretty normal, though. I don't know why it is, but I guess from a few business standpoints it makes sense.

damn, that's why now that I'm older I hate waterfall 😣

@HogDev just do the needful!

For one, your boss seems to have the right agile mindset. Sometimes the client doesnt know what they want exactly either, and building on something that already exists is sometimes easier than thinking of something from nothing. Your code should always keep future changes in mind and be flexible.

On the other hand, its quite a leap to make too many assumptions. Clients should be aware of assumptions you make and they should agree with them. If your boss makes one-sided assumptions there is a risk you will make something unnecessary and waste money and time.