This video is a snapshot of Spotify's approach to software enginering and people management in 2014. It has since come to be known as the "Spotify Model" (although I didn't coin that term).
I’m commiserating with a friend who recently left the technology industry to return to entertainment. “I’m not a programmer,” he begins, explaining some of the frustrations of his former workplace, before correcting himself, “—oh, engineer, in tech-bro speak. Though to me, engineers are people who build bridges and follow pretty rigid processes for a reason.”
Data is changing the way businesses are being built and run. Most CEOs and business leaders will agree that future success is increasingly reliant on their ability to turn data into a differentiating advantage. Yet +70% of enterprises still lag in their ability to create value from data.
Whether they're written down or part of a company's oral traditions, every software engineering team has guidelines its developers use to direct their efforts. These are the ones we use at One More Game.
Anyone who's worked in game development for a while knows that launching games is challenging. Creating online games is even more difficult, as it requires building Internet services like matchmaking, account systems, chat services and many more. Guild Wars, an online Role-Playing Game I helped develop at ArenaNet, requires ~30 backend services, and its sequel, Guild Wars 2, has ~80! By the time I left ArenaNet Guild Wars 1 included 6.5 million lines of code, which is about one-fourth of the number of lines in the Linux operating system kernel!
(4) Spotify Engineering Culture - Part 1 - YouTube
Why Computer Programmers Should Stop Calling Themselves Engineers - The Atlantic
A primer on engineering delivery metrics | LeadDev
The Data Opportunity: the Emergence of a New Layer in Modern Enterprise | by Irina Haivas | Atomico | Jan, 2021 | Medium
Engineering Tenets
Alpha-Driven Development
20 Things I've Learned in my 20 Years as a Software Engineer - Simple Thread