My new favorite track. #ai #gamer #rock @suno suno.com/s/dzbKMh7J2xAT3WH3

Saturday night fun with @Pebble 's new firmware dev kit. Thanks Eric and co!

I just watched @theo new video on why MCP sucks. So I thought I would explain why MCP actually doesn't suck. Protocols only exist to connect two distinct systems in a standard way. An LLM can only perform actions through tool calling. Tool calling is the standard interface. If I'm writing an application that uses an LLM and wishes to do tool calling, I don't need MCP. The code that calls the LLM can just implement the tool calling interface and be done with it. This is essentially theos use case and probably why he doesnt articulate MCP well. If you want the tool implementation to be independent of the code calling an LLM this is where a protocol comes in. Prior to MCP most approaches to independently distribute tools focus on language frameworks like langchain. No language independent way existed such that a LLM client in python could connect to a say a Java tool. But furthermore no standard way existed such that one could expose a tool publicly in a secure multi-tenant fashion. MCP solves this problem. And despite what @theo stated, MCP does define auth, it's one of the core features of the spec (yay OAuth 2.1, DCR,and DCIM 😭) If you use MCP for 1 tool or 1000 tools, it still has value. The issue most people complain about today is that there are too many tools or poorly defined tools. This is an issue independent of MCP and where a lot of exciting work like code mode is being done to address it. But there's other progressive discovery methods that exist, such as the implementations of ChatGPT apps, which is based on MCP, or Claude skills. Code mode, or progressive discovery don't remove the need for MCP, they just provide a meta approach to deal with tool scalability issues but can still be implemented with MCP. One could possibly make the argument that we just don't need to ship tools as systems of their own, but people are doing it and getting value out of it, so 🤷‍♂️

📱 [Trump T1 Phone: “Patriotic Marketing” Disguised as Made-in-USA, But Actually Made in China] Trump’s newly released “patriotic smartphone,” the T1, claims to be Made in the USA, but numerous details suggest it’s merely a rebranded Chinese Android phone: ⸻ 🔍 Camera Layout: The rear camera module of the T1 closely resembles that of the UMIDIGI A15 Ultra, a Chinese-brand phone. It features a 50MP main camera paired with two 2MP budget sensors—far below the flashy specs used in marketing. 🕳️ Front Camera Punch-Hole Position: The 6.78” AMOLED screen features a centered punch-hole front camera, nearly identical to those found on mid-tier Chinese models like the UMIDIGI A15 Ultra and Doogee V30. ⚙️ Matching Specs: T1 claims to offer 12GB RAM 256GB storage, Android 15, Type-C port, and a 5000mAh battery—specs that mirror the UMIDIGI A15 Ultra. However, even the front camera seems to be a downgraded version. 🧾 Origin Red Flags: There’s no transparent FCC registration or credible manufacturer information. The “Made in USA” label is likely limited to final packaging or casing assembly. Core components—motherboard, screen, battery—are almost certainly from China. Most probable OEMs include Chinese manufacturers like UMIDIGI (Shenzhen Youmi), DOOGEE (Shenzhen Doogee), or Infinix (Transsion Holdings). Once FCC filings are public, these links may be confirmed. 🇨🇳 Conclusion: The carrier-locked version of the UMIDIGI A15 Ultra sells for around $249 overseas, while the Trump T1 is priced at $499. This is a low-end Chinese Android phone in disguise, repackaged to appear “American-made” and marketed to exploit nationalist sentiment and cash in on MAGA loyalty.

Videos are up for this year's DevOpsDays Birmingham, AL. Check them out: youtube.com/playlist?list=PL…

I put together my thoughts on enterprise consulting in to a LinkedIn article: linkedin.com/pulse/from-prof…

Working from the hanger this afternoon @SDSpaceland #houston. Also, my first diveflow jump. 🤞🪂

Not sure I am prepared for the wild ride that's about to be the next two weeks. But... LFG! #movingtotexas #visitingcheyenne

W00t, first power loss after which my current home network came back up without intervention. Now for the move ... 🤦

Ever look up some docs and ask yourself "Who is the idiot that wrote this?!" Today, that was me.🤦

If you want to get your tools in front of DevOps practitioners from Huntsville, come join us at @DevOpsDaysBham as a sponsor in August. As the closest DoD conference we get to welcome our Defense and Aerospace industry family every year.😁

It's official, I have no gasoline for Monday Morning Gasoline. Sad to see another project go by the wayside, it follows me shuttering BSI.news earlier this year. Sizing things down and preparing for the move.

I maybe a little partial but fluid based cooling is the way to go. Lather up those racks in some oil and call it a day... right?

On today's" Things That Really Grind My Gears": Uploading isos at cable rates.

When your datacenter tech hooks up your test node. @VMAccel #justalittleram #awittlebittyserver

I notice lately, I am more often the critic than the enthusiast. Something to work on.