Getting things done in small increments (2022)
Many programmers subscribe to the belief that they need large blocks of uninterrupted time to get anything done. Paul Graham wrote about this in Maker’s Schedule, Manager’s Schedule :
The latest blog posts to take off on Hacker News. 395 posts.
Many programmers subscribe to the belief that they need large blocks of uninterrupted time to get anything done. Paul Graham wrote about this in Maker’s Schedule, Manager’s Schedule :
Companies are fighting back for quiet quitting and it's having a big impact.
The new normal in tech recruiting
How understanding cognitive load and team capacity can help you decide on an architectural style
A plea for more respect for documentation and technical writing in the software development industry.
I created The low-tech guys, a brand under which I develop macOS apps for a living. I started this business with a good friend of mine, thinking I could help him stop working long hours at his consulting job and ease into more creative work. However, getting to a state where you earn enough to live off the app sales…
Don’t just read it; fight it! Ask your own questions, look for your own examples, discover your own proofs. Is the hypothesis necessary? Is the converse true? What happens in the classical sp…
Optimism, obsession, self-belief, raw horsepower and personal connections are how things get started. Cohesive teams, the right combination of calmness and urgency, and unreasonable commitment are...
From a person who really shouldn't be giving others advice.
My partner and I both work from home. I'm very thankful for that as we have two young children and a commute would take up the same time we ...
Right after getting my degree, I was lucky to be hired into a small but decent R&D department as an embedded software engineer. My first task was to create a Unit Test project and have it run in our build pipeline after compilation. I was not particularly excited about this task, it seemed like busywork to me. I…
As adding more code to a product will slow down development, we should view all code as technical debt.
Software companies come in many sizes. There are small startups, medium-sized companies, and huge enterprises. As you might expect, startups are usually lean and fast. Big companies that develop large applications move much more slowly. Those might be systems developed for many years or decades by hundreds of…
The case for giving programmers private offices with doors — why open offices destroy deep work, how interruptions cost far more than floor space, and what the research actually says.
I learned things
This page describes 'The Apollo Syndrome', a phenomenon discovered by Dr Meredith Belbin where teams of highly capable individuals can, collectively, perform badly.
Listen now | "I was shocked with how intense, painstaking, and effective his learning process was"
Can I bring my emotional support dog?
A breakdown of 4 simple software engineering and coding habits that improved my productivity. These include keyboard shortcuts, learning to say no, reaching flow state faster, and keeping a big book of commands handy.
Why shifting full accountability for high-risk tasks to third parties increases rather than decreases project risk.
Leaders are paid to think clearly. And a big impediment to clear thinking is what CBT/REBT calls Cognitive Distortions: errors in thinking or thinking traps we commonly fall for. Most high-performers are not pathological, but instead fall for them when upset or in high-stress situations. In this
There has been a lot of discussion about how many Product Managers (PMs) are required in a product team. This conversation gained momentum after Airbnb restructured their product management organization, followed by articles about how startups are thriving without any PMs.
After more than 11 years, HashiCorp Co-Founder Mitchell Hashimoto pens a heartfelt goodbye letter to the company he helped create.
OKRs for Managers and C-Level? Great! But have you ever asked your teams? In this post I am sharing how I make OKRs less dry and more enjoyable for the teams I manage.
Then Life Continued
Learning how to build quality software is not part of computer science education. How do we learn it?
For interviews, it's not what you've done, it's how you explain what you've done. It's that fundamental difference which makes storytelling a critical interview skill.
Possibly the one you're Googling about.