Essays about work, ambition, love, family, and everything underneath.
Four frameworks to find friction, question the task, keep human judgment where it matters, and decide what the time you recover should make possible.
The real risk isn't the vendor shutting down. It's a product that stays technically supported while nobody maintains it, and what to check before you sign.
Four questions that tell you whose problem it is, the two numbers that decide what you do about it, and how to report any of it to a board you answer to.
The UI refactor process broken into twelve small, gated steps, so an agent can't collapse it into generic redesign slop or break flows nobody documented.
The invoice is the smallest of five numbers. How to find the other four before you sign, and why funding in terms leaves a cliff nobody costed for.
Six tests for what stays with a person. When an approval is theatre, when nobody notices a bad run, and what automation moves rather than removes.
What the first month actually looks like, what deliberately does not happen in it, and how to run most of it yourself before hiring anybody.
You picked the workflow. Now someone wants to build it as an agent. How much of the control flow to hand over, and which actions it may take without a person.
Someone has suggested building custom software. How to tell whether you actually need it, what the five year cost really looks like, and the cheaper options.
Everyone is using AI and nobody can point at an hour they got back. What makes a workflow worth automating, and where AI is the wrong tool entirely.
Four different things get called a CTO bottleneck, and they have different fixes. How to tell which one you have, and how to have the conversation.
Most technical debt costs you nothing. How to tell which of it is actually expensive, what it is costing you in, and how to rank it against shipping.
Three quotes for the same project, all different, and no way to compare them. What a proposal has to define, the questions to ask, and the warning signs.
Someone on your team wants to rewrite it. How to tell whether the system is really the problem, when incremental wins, and what a rewrite actually costs.
You doubled the team and shipped less. Eight causes that look identical from outside, how to tell which one you have, and roughly what each costs to fix.
The signals that a startup needs a VP R&D, the ones that only look like it, and the difference between a VP, an engineering manager and a CTO who is stretched.
The interface that unified four integrations, and the startup that served every industry, are the same mistake. How to spot premature abstraction early.
As the workplace evolves, so does the definition of effective leadership. Emotional intelligence, when paired with agile leadership principles, can enhance a leader's ability to navigate team dynamics.
Hiring took weeks. She starts Monday and nobody has picked her first task. What developer onboarding actually needs: the first 1:1, first tasks, a buddy.
The tech industry is known for its long hours, fast-paced environment, and high expectations. Here are 10 strategies for promoting work-life balance and avoiding burnout.
The tech industry is known for its fast-paced, competitive environment. Here are strategies for building a supportive work culture that reduces stress and improves employee well-being.
The tech industry is a high-pressure environment that can take a toll on employees' mental health. Learn how companies and individuals can break the stigma and prioritize well-being.
Written in 2023, with a note from 2026 on what it missed. The real question is which repeated task is worth handing over, and who maintains it a year later.
Leading a team in a tech startup requires a unique blend of technical expertise and exceptional people skills. Explore five essential people skills that every tech startup leader should cultivate.
In the rapidly evolving world of technology, staying ahead of the curve is essential. The key to maintaining relevance and unlocking new opportunities lies in upskilling and embracing a continuous learning culture.
Remote does not break a team. It removes the accidental communication that was covering for unclear ownership. Six practices, and how to tell the difference.
Ten things that make mentoring a junior developer work, and the point where more mentoring stops being the answer to a seniority gap you have not hired for.