alt Hacker NewsIf all you were doing is taking requirements from someone else and poorly coding them up (and yes I know a decent % of the industry matches close to this) then yes you are obsolete. Something just as useless but much faster now here.
If you are part of the requirements process. If you find problems to solve and solve them. If you push back on requirements when they are not reasonable. Etc. Then you still have a career and I don't see anything coming for you soon.
Replies
haolez • today at 12:34 AM
Recent models are pretty good at pointing out unreasonable requirements.
> If all you were doing is taking requirements from someone else and poorly coding them up
So, in your entire career, you've always worked in companies where you were a subject matter expert on everything the company did? Always knew the business domain inside out? You were running the numbers, sitting with customers, and determining yourself what they really wanted?
> If you push back on requirements when they are not reasonable. Etc
I did, because the requirements had a cost, which I had to balance with limited resources.
If widget A would make 10 customers happy, but would cost two weeks of work, that could be better spent making widget B that'd make 20 customers happy, then it would not be reasonable.
If widget A and B are free, then it becomes unreasonable to say no.