Michael Petrovich. Working and writing at the intersection of engineering, product, and data.
-
Software engineering: a decade later
AI can write the code. It can’t feel when the interface is wrong.
-
My README
A personal README on my background, beliefs, how I work, my strengths and weaknesses, and how to give me feedback.
-
You need to calm down
AI isn’t changing the fundamentals of building software. It’s changing the speed. Don’t confuse the two.
-
The highest leverage work happens early
Most people spend too much time implementing solutions and not enough time defining problems and designing solutions.
-
Effective delegation
Effective delegation is hard, but this framework can help.
-
Speed drives quality
The faster you deliver, the faster you’ll achieve high quality.
-
How to be successful
The individuals that deliver outsized impact to the people, processes, and products around them all share a few key traits.
-
How to make decisions that don’t suck
Despite its ubiquity, decision-making is a skill. Like many skills, it can benefit from the same principles behind deliberate practice.
-
To The Brink Of Burnout And Back Again
I didn’t realize it until it was nearly too late.
-
Adventures in Product: The First 90 Days
The importance of systems for learning how to learn.
-
The Three Dominoes
Three simple rules that have an outsized impact on how successfully a team operates
-
From Engineering To Product: The Adventure Begins
About two months ago, I became a product manager for the first time after over a decade in engineering.
-
The #1 Rule When Talking To Customers
Your customers will mislead and lie to you unless you follow this cardinal rule.
-
Manager README
What are my beliefs? Strengths? Weaknesses? How do I work?
-
Book Summary: Build What Matters
Deliver more customer value by orienting a product vision and strategy around customer outcomes.
-
The 2 questions that lead to better decisions, every time
1. What problem are you trying to solve? 2. How do you know that?
-
Lead time is the KPI for process
Measure it before and after any process change to prove that it’s a good change.