zlacker

[return to "Most technical problems are people problems"]
1. jeffhe+Gs[view] [source] 2025-12-05 15:27:56
>>moored+(OP)
And most people problems are communication problems. Engineers aren't engaged with the product vision or the customer base, and are allowed to silo themselves. Product doesn't see the point of engineers being engaged and feed the engineering team like an in-house outsourcing shop. Sales and CS fail to understand the cost of their promises to individual customers to the timelines of features they're hungry for from the product plan. Goals and metrics for success fail to align. And thus everyone rows in their own direction.

The solution usually isn't "better people." It's engaging people on the same goals and making sure each of them knows how their part fits with the others. It's also recognizing when hard stuff is worth doing. Yeah you've got a module with 15 years of tech debt that you didn't create, and no-one on the team is confident in touching anymore. Unlike acne, it won't get better if you don't pick at it. Build out what that tech debt is costing the company and the risk it creates. Balance that against other goals, and find a plan that pays it down at the right time and the right speed.

◧◩
2. dyausp+6A2[view] [source] 2025-12-06 04:30:41
>>jeffhe+Gs
That’s wishful thinking but not in the way you think. A lot of engineers just want to finish their tickets and get out of there, that’s the reality. They don’t want to be in more meetings with the end user or product. You might have 10% of folks that actually love the job and want to build products at most places.
◧◩◪
3. hexbin+lK2[view] [source] 2025-12-06 07:05:05
>>dyausp+6A2
> A lot of engineers just want to finish their tickets and get out of there, that’s the reality

All the juniors I've known in my career never started that way.

I wonder what happens along the way?

[go to top]