Blockchain. I can probably stop here. Merely having the word on the Vidya site will increase blog readership more than if I posted a deleted scene from Black Panther. There are already thousands of thought pieces explaining Blockchain, how it will revolutionize commerce, how it will transform the Internet. There is even a company whose decision to add Blockchain to its name led to a 600% stock surge and a financial windfall for its CEO!
I will be speaking at Tech Talk DC on October 25th in Arlington, Virginia, on Here’s What’s Trending In Software Engineering. Whether you build software, manage projects, or run enterprises, you’ll discover techniques and technologies that will give you an edge in the years to come. If you saw me speak on this topic at Code Writers Workshop in the summer, rest assured this talk will be different. First, I have added some wrinkles to the original list you will likely find compelling.
The 2017 Stack Overflow Developers Survey had the most respondents since they began the project in 2011. You really should take a look. They cover a lot of ground, and the findings across geography and demographics are fascinating. It’s interesting most developers report feeling underpaid. That isn’t surprising to me, but it might be counterintuitive to people more accustomed to Stark Industries than to Pied Piper. It’s natural to follow up by asking which programming languages pay the most, and those answers did surprise me.
The Code Writers Workshop is taking place outside Washington, DC on June 9th with the theme “Software Leadership in a New Era.” The speakers are a diverse, distinguished array of industry leaders who have done great things around the world. The keynote speaker, Kara DeFrias, was Director of UX for former Vice-President Joe Biden! The surprising thing is they’re letting me speak too. I have the honor of speaking on the topic “Here’s What’s Trending in Software Engineering.
Anyone with a basic knowledge of Scrum, and certainly everyone who has taken Agile Software Project Management With Scrum, knows the role of the ScrumMaster–to be a servant leader, to act as guardian of the Scrum process, to remove obstacles for the delivery team, to negotiate any tension between the Product Owner and the delivery team, to encourage the team to self-organize and be cross-functional, and so on. These are so well understood they’re almost clichés.
Alvin Alexander is a renowned software engineer and author. His Scala Cookbook was invaluable when I got started with Scala, and that book and his prolific blog posts have remained essential reading even as I’ve gotten better at it. One of Alvin’s most recent posts, How Scala killed the Strategy Pattern, is the latest iteration of an old criticism of the Gang of Four (Go4) Design Patterns by functional programming (FP) advocates–that you don’t even need them if languages provide sufficient abstractions.
I was recently at an event hosted by the Agile Leadership Network of DC (ALN) called Reflective Retrospectives To Build High Performing Teams. It was an interesting presentation with a highly credentialed speaker–Certified Agile Coach, ITIL, PMP/PMI-ACP Coach, Protector of the Realm, Breaker of Chains, and so on–but what really struck me that evening was a question from the audience. The question came from a fellow software engineer, who began by noting that ALN events typically engage executives and managers rather than engineers, and can be paraphrased this way:
News broke recently that the Transportation Security Administration (TSA) contracted the development of an iPad app called the Randomizer that eliminates any hint of profiling by airport security by simply directing travelers according to an arrow onscreen that randomly points left or right. That’s it. No, really. An arrow that points left or right. At random. Over and over. The cost? $1.4 million. Yes, that’s dollars. Naturally, the Internet sprung into outrage.
At an event recently, someone was kind enough to introduce herself to me, and during the course of our pleasant conversation, she asked me, “So are you a programmer?” My first impulse was to acknowledge once again that I look really nerdy. I embrace that. But my second impulse was to be mildly offended. I wasn’t sure exactly why. As I have reflected a bit about that, I think my visceral reaction to being called a “programmer” arose from my perception of programmers as just people who write code, which is a science.
As I help to revolutionize how government buys IT by teaching federal acquisition professionals to avoid spending hundreds of millions for deliverables that don’t work, I have stressed that the best way to maximize value and save taxpayer dollars is to understand the principles behind agile software development and to construct contracts accordingly. Incentives (also called fee) have long been a significant part of government contracts–including contracts for software application development.