I keep repeating this. Here is a quick list of suggestions on how to write good documentation: 1. Empathize with the person reading and trying to understand your code/api. This should be obvious but apparently isn't.

One of the few things that I can be absolutely definitive about is the definition of a "Deployment Pipeline", because I defined it. So here is a short thread that answers the question “What is a Deployment Pipeline". 1/9

the entire thread is excellent. application architectures matter in being able to deliver collaboration features.

excellent rant. largely agreed about desktop vs web applications today. other concerns aside, it _is_ possible to use graphql subscriptions + react to create a real-time UI. one _does_ have to consider the entire stack, as he says.

🤗 Hi friends! I’m speaking in the Just Culture track at QCon San Francisco Software Development Conference this year. I’d like to hear from engineering and operations folks about your experiences after incidents and outages. Please RT for reach 🙏 forms.gle/KhUrRPDjUcUX4e…

New blog post: Spring for #GraphQL is the recommended Spring integration graphql-java.com/blog/spring-fo… Spring for GraphQL Team

🔁🔁 💯💯 the feedback loops are key, all the way to production. i’ve also found that people need to experience them to truly understand.

💯💯 in order to appreciate practices that help with quality and maintenance, you need to have maintained a quality system over time.

Hot take: if you need multiple large monitors to program with, you should consider writing smaller/simpler functions.

Junior developers love magic. Senior developers hate magic. ...because they know it will eventually bite them in the ass. Learn to Keep It Simple and Stupid (KISS). #developer

excellent thread on building software. the approach is sound irrespective of where you work in the stack.

💯💯 intellij helped me think of my code not as text, but an equation that can be manipulated. refactoring are the key to making these transformations.

i’ve made a mastodon account for the future - @[email protected]

Ha! I predicted this correctly! In years of discussions about microservices and how it helps solve the org problem, we never stopped to wonder if the (bloated) org *itself* is the problem. But now that CEOs are convinced companies are overstaffed and org charts need culling 😉

biggest software flex i've seen in a while: shakti.com