Showing 112 notes (Page 5 of 6)
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…
How to be effective in the theatre of work
News is bad for you. It leads to fear and aggression. It hinders your creativity and makes you sick. We should stop consuming it, says Rolf Dobelli, who's abstained for years
"...the mere consciousness of an engagement will sometimes worry a whole day."� Charles Dickens
If you collected lists of techniques for doing great work in a lot of different fields, what would the intersection look like? I decided to find out by making it.
When I’m being first-order productive, I’m programming: creating and interacting with a system. This first-order productivity is great, but it isn’t discoverable for others: there’s generally a high bar to entry for comprehending another person’s work when it’s expressed solely as a structured program. Second-order productivity is when I’m writing about programming, or about systems. This kind of productivity is generally more accessible and distributable, and forms most of the content of this blog!
How small tech companies are using remote work to compete with the big guys.
In a world where technology is trying to make things increasingly easier, make things a little harder on yourself. You’ll get better results.
Showing 112 notes (Page 5 of 6)