Call me senseless, but what if we just removed the need to always have a stapler at hand? What kind of life needs to have all of these random bits of bric-a-brac immediately at hand?

This kind of idea makes me wonder if the people pushing these products have some cartoonish notion of others' lives

Based on my own experience, I think building a team that can do the work with only a light touch on guidance is an excellent goal to work towards. I'm a big believer in letting professionals/competent folks do what they need to do, but keeping close by in case they need support of some kind

Of course, there were other times when I helped guide architectural decisions and made sure individual work harmonized, you could say, with the rest of the team's work. I was really fortunate to work with great engineers who mostly needed me to support them and stay out of their way

I could understand moving from a monolithic repo if you were afraid of the blast radius of introducing a bad change, but that still feels like something you could solve through better post-deployment testing and monitoring.

Not sure if moving between monolith <-> microservices would actually help

I'm curious if this indicates a problem in inadequate testing or change management. One of the orgs seemed to have good automated testing and controls around changes. Another org did not have good automated testing and controls.

I've seen an org decide to go from a monolithic codebase to multiple repos/units, and I've seen an org decide to go from multiple repos/units to a monolith/monorepo. The main factors in these cases were how difficult was making changes and avoiding regressions.

Software cultures are absolutely deprived of compassionate moments where we get to be human together and experience being on the same side together. I really believe that humanness changes people's lives and I'm not giving up on its power. I have seen it measurably work, again and again.

Right! I think this kind of thing often happens when teams focus on shipping the feature without asking if the feature is anything anyone actually wants or helps the person at the other end of the computer actually do whatever it is they want to do (assuming that's something the team cares about)

The power of defaults is one of the reasons why the pit of success (learn.microsoft.com/en-us/archiv...) is one of my favorite metaphors for how we should make successfully using or doing whatever the user needs the easiest path. It should be more difficult to run into trouble, not easier

I think this kind of shit talk is especially appropriate given that the Gospels go to some length to criticize the people who loudly, visibly, and aggressively proclaim how faithful they are in public places instead of living the virtues they claim to hold so dearly

Plus, one nice thing about Occam's Razor is that you can absolutely ignore Occam's Razor. It's not a law. There's no Philosophy police who will send you to Logic Jail.

Pick the more complex-but-equal option has a little philosophical treat for yourself!

I like how the line "what the good Earth gives, you get" sounds like it's mandatory, no opt-out, "you're going to get this cereal whether you like it not" cereal