Nappi Sight

Just listened to The AI Dilemma and it definitely elaborated on and articulated some of my own concerns, as did the news of OpenAI plugins. The synthesis of concern is: AI doesn't need to be that powerful to be destructive and destabilizing (e.g. social media algorithms) to people and society. These new LLM's are already much more powerful than social media algorithms. Many of the new LLM capabilities are emergent and poorly understood. The experts designing these systems don't fully understand them, and some of whom are already worried about what they've created. LLM's are being rapidly and recklessly deployed very broadly across society, in an arms race. The strongest argument against worry is that these LLM's aren't really intelligent, are really just a super-autocomplete that enables automating mundane tasks via natural language. But I don't think any of the companies developing or deploying these things are arguing that. Even if they were, see #1 &

Having a bit of a background in philosophy and being a software engineer, I’ve found the recent explosion of interest in AI since the ChatGPT debut to be fascinating from multiple perspectives.  In one sense there are considerations about whether generative AI is really AI, and/or whether it's on the right path to deliver AGI. Relatedly, its ability to pass standardized tests raises questions about what those tests are really testing, and even raise questions about what we mean by intelligence and how we measure it. On the other hand, there's consideration about the practical usefulness and impact, regardless of whether it's an actual intelligence or glorified autocomplete.  Can it be safe and reliable, what can it automate, will it improve productivity and/or lead to massive unemployment? Interesting questions. I’m neither deep on the philosophical side nor the engineering side of these topics, and many debates seem to mix the two, but I have used ChatGPT 3, and Bing AI, a

Here’s what I read this past year: Rest: Why You Get More Done When You Work Less Leadership BS: Fixing Workplaces and Careers One Truth at a Time AARP New American Diet: Lose Weight, Live Longer The Managerial Revolution: What is Happening in the World Nicomachean Ethics Invisible Storm: A Soldier's Memoir of Politics and PTSD The Machiavellians: Defenders of Freedom The Death of Expertise: The Campaign against Established Knowledge and Why it Matters Shift into Freedom: The Science and Practice of Open-Hearted Awareness How Will You Measure Your Life? Snow Crash: A Novel The Hydrogen Sonata (A Culture Novel Book 9)

Recently, I decided to resurrect and upgrade my 10 year old EasyCache nuget package, although it ended up not being that easy. Codeplex has since shutdown, and Nuget no longer allows sign-in via a username/password account, nor can you claim access to the old accounts via any other means. Nevertheless, I created a new account, and dredged up the source code to publish a new version. I also published a couple other utilities that I thought might be handy. EasyAsync EasyCache EasyHash Enjoy!

At recent software architecture training, there was a lot of negative discussion of Agile, which got me thinking about the what the strongest defense of Agile might look like. And by Agile I think more of the practices of Extreme Programming than rituals of Scrum. IF you accept a few premises, then I think Agile appears reasonable. Those premises look something like this: Engineering requires a rigid and highly specified design/design process. Producing a highly specified design is expensive (time, money, effort, training), but necessary to avoid the even more expensive prospect of wasted building materials. Building materials (code) are virtually free and infinite in software. Software is inherently more complex than other engineering disciplines, or at least too new for a body of sufficiently reliable engineering practices to have evolved. There may yet be something unique about software's lack of physical constraints that defy or modify typical engineering

“There are no wrong answers in architecture, only expensive ones” – Mark Richards The four engineering metrics that will streamline your software delivery - Stack Overflow Blog Does ES6 make JavaScript frameworks obsolete? - Stack Overflow Blog Code quality: a concern for businesses, bottom lines, and empathetic programmers - Stack Overflow Blog Best practices for REST API security: Authentication and authorization - Stack Overflow Blog Why Intuitive Troubleshooting Has Stopped Working for You Scatter-Gather Gatekeeping, Passion, Career, and Life What Color is Your Function? How Big Tech Runs Tech Projects and the Curious Absence of Scrum Productivity vs. Guilt and Self-Loathing Heuristics for Effective Software Development Organizations: A continuously evolving list.* THE VALUE OF SPEED Getting Started with Agility: Essential Reading Stop Technical Debt Before It Damages Your Company XP as an Incentive System – Kent Beck – X