"Until the interval between writing code and deploying code is short enough to be a functional feedback loop, all you will be doing is managing the symptoms of dysfunction." -Charity Majors stackoverflow.blog/2021/01/19/ful…

i wrote a post for a friend, who asked "how do i feel worthwhile as a manager when my people are doing all the implementing?" charity.wtf/2021/01/23/que…

How it started How it’s going

manager: "so how's that feature coming along" me:

I Am Overwhelmed By All Of The Things I Need To Do, So I Am Doing None Of Them: A Memoir

Taking time off work only results in me wanting to take more time off work. I think I’m doing something wrong.

Need a slow-motion version of this GIF that lasts an entire year

It's Easter weekend, the perfect time to add even more eggs to Wingspan

Write fast crummy code to get to market, and we'll fix it later. I've never seen anyone fix it later. Never. You are just sabotaging you future. In any event, crummy code makes you slower *now*. You have to deal with it as you're writing code *now*.

NASA: Achieves first helicopter flight on Mars Whereas I:

Me explaining how simple and convenient our deploy process is

Me treating myself "because it's been a rough week"

Too real

Accurate?

Situation normal in most places:

Me every time I have to debug an issue with our CD pipelines

Conway's law is valid within a team as well. "If we have a 5 person team, and we give each one a different task to work on, we are creating 5 different 1-person teams. If we have a problem with our team's output, it might be useful to become a 5-person team." #conwayslaw

I often hear people say that Agile approaches are incompatible with fixed deadlines. In my experience, delivering iteratively and incrementally is the best way to mitigate risk when you have a date with a consequence.