You're Worthwhile, Even When You Make Mistakes
My big secret ("My work isn't good enough") was finally out. Yet I wasn’t being fired. I was being offered help from someone I respected. I was still worth their time.
Visit spin.atomicobject.com → RSS feedOn Hacker News Aug 2010 – Nov 2024
Software Engineering 18Career & Management 11Tools & Productivity 7Life, Learning & Writing 5Programming Languages 5Tech Industry & Business 4
My big secret ("My work isn't good enough") was finally out. Yet I wasn’t being fired. I was being offered help from someone I respected. I was still worth their time.
Small software teams are dramatically more cost efficient than large teams. Large teams don't even confer much calendar time advantage over small teams.
There are many great coding principles, but it can be hard to keep them all in your head at once. Instead, I try to remember these three attitudes.
Everyone knows they should pick their battles, but how do you decide when? Here are 3 questions for figuring out when to push back and when to let it be.
Instead of taking all my vacation at once, I decided to see what a 4-day work week would look like. It taught me a lot about myself and how I work.
Use the Penny Game to explore the difference between capacity and output, and why backlogs invariably grow, no matter how hard you work.
A structure where software architects work on a team separate from the development team can lead to dysfunction, reduced quality, and poor morale.
Over the course of my career, I've found two characteristics to be among the most important for software developers to thrive.
There's a lot you should know before you start creating software. Take time to understand the product, business, users, and overall project journey.
An eclectic online curriculum that covers the core requirements of a typical undergraduate CS program.
You can’t expect others to fix your problems. When you take responsibility for making the best of any situation, you have the power to make things better.