Have you realized why software undergoes lots of design changes?
Why?????????? I yell..
PLM says "I need this for our customer"
Architect (the p.hd guy talks mathematics) says no this has to be done this way.
Poor Developer (ME) I come up with a design proposal considering all the comments, When PLM is available, Architect is too busy and someone else is the "Acting Architect" and gives me a "Go Ahead".
Feature is Design Done/ Code Done/Review Done/ Docs Updated .
And time to chill out.
Requirements changes again and again, hits the feature State Machine. Back to square one.
How would one feel? I feel like goin on the top of mountain and scream...
"Why the hell Am i a software engg"?
Subscribe to:
Post Comments (Atom)
Why requirements change frequently :- this the technique invented by SW companies to keep the enggs occupied as well as customers billing!!
ReplyDeleteSuperAppu..Great work by a true Genius from PSG ROFL
ReplyDeleteI don't understand why the "acting architect" should give a "Go ahead". He can help you to come up with a better design, but unless he is the "real architect" you should not start implementing the same.
ReplyDelete