DevOpsy

I personally feel that Apple is doing supremely well recently. Their new chip architecture is almost magical how it can run so fast and so cool and Apple Vision makes the next best VR/AR headset look like an old piece of crap.

If they manage to make gaming more of a thing with their products and the Apple Vision becomes more compact and cheaper (which it will), they are heading for a new golden age.

Just like everything else in software delivery, you are not aiming for perfection and ideals, but to continuously optimize and improve. You may never get there but that also doesn't mean you need to accept friction and not do anything about it.

"Fewer meetings" could indeed be applied to a fault (like everything else) but that's definitely not the aim, the aim is to optimize for async communication and have more substantial meetings with outcomes when you need to have them. And also, it is far more rare to work at companies where they don't have enough meetings, usually, it is the opposite.

I definitely didn't mean to imply in the article that meetings or sync communication in general does not help contribute to flow state. My point of view is that these sessions you do synchronously are also a big part of what makes flow possible, because after them doing the work becomes easier, more clear and flow is more possible. But they are very much necessary to plan, strategize and discuss as you well put it. Also to ensure the right code is written. Although on that note I also feel that all meetings and discussions should have a codified result, especially when it comes to align with engineering principles, coding style guides, and things like that align people in the way they work.

I will need to revise the article to ensure I am clear about that point, thanks for the feedback!

Work as a form of communication --> Most conducive to flow state

Asynchronous communication --> Second best

\Synchronous communication --> Least conducive to flow state

Great developer experience (DevEx) is what you get when developers can easily achieve and maintain flow state at work.

If you need to attend a very large tech conference (or if you have before) this will help

It seems that user experience always takes a back seat when designing tools and people just associate UX with the UI, but it should apply to everything.

These best practices revolve around abstracting your terraform code away, favouring inputs over code changes.

Skills and resources to help you get into DevOps

Daily life in a DevOps role and ways to mitigate yak shaving.

Some ideas and practices to do TBD and keep your git history cleaner

You know I have to agree with you that AWS UI is more responsive, the UI in GCP is a bit heavy on the JS and sometimes can make the CPU spin. However due to all the reasons stated in the article, I would take that downside any day, twice.