Motivating IT people to change, talking to developers

You know how things go. Somedays, all of the sudden, it’s 4:17 and you have your last meeting of the day at 4:30, and it’s also your daughter’s third birthday, so you need to get to that. And while you managed to eat a really great sandwich, it also, turns out no one’s walked the dog all day! Thankfully, I also had the pleasure of talking with Ben today about two topics I’ve been thinking a lot about this week: how can infrastructure and developers get over their acrimonious history and start talking with each more, and, some thoughts on the Spring Framework.

Sometimes, you need start with the explanation and see what opinion fits

These 5 tactics are good for a 13 year old student or an adult knowledge workerHere are the five test taking and essay test taking tips I shared with Cormac: If you’re doing the assignment in Google Docs, or whatever, of possible, copy and paste the questions into your document. This way, you have them right in front of you. You don’t have to answer the questions in order. On your first pass, just answer the ones you feel have an answer for.

The Narcissism of Small Differences in Charts

The Narcissism of Small Differences in Charts In surveys, just because something is last doesn’t mean it’s bad. It’s true the other way as well. Now, if there’s a huge difference between the first and last thing, then, sure. If 85% of people like the first choice, and 15% like the last, you’ve got a stew goin'. But, when the differences are small - let’s say all below 50%, you need to be careful with how you interpret the chart.

20230321

I very much so want to use this style for reports. Those charts are amazing.Feedback on today’s piece.Here's my final article. What do you think? Tell me your analysis of what I could have prompted you with to get your responses close to this final version. 🤖Your final article effectively discusses the challenges of solving the IT silo problem, the limitations of siloed organizations, and various approaches to tackle the issue.

The Silo Unifier’s Paradox

If no one owns the problem, no one can fix it - The Silo Unifier’s ParadoxSolving the IT silo problem is challenging as there’s no one person responsible for the entire process. Each solo is owned by different groups like software developers, operations, security, project managers, and more. These groups often have competing goals, desires, incentives, and lift-styles/worldviews. Agile and DevOps practices attempted to break these silos, shifting activities like testing, security and ops “left” to developers, or centralizing shared services (“platforms” now-a-days).