Showing 120 notes (Page 5 of 6)
A behavioral design think tank, we apply decision science, digital innovation & lean methodologies to pressing problems in policy, business & social justice
After 25 years of my career I came to understand that one particular type of programmers is the source of many problems in our industry. Here is the story of a project that was nearly destroyed by two such programmers. One of them was leading frontend development, the other – backend. While the rest of the team was slacking off because business requirements were in the works, these two chaps were working hard.
A study of Google's code review tooling, AI-powered improvements, and recent statistics. Critique, "Modern Code Review at Google," and various Google software engineering papers.
Imagine you’ve been tasked to implement a sizeable new feature for the product you’re working on. That’s the opportunity you’ve been waiting for - everybody will see what a 10x developer you are! You open a list of the coolest new libraries and design patterns you’ve wanted to try out and get right into it, full “basement” mode. One week later, you victoriously emerge and present your perfect pull request!
One of the fundamental challenges in software engineering is managing and minimizing complexity. This challenge is not just a theoretical concern; it has real and tangible impacts on the pace of development.
If courses teach you’ll be building more greenfield projects than not, I’d be hesitant to consider it a well-rounded education in software development.
New managers often want to get everything right from the get-go. But, ironically, that would be their first mistake. Why? Because that's the total opposite of authenticity.
Good enough code is a nice middle ground between implementing a feature fast and maintaining the code quality.
Why aren't developers write tests? Because they are bad for them
The Startup CTO's Handbook, a book covering leadership, management and technical topics for leaders of software engineering teams - ZachGoldberg/Startup-CTO-Handbook
In the emerging age of AI generated code, is leetcode really the best way to evaluate technical candidates (was it ever)?
Aka, how do I know if a product leader knows what they're doing? There are thousands of articles, courses, and guides on how to build a roadmap for product managers. Even with all these resources, roadmaps often become a point of contention between product managers and their stakeholders. There are very few guides for engineers, designers, or executives on how they should evaluate or engage with a product manager's roadmap. This post comes from a presentation I put together to answer a simple b
A lot of information can be found online about suggested best practices for pull requests (PRs) and code reviews, particularly regarding the ideal size, scope, and description of PRs, as well as the desired response time and comment style for code review comments.
Yesterday we had a super fun meetup here at Intercom in Dublin. We split up into small discussion groups and talked about things related to managing teams and being a senior individual contributor…
Showing 120 notes (Page 5 of 6)