|
|
|
|
|
|
by sarchertech
1346 days ago
|
|
|
I have never understood why companies consistently hire people right out of college (often with random degrees unrelated to anything relevant) to tell a team of engineers with 10-20 years of experience what (and often how) to build. Back when I was new, engineers worked directly with subject matter experts and the occasional business analyst. Now we’ve mostly replaced SMEs with product, and I don’t think it’s working out. |
|
|
Exactly this.
Not only that, but when it works the way you're describing, it's often a 2-way conversation. The developer strives to understand the goals, then starts making suggestions to determine if the business is ok with shortcomings that would make it a lot cheaper and faster, but would fulfill those goals. They'll also dig into what the business wants in the future so when the implementation starts they can take that into account.
Instead we get product who wants to own all of that and then throw things up into a jira ticket and have it magically be great. There's no value add there.