The Great Law of the Iriquois takes a future-focused stance in decision making by considering the impact of a decision on future generations. Would this decision benefit our children seven generations in the future?
Previous I wrote about decomposing projects and three methods for breaking down a project:
Software Engineers rarely have time to read books. So when an engineer gets excited about something they are reading, I’m on board. I’ll buy the book and read it too; to build ubiquitous language on our team. It fosters clear communication; I like to call it ubiquitous reading.
Software engineers hate to waste time. That’s why they’re so adverse to meetings - why sit around talking when they could be writing code?
I’m working on getting better at what Cal Newport calls the work shutdown ritual rather than closing my laptop and getting the heck outta Dodge.
Good managers with a P&L always know their numbers. If asked, managers can recite them from memory. But some managers don’t always run off a budget. For Software Engineering Managers, their numbers are project statuses.
Seth Godin suggests blogging every day (including Saturdays and Sundays). At more than 7000 posts, he walks the talk. His writing, podcasting, and thought leadership continues to amaze me.
As the grandmother of Redfin’s VP of Engineering, Sasha Aickin, once said:
When everything is urgent, nothing is. Gergely Orosz (@gergelyorosz on Twitter) provides a list of four considerations when asked to take on “urgent” work:
Seth Godin gives us a similar question to the “5 Whys” intended to clarify a future path:
Mike Crittenden mentioned a presentation by Tanya Reilly called Being Glue. Teammates who are the “glue” take on the non-technical tasks required for solid teams. Then they are not promoted because they’re “not technical enough.”
Whenever I have a simple repetitive task, I like to create a quick single-page app to automate it.
Understanding your team’s scope of responsibility is made easier with a Map of the Universe. This one-page diagram outlines the high-level applications your team maintains and how data flows between them.
Every project must take into account three perspectives: the business perspective, the technical perspective, and the customer perspective.
In Software Estimation without Guessing, George Dinwiddie outlines three different ways to break down a project to estimate it:
It’s easy to hide in the corner and update task statuses instead of leading the projects you’re responsible for. That’s shuffling deck chairs on the Titanic.
Instead of framing everything wrong with your system as technical debt, call it a technical investment.
I love Tech Twitter. It’s why I’ve stuck with Twitter for more than 15 years. The resources generously shared by my fellow software developers and engineering managers help me learn, grow, and stay current in the industry.
I keep records for all sorts of things: fitness statistics, time tracking for work, and writing word counts, to name a few. It’s data that sits in notebooks and spreadsheets, and it will never be used again.
Welcome to my new site. I’m reposting many of the articles I send out from my newsletter Known Unknowns. This will become the source of truth for these posts.
The longer your career goes on, the more difficult it is to remember the things you’ve accomplished. Occasionally it’s a challenge simply remembering what you did last week.
Communication is critical in organizations and on project teams. If I can learn something than improves how a project runs, I’m all for it.
Bug reports are a minefield of useless comments to passive agressive opinions. They can be as barely detailed as “[thing] doesn’t work” to page-long diatribes that don’t really tell you what’s going wrong.