Pure speculation, but I feel the inference money is tiny compared to the speed and permanence of Office integrations MCP enables through the consultancy swarm.

MCP lets you glue random assed parts of services to mega-ultra-high critical business initiatives with no go between. Delivered through a personalized chat interface that will tell you how sexy you are and how you deserved to win at golf yesterday… from salesman to auto interface to forever contract in minutes.

MS sells to insecurities of incompetent management and facilitates territory marking at the expense of governments and societies around the world for mega bucks. MCP, obvious as it is technically, also lets them plug a library into existing services for a quick upgrade then an atomized upsell directly to the chat interfaces of upper management.

Microsoft’s CEO has talked about his agent swarm. Much like RPA this woo appeals strongly to the barely technical.

Templates and templating languages are still a thing. Source generators are a thing. Languages that support macros exist. Metaprogramming is always an option. Systems that write systems…

If these AIs are so smart, why the giant LOCs?

Sure, it’s cheaper today than yesterday to write out boilerplate, but programming is about eliminating boilerplate and using more powerful abstractions. It’s easy to save time doing lots of repetitive nonsense, stopping the nonsense should be the point.

I find that technology really exciting. Partly because it’s a polished and comprehensive version of something I was implementing around my MCP cluster anyways.

Mostly, though, because it seems like we’re mere minutes away from having Star Trek style LCARS adaptable GUIs managed by an AI computer system simultaneously so smart it runs mission critical operations yet so dumb we have to remind it that we want our tea “hot” five times a day.

It’s happening. We’re gonna be living in the future!

No nulls, no nullability bombs.

Forcing devs to pre-fix/avoid bugs before the compiler will allow the app means the programs are more correct as a group.

Wrong, incomplete, insufficient, unhelpful, unimpressive, and dumb are all still very possible. But more correct than likely in looser systems.

> No nulls, no nullability bombs.

I hate this meme. Null indicates something. If you disallow null that same state gets encoded in some other way. And if you don't properly check for that state you get the exact same class of bug. The desirable type system feature here is the ability to statically verify that such a check has occurred every time a variable is accessed.

Another example is bounds checking. Languages that stash the array length somewhere and verify against it on access eliminate yet another class of bug without introducing any programmer overhead (although there generally is some runtime overhead).

The whole point of "no nullability bombs" is to make it obvious in the type system when the value might be not present, and force that to be handled.

Javascript:

  let x = foo();
  if (x.bar) { ... } // might blow up

Typescript:

  let x = foo(); // type of x is Foo | undefined
  if (x === undefined) { ...; return; } // I am forced to handle this
  if (x.bar) { ... } // this is now safe, as Typescript knows x can only be a Foo now

(Of course, languages like Rust do that cleaner, since they don't have to be backwards-compatible with old Javascript. But I'm using Typescript in hopes of a larger audience.)

Another red flag vis-a-vie energy source is ignoring hydro electric. High energy consumers and areas with a constant surplus of hydro are a good match. One of the new mega dams on Central Asia was restarted and funded primarily by an aluminium conglomerate - cheap and stable pricing at industrial scales.

This is why one of the two major Aluminum smelters is located in Washington. The economics of using hydropower to run the smelter are really good.

Amazon didn’t pay zero taxes, robbing the commons. Amazon engaged in trade and investment, taxed on all sides and at multiple points in the exchange of goods and services. Then Amazon invested their profits into further tax-creating transactions, reducing their tax burden that year.

When Amazon stopped investing and started extracting those profits everyone paid taxes on that giant money pile that wouldn’t exist without the investment. Every Amazon worker, CEO included, paid taxes all along. Amazon’s service providers and partners did. Amazon now does too, and the tax coffers have won big.

Taxation offsets from investments should be broadened (to individuals), not shamed.

Vibedetector

We need a service that rates vibe coding capabilities. A "vibe rater".

Bourdain didn’t initiate the cultural practice of going on safari and congratulating one’s self. The Michelin guide was founded in 1900.

Bourdains travels also weren’t the curated tourist jaunts you’re describing. They often showing the grim and lesser known sides of conflicts and situations while presenting genuine local cuisines. It’s what the unconcerned tourist aspire to, not what they do.

Or just hire people for your marketing team that have even a passing familiarity with web dev? They're not even that hard to find.

Keep those initial hires aboard and train up the rest. Get rid of the ones who don't want to learn. I mean really why do we try so hard to avoid bridging such simple knowledge gaps? It's not a big deal and we shouldn't shut people out of career development under all these obviously false excuses.

You are forgetting that the websites/CMS is often tool for the organization. It's not just about publishing the content. CMSes are used for writing and editing. Event spaces use their website for planning, chefs use it to generate printed menus.

Static site generators are good for some usecases but too little or too niche for most cases.

Whats with the git obsession?

Modern CMS workflows separate the content from the website code/app. The code is always version controlled and for content most CMSes have some sort of content versioning.

Customized, self-guided, tailor made kids content isn’t slop per se.

Colouring pages autogenerated for small kids is about as dangerous as the crayons involved.

Not slop, not unhealthy, not bad.