What Silicon Valley "Gets" About Software Engineers - Gergely Orosz
The expectation at traditional companies is to complete assigned work. At SV-like companies, it's to solve problems that the business has.
It's important to give developers the freedom to make important decisions that could positively benefit the business.
In practice, a motivated engineer easily makes multiple times the impact of a "factory worker" who is just told what tod o.
Engineers who are encouraged to solve problems will reflect on the tasks assigned to them. They will take the time to think about the business impact of the task. How does it align with the business goals? Can we avoid coding that feature at all? Can we ship multiple tasks at once?
Employees - not just engineers - often have access to realtime business metrics.
Developers with access to business data can make better decisions. They will be better informed of the "why".
Engineers should be encouraged to intereact with the reset of the business. Facilitate communication between developers, designers, and product leaders. Let developers become product-focused.
Encourage communication betwen developers from different teams. It's easier to solve problems as such.
Companies that care about engineers focusing on solving problems quickly set up various infra, platform and SRE teams, who reduce the developer experience churn.
"SV-like" companies think of engineers as value generators, and problem solvers. Traditional companies think of them as factory workers.
Creative problem solvers can bring in more value when used properly. You also provide engineers a sense of purpose when you give them more freedom to make decisions. This is how you enable them to contribute more business value.