Author Archives: Jim Grisanzio

Unknown's avatar

About Jim Grisanzio

Software, Science, Geopolitics, Money

One Arm Dead Hang

I did it! One arm dead hang! 5 seconds each arm! Wild. And I didn’t rip my arm out of my shoulder in the process! It took two months of preparation and daily two-arm dead hangs at 60-90 seconds and progress seemed slow. And then today I just felt like it deserved a quick try. It was a huge leap forward going one arm at a time. Will build from here. Excellent.

UPDATE April 14, 2026: Got the one arm dead hang up to 15 seconds now. Progress!

No JavaOne 2026 Photos

I was at JavaOne 2026 in California last week. I participated onstage at the Community Keynote and also recorded some audio podcasts, which I’ll post over the next few months at Duke’s Corner. And since I’m on the team that produced the week-long event itself, I had many other duties to attend to throughout the conference as well. I’d say the Community Keynote took the most planning and implementation for me this year, where I hosted a short panel on the Java User Groups with some great JUG leaders. More on that in a later post, but here’s the live stream of the entire keynote that involved the entire team and community guests.

But one thing was missing from this event — I didn’t take a single photo! Usually, I take hundreds!

Instead, this year the Java Developer Relations team hired 3 photographers to shoot most of the event (except for the speaker dinner and the Day 0 events) plus a new feature for speaker headshots. And multiple team members showed up with cameras to shoot various bits as well. It felt weird to not have a camera glued to my face all day, to be honest. And I don’t know how I feel about it. On the one hand, shooting events has been a core part of my conference activities for a long time, but on the other hand it was nice to not have to lug around two big cameras and three lenses for 10 hours a day for 4 days straight and then have to edit hundreds of images afterwards. For example, last year I shot JavaOne 2025 all alone (including the speaker dinner and the Day 0 events), which was a challenge for sure. I didn’t shoot headshots because that does actually require another person and specific gear so we didn’t offer that service last year.

But the 600 images I did shoot took a few weeks to edit and publish. It was an enormous amount of work for one person that usually gets done via a small team of photographers and editors. But, hey, those images generated more than 75,000 views on Flickr so that’s cool. Now, it turned out that no one cared about that massive metric, but it’s surely meaningful to me. And the images are valuable to the Java developers who got them on Flickr via a Creative Commons license so they could be used elsewhere freely. That’s why I shot so many events over the years — to contribute the content to the developer community. Open Source conferences should generate Open Source content, right? It’s interesting that not everyone in the FOSS community agrees with that statement.

But this year? Nothing. I have no JavaOne 2026 photos to contribute. That was the plan, but I’ll have to digest that decision for a bit.

Anyway, here’s something I noticed by NOT shooting images this year. I gave myself time to breathe! Developer conferences are challenging to manage under the best of circumstances. You can easily grind yourself into dust in no time flat working 12 hour days on site following months of planning. I didn’t do that this year. In fact, I intentionally didn’t even attend all of the events throughout the week but instead chose to go back to my room at times to rest. I could have spent the extra time recording dozens of podcasts but I didn’t do that either. Instead, I recorded 6, which is a perfectly reasonable number. I did, however, talk to as many developers as I could find. Just hallway conversations. And that was a new exercise for me because in the past I used the camera to engage people. This year, it was just me. And I really loved it. I got to know many more people this way since I was more present in every moment. I was there to talk to you, not shoot your photo. The whole thing felt different.

So, it was a good event generally. I may implement this system in the future and just leave the photography behind at this point. I’ve shot about 100,000 images at events since 2000 so maybe that’s enough. Maybe it’s time to move on.

Japan Expands with Nuclear

Joint Announcement on the Japan-U.S. Strategic Investment

It seems Japan is investing 40 billion dollars in small modular nuclear reactors through joint projects with the United States. The recent plan marks a shift back toward nuclear technology to support economic expansion while some nations in Europe continue to deindustrialize. Small Modular Reactors (SMRs) are also necessary to support rapidly rising electricity demands required to implement new and massive Cloud and AI data centers. And by working with the United States, Japan is strengthening its role in next generation reactor technology, which may be surprising given that the nation suffered substantially from the 2011 earthquake and Fukushima nuclear accident.

The announcement also helps move SMRs from early development into real world deployment. This effort could shape global energy strategy for decades and enable new opportunities for economic development for hundreds of millions, even billions, of people. Imagine all the nations around the world wrecked from hundreds of years of colonization now getting badly needed, unlimited, reliable power. It’s time to build.

Cal Newport — In Defense of Thinking

From Cal Newport in the NYT : “The problems I focused on in Deep Work, and in my writing since, have been getting steadily worse. In 2016 my main concern was helping people find enough free time for deep work. Today I think we’re rapidly losing the ability to think deeply at all, regardless of how much space we can find in our schedules for these efforts.”

So, it’s getting worse. Fine. That only represents more of an opportunity for those who can leverage emerging productivity tools to implement stuff while at the same time master the ability to master deep focus to create stuff. I’ll take it.

In Defense of Thinking
NYT Opinion Guest Essay There’s a Good Reason You Can’t Concentrate
The Deep Life
Deep Work

Bob Treacy: From the Factory Floor to Harvard and 30 Years of Java

Duke’s Corner Java Podcast, March 15, 2026 — Bob Treacy: From the Factory Floor to Harvard and 30 Years of Java

Bob Treacy started his career as a union steward on the factory floor at GE Aircraft Engines. After earning a BS and MS in Computer Science from Boston University while also raising a family, he jumped into software, never looked back, and remains at the leading edge of Java and AI today. He picked up Java in the summer of 1995 at a training session in New York, and the language has been central to his work ever since. Today he is Principal Software Architect and Data Engineer at Harvard’s Institute for Quantitative Social Science, and he has attended more than 20 JavaOne conferences, which is most of Java’s lifespan.

Getting to all those JavaOne events has always been non-negotiable. “Every job I’ve ever gone to, one of the things I demand is that I be able to go to conferences like JavaOne.” The reason, he says, is simple: “It brings a lot of different perspectives, sharing experiences, learning from each other, and just a great group of people.”

At JavaOne 2026 he’ll present work from Harvard’s Dataverse project, an open source platform for preserving and sharing research data. The problem he is solving is straightforward but persistent because researchers treat the repository like a simple archive and skip the metadata that makes their datasets discoverable. His solution uses LLM embeddings and a graph database to compare new dataset descriptions against existing ones and recommend subject categories automatically.

The conversation goes well beyond his upcoming JavaOne session itself. Bob lived Java’s entire evolution from the rough early days of applets through HotSpot, modularity, and the modern work on GPU access via Project Babylon and the Foreign Function and Memory API. On AI, he says that “I think there has to be a human in the loop.” He sees LLMs as causal models, not reasoning systems. “Given these words that came before, what’s the next word going to be? That’s not really intelligence. I don’t totally buy some of the narratives that are out there about AGI.” His advice to students is equally grounded in simplicity. He advises students to learn the code, but spend more time understanding how large systems work together. As he puts it, “just doing pure coding” is no longer enough.

Bob Tracey: LinkedIn | Jim Grisanzio: LinkedIn, X/Twitter

OpenSolaris History on Grokipedia

As a test, I recently requested that Grokipedia update its page on OpenSolaris to include the source code release history I kept while I was the community manager. There were over 80 releases of source code, entire projects, and technical documentation during the five years of the project. I kept the history here. Anyway, I submitted the request to Grokipedia, and a few hours later the page was updated. Just like magic! That’s pretty much impossible with Wikipedia since I’m not one of their chosen editors. In fact, many years ago I tried to make changes to pages on Wikipedia and they were reversed seconds later. So, good on Grokipedia. I’ve long since given up on Wikipedia so it’s great that Grok is moving forward with a new community-driven encyclopedia.

The Pentagon Pulls the Plug on Anthropic

War with Iran + Pentagon vs Anthropic with Under Secretary of War Emil Michael — The All In Podcast

Emil Michael came into his role as Under Secretary of War last August and did what any good lawyer would do right away. He read the contracts! But what he found surprised him. And that led to a major dispute between Anthropic and the United States government that blew up in the media last weekend.

Part of the backstory is how Anthropic, one of the top AI companies in the world, got so embedded in the government in the first place. The Biden administration’s executive order on AI effectively limited compute capacity for most companies while grandfathering in a small number of selected winners. Anthropic was one of them. From there, the company executed a smart enterprise sales strategy and moved their software and engineers into the most sensitive parts of the government. This is a common strategy for tech firms selling into the largest customer on Earth.

So, by the time Michael arrived, Anthropic wasn’t just a vendor. It was woven into the daily workflows of some of the country’s most critical military commands including Central Command, the Indo-Pacific Command, and several intelligence departments. That history matters now because, as Michael acknowledged, untangling a deeply embedded technology partner is far harder than simply switching vendors. The other AI companies haven’t built out that kind of government infrastructure yet. They’re capable on the model side, but they have to catch up on everything else, which they certainly will do in short order.

But buried in Anthropic’s terms of service were restrictions that, from Michael’s perspective, made the software nearly unusable for its intended purpose — to plan, fight, and win wars.

“You can’t use them to plan a kinetic strike. You can’t use their AI model to move a satellite. You can’t do a war game scenario with it,” Michael explained on the All In Podcast. The Department of War, as he noted repeatedly, is pretty clearly stated right in the name. War.

What followed was three months of laborious negotiations arguing over scenario after scenario involving various military operations. Anthropic would grant an exception here and another one there. But Michael needed something broader. The military cannot predict every situation it will face in real time and into the future, and an AI model that requires pre-approved use cases is not a reliable operational tool. In fact, it would compromise national security and potentially endanger troops in the field. Instead, he pushed for a single standard — all lawful use — that he could apply to all AI vendors.

Then came the moment that accelerated the conflict. After the Venezuela mission, an Anthropic executive contacted Palantir, the prime contractor implementing Anthropic’s technology, and asked whether their software had been used in the raid. Since that information is classified, Palantir informed Michael. The implication was clear. If the answer were yes then Anthropic might consider that a terms of service violation and pull their software.

“What if the balloon’s going up at that moment and it’s like a decisive action we have to take,” Michael said. “I’m not going to call you to do something. It’s like not rational.” That phone call reference wasn’t a hypothetical situation. Michale said that Anthropic CEO Dario Amodei actually told him durning negotiations to just call him when issues came up. From Michael’s perspective, though, that’s obviously not a reasonable solution under the circumstances, especially involving combat and national security.

That conversation grew to a breaking point. Michael went to Secretary of War Pete Hegseth, who demanded that Anthropic lift the restrictions. The company refused. So, Anthropic was formally designated a supply chain risk, the first American company ever to receive that designation from the government. Generally, that’s reserved for enemies. As a result, the $200 million contract was cancelled. Now it’s Michael’s job to unwind Anthropic from their positions throughout the government.

The broader issue here goes well beyond the Pentagon. As Chamath Palihapitiya argued on the podcast, what Anthropic demonstrated is that any sufficiently powerful AI provider can, at any moment, change its terms of service based on the internal values of its employees, which seems to be an issue for this company. That is a significant business risk for governments, corporations, and anyone else who has built critical workflows on top of a single AI model. “It’s deplatforming times a thousand,” he said.

The situation is still fresh. But for now, the ball is in Dario Amodei’s court. Michael said plainly what he has always wanted, which is a reliable partner willing to support lawful use without requiring a phone call every time something comes up. That’s not an unreasonable ask. And it’s the same standard that Google, Grok, and OpenAI have all moved toward without any drama. Anthropic chose a different path. And in doing so, the company may have handed its competitors a significant opening inside massive government accounts it spent years cultivating.

Anthropic’s revenue and valuation have both been growing rapidly. But will that trend continue? It’s well known that AI engineers and advanced researchers will only stay where the work is interesting and the money is flowing freely. Future contracts will go where the terms make sense for the government. How Amodei responds now, and how quickly, will reveal whether Anthropic is a principled company or simply a difficult one with a political agenda.

AI Meets the Department of War

Ben Thompson’s article at Stratechery starts with a power politics view of international law. It doesn’t really exist, he says, because no one can enforce it. Might makes right. The U.S. bombed Iran and that settled the debate. That’s how power works in the world. Always has.

From there, Thompson pivots to Anthropic, which recently refused demands from the Department of War to lift restrictions in the model’s terms of use. Dario Amodei, CEO at Anthropic, said the company would not support mass domestic surveillance or fully autonomous weapons. The DOD responded by threatening to designate Anthropic a supply chain risk, which is a label reserved for foreign adversaries.

Thompson’s analysis here is blunt. Amodei has publicly compared advanced AI chips to nuclear weapons. So Thompson takes him at his word and extends the logic to its natural conclusion. If AI is truly that powerful, which remains to be seen at present, then a private company that controls it and seeks independence from the military will run directly into the U.S. government. In other words, this isn’t just a vendor dispute. It’s a national security issue. Anthropic doesn’t take that view, obviously. The problem is that the U.S. government has the guns.

The conclusion Thompson comes to is binary. Either Anthropic accepts a subordinate role to elected government authorities, or the U.S. government will eventually destroy or remove it, which they’ve done before throughout history. Thompson isn’t supporting that outcome, of course. But although he seems to lean to Anthropic’s side of the debate on domestic surveillance his analysis is comprehensive and more than fair. He also argues that Anthropic’s insistence on controlling military decisions is itself fundamentally misaligned with how power operates in the world. He reminds us of this reality right up top in his piece with a quote from Pericles: “Just because you do not take an interest in politics doesn’t mean politics won’t take an interest in you.” He’s correct with that bit.

Here’s Ben Thompson’s original article on Anthropic:
Anthropic and Alignment

Here’s Ben Thompson on the A16z Podcast talking about his article:
Ben Thompson: Anthropic, the Pentagon, and the Limits of Private Power

Here’s much more on the issue from the All In Podcast but from the perspective of the Department of War, which is substantially different:
Pentagon vs Anthropic: Why Anthropic was labeled a supply-chain risk