What Silicon Valley "Gets" about Software Engineers that Traditional Companies Do Not
“1. Autonomy for software engineers; 2. Curious problem solvers, not mindless resources; 3. Internal data, code, and documentation transparency; 4. Exposure to the business and to business metrics; 5. Engineer-to-engineer comms over triangle-communication; 6. Investing in a…
- from
- Engineering Team Management
- added
- 2026-10-10
- likes
- 0
similar
-
All the best engineering advice I stole from non-technical people medium.com
“It's intriguing that the stuff that really seems to make a difference in the quality of software never seems to be about software.”
-
What Makes A Great Software Engineer? faculty.washington.edu
Doesn't conclude on a definitive answer to the question, but details a model based on 53 attributes (!). Still a good source referencing other papers on the topic.
-
Software Engineering's Greatest Hits youtube.com
When scientific method meet the practice of software development. My takeaways: the best metric is less lines of code, there is no 10x developers, too much unused configuration options, pair programing is for transfer of domain-specific knowledge and hackathon don't produce…
-
Paper we love: Software Engineering Organizations github.com
“The practice of software engineering, and its history is, itself, a complex study in humanity, coordination, and communication.”
-
Some reasons why enterprise software is good and maybe even fun news.ycombinator.com
The majority of us will not build the next unicorn: we statically have a better chance to build enterprise software. The twist? It might even be more interesting than you expect.
-
Surprising Things About Working at Well-Known Tech Unicorns blog.pragmaticengineer.com
Echoes my own experience on differences between expectations and reality in high growth and visible companies from the point of view of an engineering manager.
Engineering Team Management › Motivation: ““1. Autonomy for software engineers; 2. Curious problem solvers, not mindless resources; 3. Internal data, code, and documentation transparency; 4. Exposure to the business and to business metrics; 5. Engineer-to-engineer comms over triangle-communication; 6. Investing in a…”