
An Ode to Junior
Learning, building trust, and getting stuff done are crucial to progressing your career - especially early on. These are the things I learned on my journey from junior.
Musings from day-to-day Software Engineering
Dormant Last read · last published · next check
Read 2 days ago and current, but nothing has been published for 13 months.

Learning, building trust, and getting stuff done are crucial to progressing your career - especially early on. These are the things I learned on my journey from junior.

Many engineers like having interesting side projects to show off, but motivation is hard to keep up. Understanding how you're motivated is crucial. Here's some methods I use!

Design your team around your product, remove silos and increase productivity with a cross-cutting product team.
Action without reason is worthless, and worse than inaction. Take the time to stop and measure before committing, or risk wasting more effort with nothing to learn from it.
A new project dawns, a new domain begins. Somebody whispers 'domain-driven design', and the team forms a circle around them and chants 'event storming'.
One-to-ones are an excellent opportunity for building trust and achieving goals with your team lead - How can you make yours more impactful?
Not the sword-wielding friends, nor the (4) Teenage Mutant Ninja Turtles. It's just a useful tooling pattern that I recommend - potentially one of the best to have in your belt.
In your job, you have to make many decisions - or contribute to many. Having a strong opinion (that is loosely held) will make strides. Here's why and how to generate one.

Stop writing so many unit tests and join me on the dark side. Focus on integration testing instead of unit testing, and bask in the saved time and superiority.
Most engineers have actively refactored code they're responsible for, and a lot think there's no cost to refactoring - but there is. Let's explore and understand, what is it?