Tag Archives: Communities

Cluetrain Yesterday and Today

When I lived in California in late 2000 I read probably the best book on modern communications ever written: The Cluetrain Manifesto by Rick Levine, Christopher Locke, Doc Searls, and David Weinberger. The authors actually teased the book on the web in their 95 Theses in 1999, so we all knew what was coming would be equally outrageous. Couldn’t wait.

Back then I worked in Cupertino, and many times I’d take breaks and walk across the street from the office to get some coffee and flip through the pages. I loved it. It represented a radical departure in marketing and communications at the time because seemed obviously influenced by developers in the rapidly growing Free and Open Source Software movement (FOSS). I was already familiar with most of the topics in Cluetrain because I worked at Sun Microsystems and mixed with FOSS engineers every day. Still, it was cool to see the concepts applied to marketing where these ideas were totally unknown.

Cluetrain made bold predictions about markets becoming conversations, about authentic voice displacing canned corporate messaging, and about employees and customers breaking free from rigid command and control structures. We read it widely at Sun, especially those of us managing FOSS projects. Back then Sun was opening millions of lines of code, so the book gave us useful language as we built projects and engaged development communities. It also came in handy for dealing with the media, which was my primary job at the time. Cluetrain also fit Sun’s culture perfectly because the place seemed at times more like a frat house than a corporation.

The Prediction: Markets Are Conversations

The Cluetrain Manifesto’s central argument was clear. Mass media had interrupted human conversation and turned people into passive consumers and markets into targets. Even within Sun’s generally open culture, there were still power centers in marketing and product development talking in terms of “targeting” the media, developers, and customers. That positioning drove me nuts because the engineers never spoke that way. Cluetrain argued that the Internet would reverse that old paradigm because people could now talk directly to each other about products, communities, and companies across traditionally closed corporate firewalls.

The authors based their conclusions on their own observations. They showed how customers were gathering in online forums to compare notes, share experiences, and help each other get things done. Engineers at companies could openly explain their software to peers in the community and to potential customers without a corporate communications department in between. Companies that tried to control these conversations through legal threats or PR spin got mocked online, often without realizing it, so it fell to people like me to explain what was happening to teams internally. That was a painful process, I can assure you. The pushback from the more conservative teams was significant. But I never had to justify the book’s ideas to developers because in the FOSS community open communication was just considered normal.

But Cluetrain wasn’t simply calling for friendlier or more open marketing process. It was challenging the idea that companies should attempt to control the conversation about them. That was a wasted opportunity in the Cluetrain paradigm. The people building the products always knew more than the marketing department, and the customers using those products often knew things the company itself didn’t. The Internet let those conversations thrive at a scale that had never existed before, and it didn’t require everyone to agree to the latest message. In fact, disagreement was generally part of the value. People could challenge companies publicly and develop their own understanding of a product without waiting for the officially approved marketing campaign.

What Actually Happened

The first part of the prediction proved accurate. Conversations exploded online. Developer interactions thrived. Customer and developer reviews became crucial to purchasing decisions. Social media finally gave employees and customers a public voice, and many companies encouraged this change. For example, Sun and Microsoft were among the first large software companies to build blogging platforms for employees to talk with outside communities. Development engineers usually led the way, and within a few years Sun had more than two thousand employees blogging and talking to whoever they needed to talk to in order to get their jobs done. That openness was a real relief from the constraints of corporate life, and for a while the old, one-way broadcast model lost some of its grip. We used to call that old broadcast strategy “megaphone marketing” at Sun, but we were now in a many-to-many world. It was cool.

But the manifesto underestimated how quickly new gatekeepers would emerge, and how differently they would operate. The authors understood the Internet would break down old barriers between companies and their audiences, but they couldn’t have anticipated that the new communication systems would themselves become enormous businesses with their own tools and economic incentives.

Facebook, Twitter, Instagram, YouTube, and other platforms created spaces for open conversation, but they also monetized it. Attention became a product. Personal data became even more valuable than before. Algorithms became necessary to sort through the volume, but those same algorithms also began deciding which conversations got seen. A thoughtful explanation doesn’t necessarily earn more attention than an outrageous claim, and content that produces a strong emotional reaction can be worth much more to a platform than content that’s simply accurate or understated. And we all began to see this in our social feeds. A casual peek at a colleague’s screen would reveal that their online conversations showed an entirely different world based on their preferences that were amplified by the platform’s algorithms.

Bots and fake accounts made it worse and the line between an authentic participant and a manufactured one grew harder to see. And a well funded campaign could manufacture the appearance of agreement without any real support behind it. But developers could always see this. Most early FOSS projects ran on Mailman lists, so those discussions among engineers largely escaped the corporate swamp for years. Over time, though, as more engineers drifted onto social media, they were pulled into the mess too. The Internet didn’t eliminate gatekeepers. It built new ones with far more precision than the old media ever had. Also, whereas the old media tended to be centralized, the new one was atomized and embedded everywhere.

The Transformation of Corporate Communication

Companies adapted to these open changes quickly. They hired social media managers and community managers, built brand accounts, and encouraged employees to act as ambassadors. The language of Cluetrain worked its way into corporate communications and marketing meetings, which made it feel like the old model was changing. But something got lost along the way.

The manifesto called for people to speak from a genuine passion and their firsthand knowledge from working within an open community. However, what companies built instead was a new form of managed authenticity. Posts were getting written by communications teams and checked by legal before going out. Influencers were paid to look organic. Employees were encouraged to speak publicly while at the same time getting detailed guidance on exactly what they could and couldn’t say. Some companies appeared to be part of the conversation while also working to keep as much of the control as possible.

But other companies were more genuine about it. They admitted mistakes and let employees talk freely and participate in the communities. At Sun we aired plenty of our dirty laundry in public blogs, and the community noticed that and appreciated it. Several Microsoft bloggers did the same. But those were exceptions rather than the rule, and over time most companies learned to fold blogs and social media into the same communications machine they’d always run. Once authenticity became something a company could measure and manage, it turned into just another item in the corporate toolkit. It was wild to see people in marketing meetings starting to borrow the language engineers had used for years, at least on a surface level.

The Complexity of Authentic Voice

The manifesto also underestimated how hard an authentic voice is to maintain inside an large organization. It’s easy to say employees should speak honestly. It’s harder when those employees have managers, legal departments, and reasonable worries about what happens if they say the wrong thing publicly. People are complicated. They carry competing loyalties, worry about their careers, get tired, make mistakes, and sometimes just disagree with the company they work for.

Also, authentic doesn’t automatically mean good, either. A customer’s honest opinion can be unreasonable. An employee’s honest take can rest on a bias they don’t even recognize. A developer can be technically brilliant and still be a troll. FOSS communities learned this a long time ago, which is why so many projects eventually had to write and enforce conduct policies. Openness alone was never enough, especially when systems scale.

The manifesto also didn’t foresee how authenticity itself would become a commodity. Brands hire consultants to develop an authentic voice. Corporations spend real money trying to appear genuine, and influencers get paid to look like ordinary people making ordinary recommendations. As a result, people learned to perform realness the way they once performed professionalism, and once everyone is trying to appear authentic, authenticity just becomes another style of engagement. This is just a normal process of how organizations full of complicated people operate. It’s to be expected.

What the Manifesto Got Right, and What It Missed

Despite these blind spots, Cluetrain identified something real about how business would change. Markets did become more transparent, and information asymmetries did shrink. Customers and development communities gained real leverage over corporations. Microsoft’s own path from calling Linux a cancer to actively engaging open source projects is a good example. Companies that ignored what customers were saying suffered brand damage faster than they would have in the old broadcast era. And the hyperlinked organization the authors described turned out to be real to a certain degree. Work became more distributed. Information stopped moving strictly through the hierarchy. A developer could talk directly with a customer, and an employee could find the person who knew how to solve a problem without asking permission to cross multiple layers of management. Some managers didn’t love this, of course, but they couldn’t really stop it. Many even saw Cluetrain as an opportunity for career advancement and skill development.

What the authors missed, though, was that they underestimated how well old power would simply adapt. They believed the Internet would make hierarchy less important, and in some ways it did, but hierarchy didn’t disappear. It mostly moved online. They also underestimated scale. Small communities can sustain honest conversation because people get to know each other quickly. They learn who is helpful, who is selling, and who has a real history in the project. That doesn’t necessarily hold once a platform reaches millions or billions of people, though. Context breaks down, algorithms fill the gap by deciding which participants and messages get seen, and gaming becomes easier.

They didn’t foresee algorithmic curation either. The Internet made more information available, but that didn’t mean people would actually see more of it. Two people can use the same platform and end up with entirely different views of what’s happening because the platform is showing each of them a different slice of reality. And they didn’t anticipate how concentrated the new gatekeepers would become. All these years later handful of companies now provide the infrastructure most online conversation runs through. They set the rules, run the algorithms, and collect the data. The promise of decentralized conversation gave way to a new kind of centralized control.

The AI Complication

Then we got artificial intelligence, which is where Cluetrain gets interesting again. The authors believed people could tell the difference between corporate language and the way real people actually talk. That held up fine in 1999. It’s much harder to claim today, though.

AI can write a customer review, draft a social post, answer a support question, or generate an image that looks real. And it can do all of this while maintaining a consistent personality for years. Now, fake reviews and manufactured enthusiasm existed long before AI. What’s changed most recently is how cheap, easy, and fast it is to produce content at scale, and that undercuts one of the manifesto’s core assumptions. If authentic voice is what matters, but we can’t reliably tell which voices are authentic, what happens to the conversation? We used to be able to easily spot corporate messaging, but it’s getting harder and harder to spot AI messaging as those systems become pervasive.

It gets more interesting once you stop thinking about individual fake messages and start thinking about participants themselves. An AI system can answer questions, defend a company, criticize a competitor, and take part in a developer community to the point where people start developing relationships with it. But human reputation develops through repeated interactions where you have something at stake and have to live with what you said. But now an AI agent can simulate the pattern of that outcome without having any of the human substance behind it. Its apparent expertise actually came from a model trained on other people’s work, and its apparent reputation really belongs to whoever operates it either at the LLM or the harness level. That’s a bigger challenge to Cluetrain than simply noting that AI can write marketing copy.

Automation Is Not AI

There’s a distinction worth making here because it sometimes gets lost in many discussions about AI. Automation has been removing humans from transactions for decades. A vending machine does it. An ATM does it. A self checkout does it. None of those systems need AI at all.

I was reminded of this recently while clothes shopping in Tokyo. I expected a clerk to check each item, scan or key in the price, and fold everything neatly for me That’s usually how it goes here. This is Japan, after all. Direct human service matters. A lot. Instead, I dumped a tangled pile of ten items into a bin, and the system identified everything immediately, listed everything on a screen, and let me pay with a quick tap of my card (I love the security on that last part). No human involved anywhere in the process, and no bar codes for me to scan myself. It just worked. What matters here is that this kind of checkout doesn’t need AI to be impressive. RFID (Radio Frequency Identification) can identify a pile of products without anyone scanning them one by one, which is what makes the example useful beyond AI specifically. Automation has been removing people from physical transactions for a long time. We’re all used to it now even though we may not like it. This may help explain why people are so sensitive about AI because AI now extends that same trend but into our conversations. Now an AI agent can replace the conversation itself.

Where Cluetrain Still Works

I still see the original Cluetrain principles working in the FOSS projects I’m part of, though. A developer asks a question on a mailing list, and other developers respond with real knowledge and no filter. They argue, share code, make mistakes, correct each other, and build things together because there’s context and an expectation of openness and credibility. People develop reputations in these spaces. You learn who has expertise, who tends to cause trouble, and who is genuinely trying to help. That history and experience over time gives the conversation weight that a comment in a text box on a website can’t create on its own.

I’d revise one part of the usual argument here, though. It’s not quite right to say Cluetrain works at human scale and fails at platform scale, since some gigantic communities function well and some tiny ones are dysfunctional. What actually matters is context, reputation, shared purpose, and accountability. A local bookstore can have those things. So can a software consultancy, a FOSS project, or a single team inside a much larger company. But Cluetrain breaks down once a conversation gets so large and impersonal that participants lose the ability to build context and reputation, while at the same time the platform itself gains more say over what everyone sees.

What We Need Now

The Internet did change business, and authentic conversations did become more important. But the story didn’t unfold as cleanly as Cluetrain predicted. Markets became conversations, sure, but many of those conversations are now mediated by platforms with their own economic incentives. Our content is now run through algorithms built to hold our attention, and our conversations are increasingly populated by AI that can imitate humans well enough to fool most people who aren’t looking closely.

That raises real questions. Does it matter whether the voice answering you is human as long as it gives you what you need? Many times it doesn’t matter. And that’s fine. But in most cases, people tend to seek human interactions. The real question is how markets will function at scale if we really can’t tell who, or what, we’re talking to. We don’t know the answers yet since all of this is still emerging. Some companies are being transparent about their use of AI and are disclosing when people are talking to a bot. Some companies are now saying that AI is just a tool to augment humans rather than a replacement for humans. Others, however, will remain less transparent about their use of AI simply because the incentive to cut human involvement is massive. Those companies seem intent on pushing the narrative that AI will just replace people in the future.

I don’t think AI will destroy human conversation or replace people entirely. Markets are changing, that’s true, and many people will be displaced, but that’s been happening forever. Nevertheless, People will keep seeking relationships, expertise, and direct contact with other people. That’s just an innate human characteristic. And the more artificial our digital environments become, the more valuable genuine interactions will get. That may be part of why live conferences still draw big crowds. When you’re standing in a room talking to someone, you don’t have to wonder if an algorithm or someone bot produced the experience. It’s just real.

That’s what Cluetrain ultimately got right. Markets are conversations because markets are made of people. The Internet made those conversations possible at a scale no one could have imagined in 1999, but it also built new gatekeepers, new incentives, and new questions about who or what we’re actually talking to. I still talk about Cluetrain at developer conferences, even though almost nobody in the room has heard of it anymore. The book may be mostly forgotten, but the basic idea holds. We should still want knowledgeable people talking directly with customers and developers talking directly with their peers. And we should still want communities where reputation gets earned through real contribution rather than assigned by algorithms that can be gamed.

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, since I’ve shot so many events in the past. 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. And there was no room in the budget to hire a photographer to shoot headshots.

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 80,000 views on Flickr so that’s cool and who knows how many views on various social media sites. Now, it turned out that no one at Oracle cared about that massive metric, but it’s surely substantial and 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 personally have no JavaOne 2026 photos to contribute. That was the plan for this year, of course, but I’ll have to digest that decision for a bit. But what about the many hundreds of images that were shot by the three professional photographers at JavaOne 2026 funded by Oracle? Nothing. I can’t find a single image online from the event. No websites. No social media. Nothing on Flickr under a Creative Commons license. One of the arguments I gave to my team in 2025 was that whenever Oracle hires professional photographers for events the images simply never see the light of day. What’s the point of just dumping them in some corporate database to rot over time behind the firewall? So, let me shoot the event instead so at least we have something to give to the community and for our own use on social as well. Sure, Oracle does post a few tiny low resolution images from their events on a few corporate websites for a short period of time, but even those vanish in mere weeks. Such a dumb waste of resources. And such a wasted opportunity to help build the community by offering massive numbers of free high resolution images from the world’s premier developer event. Sad.

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. But 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 hotel 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. The camera was always my crutch. It was always my filter. This year, though, it was just me. I wasn’t that nervous 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 just move on.

Marit van Dijk and Anton Arhipov: 25 Years of IntelliJ IDEA

Marit van Dijk and Anton Arhipov: 25 Years of IntelliJ IDEA | Duke’s Corner Java Podcast | January 29, 2026

This is the second in a short series of speaker profiles for JavaOne 2026 in Redwood Shores, California, March 17-19. Get early bird pricing until February 9, and for a limited time, take advantage of a $100 discount by using this code at checkout: J12026IJN100.

JavaOne: Register | Sessions

In this conversation, Jim Grisanzio from Java Developer Relations talks with developer advocates Marit van Dijk and Anton Arhipov from JetBrains about the 25th anniversary of IntelliJ IDEA, the latest features of the IDE, Anton’s upcoming session at JavaOne in March, and their perspectives on JavaOne as the premier conference for Java developers.

25 Years of IntelliJ IDEA

Just as Java turned 30 this year, IntelliJ IDEA is now 25 years young! Not every technology survives that long, and even fewer thrive while doing it. But both Java and IntelliJ IDEA are doing just that. The secret to this longevity for IntelliJ IDEA, according to Marit van Dijk and Anton Arhipov, comes down to something simple but demanding — staying current with the Java ecosystem and engaging the massive Java development community around the world. The main reason for their success is the huge effort engineered into the platform to produce the technologies that developers need while at the same time staying with all the bleeding edge stuff happening inside the Java community.

This commitment reaches beyond just supporting new Java versions. The IntelliJ IDEA team works on preview features even though specifications sometimes change during the preview process. When Oracle moved to a six-month release cycle for OpenJDK about eight years ago, IntelliJ adapted smoothly since their teams were already involved with the OpenJDK community. Marit says that new release cycle actually streamlined their work. They already knew about preview features and could start developing support upfront, not at the very last moment. This let them iterate alongside the community rather than chasing after it.

The company also collaborates directly with other community members — such as framework developers, build tool teams at Maven and Gradle, and even Google — to implement best practices straight into the IDE. Maven 4 is not even released yet, but IntelliJ already has support ready with migration features to help developers make the transition. Anton says that this effort means that support is not only working with the new version of a technology but also being smart about how you use it. The IDE catches outdated patterns and deprecated APIs and also offers quick fixes to migrate code with a single keystroke.

First and Lasting Impressions

Both Marit and Anton started working at JetBrains years after they had already become devoted IntelliJ users. Their first impressions of the IDE moved them deeply and remain with them today.

For Anton, his first reaction to using IntelliJ IDEA was immediate. “In one word, wow, this is smart. This is an IDE that understands code.”  That intelligence in the software became the foundation of his relationship with the technology.

Marit had a similar experience when she switched to IntelliJ IDEA. She had used other IDEs before and they were perfectly fine, but IntelliJ seemed different. “I found that it was actively helpful with the code inspections and quick fixes and helping me when my code didn’t compile or preventing me from making mistakes. And I was sad that I didn’t switch earlier, like years earlier. And I’ve been raving about it ever since. And now they pay me to do that. So, you know, everybody wins.”

AI and the Future of Development

As usual in these conversation, we turned to artificial intelligence and its growing role in software development. Anton will explore this topic in depth at his JavaOne session titled “Spec-Driven Development With AI Agents: From High-Level Requirements to Working Software.” Everyone knows that the AI landscape is changing fast, but things are actually getting simpler, Anton says. Developers can now get better results with less effort and less complex workflows using AI agents. Models are improving at guessing developer intent and reducing the need for careful constraint-heavy prompting.

But Anton sets realistic expectations about AI. When asked whether his session targets junior or senior developers, he says that “we are all juniors in this regard.” The field is so new that nobody can claim years of expertise with AI development tools.

Marit emphasizes another crucial principle about AI-generated code. “You are still responsible for the code,” whether you write it or an agent writes it. It has your name on it. AI does not diminish developer accountability or the need for developers to remain highly skilled in their craft.

Anton adds another dimension about integrating AI with development tools. “AI without the IDE is kind of unreliable, but the IDE without AI is unproductive.” The key, he says, is to fuse these things together leveraging the benefits of both for better productivity. The context the IDE provides and its understanding of your project structure and dependencies makes AI suggestions more relevant and actionable.

JavaOne: Where the Community Comes Together

Anton will be presenting at JavaOne 2026 in March, and both he and Marit shared their perspectives on what makes the conference special.

For Marit, JavaOne has always been unique. The “who’s who of Java” will be there, she says. Last year’s conference-ending “Meet the Architects” panel particularly stood out. The audience could ask Oracle Java architects basically everything about Java for over an hour. This kind of access to the core engineers building and shaping the future of the language is something you would not normally get at any other conference.

Anton shares his view that JavaOne has always been the conference to get all the news about Java. He has always viewed the event as the place where you get condensed information about what’s going on with Java all in one place — the language, the platform, the standards, the frameworks, and the community.

Community and Looking Forward

Marit and Anton maintain close relationships with the developer community through conferences and Java User Groups. Marit says that they have many JUGs in the Netherlands, and many of them invite her to come and speak at their meetups throughout the year. Also, when they travel somewhere for a conference, they look for opportunities to combine that trip with local JUGs to speak there and connect with people. This direct engagement with the open Java community lets Marit and Anton talk to developers directly, see how they can help them better, understand what developers are struggling with, and take that feedback back to the engineering teams. The same authenticity extends to how JetBrains approaches IntelliJ development. The engineering team maintains close relationships with framework developers and library maintainers and OpenJDK to ensure that when new versions release, IntelliJ users have good support from day one.

As IntelliJ IDEA celebrates 25 years, the development continues. They keep releasing new features with every version: the Spring Debugger that helps developers understand their Spring projects at runtime, Command Completion that enables developers to perform commands without memorizing shortcuts, and more. The anniversary celebrations for the teams have included parties with cakes featuring old logos, a game plugin that lets developers play video games while AI generates their code, and social media campaigns engaging the global community. For developers curious about IntelliJ IDEA, Marit and Anton encourage people to subscribe to the JetBrains YouTube channel where they regularly produce videos explaining new features.

This 25-year milestone represents more than just history. It represents an ongoing commitment to understand code, support developers, build the Java community, and evolve alongside the entire ecosystem. This pattern is pervasive among Java developers and also the many companies offering developers advanced tools. The smart IDE that so impressed Anton and Marit years ago continues to get smarter — right along with many other tools and technologies that are growing as a result of the Java platform itself.

Anton Arhipov: X , BlueSky, Linkedin
Marit van Dijk: Website, Linkedin, BlueSky, X 
Jim Grisanzio: X, Linkedin
Duke’s Corner Java Podcast: Substack
Oracle Java Developer Relations: Inside.java, Dev.Java, Learn.java
Topics Discussed: IntelliJ IDEA 25th Birthday, The Java Dukes, What’s new in IntelliJ IDEA 2025, Spring Debugger, Command Completion

Duke's Corner Java Podcast
Duke’s Corner Podcast

Spamming the Linux Kernel Mailing List

Meeting Linus Torvalds at the Open Source Summit in Tokyo in June 2018.

I’ve crossed paths with Linus Torvalds at many events throughout the years, but this was the first time I actually met him and spoke with him. I waited until after his keynote and walked up to the stage, along with dozens of Japanese developers. He stayed afterwards and spoke to everyone and signed shirts and books for about a half hour. I stood off the side of the line and just took photos and listened in on the conversations. When he was finished chatting with everyone I introduced myself and we walked out into the hallway. I mentioned that I was the OpenSolaris Community Manager at Sun. He stopped, looked up, smiled, and said, “Oh, I’m sorry!” And we both laughed. I still have bittersweet feelings about Sun and OpenSolaris. It’s a shame how it all ended. I went from working on the hottest project at Sun at the time and being Sun’s #1 blogger (see: BSC front page (hits refreshed daily) to losing those platforms virtually overnight. That wrecked my career and forced me to reset yet again.

Then I told him about the time I spammed the Linux kernel mailing list with my OpenSolaris announcement back in 2005! It was an accident, of course. You see, we had been collecting emails on our website from people who wanted to be notified about the upcoming OpenSolaris announcement. We had already released the DTrace code in January 2005 but hadn’t yet opened the entire kernel. That bit was set for June and then there would be many releases after that. So, for six months about 10K people entered their email address into our web form, and obviously some special friend keyed in the Linux kernel list for kicks. Sure, we didn’t look at or clean the list for spam, but hey, we were all very busy. That OpenSolaris launch was quite a challenge.

Here is my announcement.
Here’s my apology.
Threads from the day (search for OpenSolaris)

Embarrassing. But a lesson well learned. And a good laugh years later with Linus himself. He did ask if I was treated ok by the community after the gaffe, and I said I was. All good. Anyway, we had a good conversation about Sun, Oracle, Linux, and the FOSS community. I’ll take it.

Linus Torvalds at the Open Source Summit in Tokyo in June 2018.

Message to the OpenSolaris Pilot Program

And finally, here’s the private email I sent to the OpenSolaris Pilot Program the day before I spammed the Linux community on OpenSolaris launch day. We ran a private pilot program for a year before we opened the project and those few hundred developers became the seeds of the new OpenSolaris community.

[osol-discuss] Good Luck and Thank You

Jim Grisanzio Jim.Grisanzio at Sun.COM
Mon Jun 13 17:27:01 PDT 2005


Hello, OpenSource Pilot Community.

I just wanted to chime in before the fur really flies around here:
Good Luck, and Thank You!

You all deserve Sun's thanks for your efforts and your patience this year. It should be wild day tomorrow, for sure, so light up those blogs and start talking, guys. The engineers are leading this launch tomorrow, make no mistake about it.

Oh, and if you want to bring someone into the program, you *don't* have to call me and sign another f****** NDA. Just do it. I can't tell you how happy I am to not have to dig out another NDA. Not that I could read the damn thing but whatever. It's such a cold way to start a friendly little conversation, don't you think? Also, I've tried to honor as many of your requests (and those from internal people) as possible to get people into the program. We ended up with 145, but quite frankly, dozens and dozens of developers never made it in due to lack of time or resources. We even had a dozen Chinese engineers all briefed, translated, and NDA-signed but couldn't get export control approval in time. It drove me nuts for three months. I'm more than a bit pissed about that one.

Anyway, I hope you are happy with the results of what we are all releasing. The core team here has worked almost non-stop for weeks on this to get ready for the final push. We wanted to do more, you know that, but hey, look at where we were last year and look at the potential tomorrow brings. Also, the OpenSolaris team internally really has been genuine in their intentions, I can assure you. At times we've not been as open as we could have been -- we get that -- but I hope you believe me when I say that many people on the team fought hard on your behalf all year long. Every time you told us we were full of shit on something we took it to heart and it went up line. There were a few, ah, heated,
conversations regarding some of the issues that were discussed in the pilot. We won some and we lost some, but every time we moved a little closer to our goal of openness. As you've seen, this stuff takes time. I wish we could have exposed more of that process to you. Next time it will probably be easier to do that.

As this program has grown it's garnered attention from all across Sun and from Sun's competitors and supporters. Just recently, I've heard from executives and engineers traveling to South America and to Asia, and they report that there *absolutely* is massive community interest out there. Even Wall Street has noticed. Some people are probably a bit confused since the Solaris community was supposed to be dead by now. Well, too bad. It's too late. They lost their window of opportunity to crush us. Our next step is to stay positive and to engage the interest we know is there, make it tangible, and grow this OpenSolaris community. In a very real way, you've all been part of something special here. You've helped change this company and potentially an entire market along the way. Some people may not know this quite yet, but they'll surely find out tomorrow. You are some of the most knowledgeable people in the world about Solaris, and you've help make OpenSolaris a possibility.

Congratulations and we'll see you on the other side.

Jim

Session at Open Source India

Last week I took some vacation time from work and went down to Bangalore to present a session on FOSS communities at Open Source India. It was such a wonderful experience, wow! India is electric. If you want to meet thousands of CS students and talk about Java, go to India! I have a lot of experience mixing with students over the years doing OpenSolaris projects in India, Indonesia, Singapore, Vietnam, Hong Kong, and China. I really love it. They teach me every time!

Jim Grisanzio Keynote at Open Source India in Bangalore in November 2025. Photo by Open Source India.
Jim Grisanzio Keynote at Open Source India in Bangalore in November 2025. Photo by Open Source India.
Open Source India

At Open Source India I talked about some lessons I’ve learned from building FOSS communities over the years at Sun, Oracle, and also on my own. Most of the recent content I presented came from Java, of course, since I work at Oracle on the Java Developer Relations team. But I’ve participated in many Open Source communities (Linux, OpenSolaris, MySQL, NetBeans, JXTA, BarCamp, OpenOffice, and others) over the years, so I tried to weave in many stories and experiences from those groups. I tend to focus on telling stories about developers I’ve met over the years and who I’ve photographed and interviewed. So, my presentation is unique in that it’s based on personal experience. And I talk mostly about contributing, which is the most important process that keeps Open Source communities growing and provides the most opportunities for developers. I think things went over pretty well. After I got off the stage many people came up to chat, and we just continued our conversations from earlier in the day and the previous day. That’s the “hallway” track and it’s probably the most important part of any tech conference.

The conference drew about 5K people (see official event images) with a nice mix of professional developers and computer science students. I had so many conversations with students, which was really amazing. They are so bright, eager to learn, and enthusiastic about the future. Many of them are taking Java in school now or will be soon. I tried to stress that they shouldn’t overlook Java but instead they should take as much Java as they could. Java is vastly more advanced these days, and it’s much easier to learn than it was previously. The engineering team at Oracle has taking seriously the issue of getting new and young developers coding in Java and making the onramp easier — see Java 25 here, here, here and inside.java, dev.java, and learn.java. I also told them to build their portfolio now while they are in school by contributing to Open Source projects. This way they can build a professional network early, and they’ll have concrete contributions to show future employers during interviews. Don’t wait! I told them about the conversations I’ve had with about a hundred Java developers in recent years for my podcast Duke’s Corner, which is the most valuable project I work on at Oracle.

Below are some posts on LinkedIn about Open Source India from people I met there. It’s truly touching to read such nice comments from everyone I met based on our conversations at the conference and my presentation. And some of these posts have hundreds of interactions, so that demonstrates that the developer community is thriving in India on social media. It makes sense to engage these developers when they are in school to talk about Java and the opportunities this technology offers for their future.

LinkedIn Posts

Sohail Haldar, Anish Chatterjee, Janarthanan Muthu, Sharat Chander, Solomon Mark, Jim Grisanzio, Balaji Rajendran, Nandita Mahesh, Open Source India, S Sandhya, Aishwarya Amin, Renuka Jagtap, Sanjay Jha, Sohail Haldar, Surendra Narayan, Surendra Narayan, Shan Kuriakose, Sunil Kumar, Open Source India, Jim Grisanzio, Sharat Chander, Yugesh K

JavaFest Bangalore

Also, a few days after Open Source India, the Bangalore Java User Group ran their annual conference, JavaFest, in collaboration with eight other JUGs across India. I pitched JavaFest in my session at Open Source India and I’ve been helping promote and support the event in collaboration with our Oracle engineering team in India. Hopefully some day I’ll get to speak at JavaFest as well. See two popular posts on LinkedIn from Praveen Mohan and Jayashree S Kumar from the Oracle India Developer Center in Bangalore covering JavaFest. Praveen and Jayashree work in quality engineering, and their team also contributes extensively to the Bangalore Java User Group. Also, here’s an interview I did with Praveen previously where he talks about Java quality engineering and the local community in India. It’s nice to hear that the Oracle engineering team in Bangalore values direct interactions with the community.

I didn’t bring my good camera on this trip. But I did take some selfies with my phone. See them on Flickr.

A quick note on my presentation: The pdf has about 50 source links so be sure to click on them for more.

Jim Grisanzio, Building FOSS Communities, Open Source India. Bangalore, India. 11/2025

My next trip to India will be in April 2026 for the Great International Developer Summit (GIDS). I’m really looking forward to that trip too. I bet there will be many enthusiastic CS students there as well. But whereas the Open Source India presentation was on FOSS generally, my presentation for GIDS will be exclusively on Java. Can’t wait. Cheers

Community Development is Business Development

During my time in Open Source community development, I’ve repeatedly faced the same annoying question coming from business managers: “What’s the business value of Open Source?”

Or sometimes the question goes unstated but whenever you talk about community development operations in a meeting the room goes quiet as if what you’re saying has little value. What’s funny is that this questioning of Open Source community development as a valuable discipline comes from the very people who directly engage in similar activities when they implement their own product launches; conferences; and tours to meet customers, analysts, and journalists. In community development, we do the same thing. The only difference is that we engage developers, not customers, analysts, and the press. That’s it. It’s that simple. But it gets even crazier when you realize that the developers we meet work within the customer base! And it’s well known that developers influence tech purchasing decisions.

This constant questioning of Open Source development hits community builders who work at major software vendors whether they are in engineering or marketing roles. The skepticism used to be understandable in the early days, but is it really still a mystery here in 2025? Giving away software for free seems counterintuitive to traditional business thinking, but the evidence of economic value is overwhelming. To not see this is unacceptable.

In Open Source software, a powerful economic principle has emerged over time. It’s simple. You build the Open Source development community first, and then the business opportunities follow. You have to actively work both sides of the equation, but the process isn’t difficult to understand. This isn’t speculation. So many companies have proven that this strategy generates serious revenue while also creating opportunities for millions of developers worldwide. It’s just business development. I sometimes push back on this question and point to concrete proof that community investment translates directly into business value. But most times I just ignore it and look out for people who are more knowledgable about market development.

Anyway, here are a few examples for kicks.

Linux: From Hobby Project to Massive Business Value

Take Linux. When Linus Torvalds released his Linux code in the 1990s, he invited collaboration from developers. Then thousands of kernel engineers submitted contributions. Now Linux powers most servers, supercomputers, and Android devices. IBM recognized this process early and invested aggressively in Linux development.

But many people missed this early innovation entirely. I remember I was at LinuxWorld Expo in New York City in 2001 when IBM announced its insane billion dollar investment in Linux. From the show floor I called back to colleagues on the marketing team at Sun in Silicon Valley because I viewed this move as a threat to Solaris, and I thought we’d have to respond in some way. I was literally on the call as Linus was holding court right outside the Sun booth on the show floor. He had dozens of young developers listening to his every word.

But instead of being taken seriously, I was met with laughter and mockery. “Oh, Jim, Linux is a toy,” they told me. The conversation ended quickly. That dismissive attitude was widespread throughout Sun’s technical marketing teams at the time — even among many engineers, sadly. Sun’s Solaris was a technically superior Unix at the time, so what could possibly go wrong, right? And besides, why would large enterprises ever choose a buggy free operating system cobbled together by a bunch of volunteers hacking in their basements?

That dismissal was costly. IBM’s investment paid massive returns and Linux totally undermined Solaris and Sun. I remember working on earning calls and and having to explain quarter after quarter why Linux was growing and why Solaris was declining. It was remarkable how utterly blind my colleagues in marketing and business development were at the time. It’s obvious they forgot to read “The Innovator’s Dilemma: When New Technologies Cause Great Firms to Fail.” I did suggest that they read the book, by the way, but no one took me up on the offer. I read it multiple times.

By enabling Linux for enterprise use, and contributing to the growing Linux development movement, IBM built a thriving services business that generated billions. When IBM acquired Red Hat years later for tens of billions of dollars, they purchased a company built entirely on community-developed Open Source software. Meanwhile, Sun’s proprietary Solaris became increasingly irrelevant as Linux matured and captured the enterprise Unix market. That toy operating system that Sun’s marketers laughed at literally wrecked Sun. Oracle acquired what was left of Sun a few years later as the company crashed and burned to death. But not for Solaris. The real value at Sun was in Java and Java’s growing developer community. The lesson to me was clear: dismissing a thriving global open source community is a dumb strategic mistake. Sun did finally open Solaris but by then it was too late.

Linus Torvalds at Open Source Japan in Tokyo in 2018.
Linus Torvalds at Open Source Japan in Tokyo in 2018.
Java: The Power of a Global Developer Community

Java demonstrates the pattern as well. Engineers at Sun Microsystems created Java but the community made it dominant because the technology was open from the beginning. Millions of developers learned Java. Thousands of companies adopted it. And an entire ecosystem thrived. When Oracle acquired Sun, they recognized the value of Java’s massive global community. Java Virtual Machines now run on billions of devices globally, spanning servers, embedded systems, and IoT devices. Oracle generates substantial revenue from Java-related services and support. But it was the developer community that created the global installed base that drives this revenue. Java developers earn strong salaries, representing another dimension of community-driven value. The community created sustained employment for millions of developers worldwide.

Over the years, I have interviewed about a hundred Java developers for podcasts, and their perspective is remarkably consistent. They all tell me that the open sourcing of Java made all the difference in their careers and in Java’s success. Java was open from the start, and that openness enabled them to engage with the technology in ways that proprietary languages didn’t allow. They could examine the source code to understand how features worked. They could contribute improvements. They could build tools and frameworks on top of Java without license restrictions. They credit open source and community development as the fundamental reasons for Java’s success. Without that openness, Java would have been just another proprietary language competing for attention. With it, Java became a global platform that millions of developers built their careers around. This is not speculation from business strategists. This is the direct testimony of the developers who chose Java precisely because it was open.

James Gosling keynote in Japan in 2008.
James Gosling keynote in Japan in 2008.
How FOSS Creates Business Value and Opportunity

Development communities accelerate innovation faster than any single company could achieve internally. Major container orchestration platforms, AI tools, content management systems, operating systems, languages, frameworks and databases that were open sourced have improved rapidly through community contributions. The largest cloud providers now build profitable services around these technologies. Companies that Open Source their technologies gain access to global technical expertise while building ecosystems that drive commercial adoption.

Communities also function as talent pools where companies identify skilled developers through their Open Source contributions rather than through expensive recruiters. This collaborative approach has enabled companies to reach well over a billion dollars in revenue while also creating global opportunities for developers. For example, I’ve interviewed developers who stated quite directly and passionately that Open Source and Java saved their lives. Others have said that Java enabled them to go to college and support their parents. Some have built multi-million dollar companies around Open Source frameworks. Others earn substantial income from maintaining popular packages or community sponsorships. These success stories span continents and demonstrate that Open Source creates genuine economic opportunity regardless of geography or traditional credentials.

Finally

The evidence is pretty clear, isn’t it? Community development is business development. It’s not similar. It’s not almost the same. No. It’s identical. Companies can build profitable businesses by investing in Open Source development through code contributions, foundation support, and active participation. Major enterprise software companies, database vendors, DevOps platforms, data analytics firms, and content management providers all demonstrate the model works at any scale.

Decades of history and also current trends show this clearly. You build an Open Source development community first, and then the revenue follows. You support developers, contribute to projects, start technical user groups, and host conferences. These investments generate returns as the market matures through multiple channels including sales, talent acquisition, cost reduction, and market development. Just look at Linux and Java as the two obvious examples. Open Source proves that collaboration creates more value than competition at the community level, and that sharing knowledge accelerates everyone’s success.

James Gosling and Bill Joy at the Sun Reunion in Silicon Vally in October 2019.
James Gosling and Bill Joy at the Sun Reunion in Silicon Vally in October 2019.

Read up on Sun’s Bill Joy: “No matter who you are, most of the smartest people work for someone else.”

Doc Searls on The New Vernacular

I remember in the early 2000s at Sun Microsystems we gathered hundreds of engineers in the auditorium on the Santa Clara campus for a day of sessions on Free and Open Source Software (FOSS). Back then Sun was quietly engaging FOSS community leaders at conferences and also inviting high profile developers to campus for conversations about building open communities. These meetings attempted to help teams as they grappled with opening Sun’s software projects: NetBeans, Grid Engine, Looking Glass, OpenSPARC, OpenOffice, OpenSolaris, JINI, JXTA, and Java.

There were many interesting speakers in the auditorium that day. But the Doc Searls session really resonated with me. He was a bold and dynamic personality. He explored concepts shared between software and construction, which struck me given my background in real estate development. I was new to Sun and software and had just moved to Silicon Valley from the East Coast. I was thrilled that my past experience in construction might help facilitate the radical career change I was making. I was already overwhelmed with the magnitude of change going on during that time at Sun, so it was nice to hear some solid and familiar content. I met many developers from the FOSS community in those early years at events and even at random meetings on Sun campuses. One day I walked into a meeting in Cupertino and sat down next to Richard Stallman, who then stood up and started lecturing the Java engineers for two hours about Free Software. Where am I? This is amazing, I thought to myself. Those interactions with FOSS leaders in and around Sun were extraordinary. It was an exciting time to be there.

Even though Sun had many competing factions during this time, the prevailing thought was that we didn’t want to simply open our software projects, dump the code over the firewall, and walk away. Instead, most teams aimed to update their internal development infrastructure, move source repositories across the firewall, release code under Open Source Initiative licenses, and build engineering communities by accepting contributions back. This approach, which aligned with the collaborative ethos Doc Searls expressed in his session, was an effort intended to help Sun return to its roots as a company grounded in Open Source and Open Standards. Now look, there were many internal skeptics (or antibodies, as we called them) resisting these moves, I assure you. And there were many heated battles at many levels throughout the entire company. The opening of all those projects over a period of about 6 years wasn’t easy.

Years after Doc’s talk at Sun, I stumbled across his article “The New Vernacular” and felt it nicely summarized the ideas he shared at Sun. Recently, I reread it. Here’s my reflection on his 2001 piece, looking back across twenty-four years.

The New Vernacular, Doc Searls, April 2001: A Summary

In 2001, Doc Searls argued that software was maturing into a construction industry, a vision that felt prescient then and remains relevant today for its emphasis on collaborative, community-driven development. The software industry had long borrowed the language from construction, speaking of tools, systems, architectures, builds, and frameworks. Searls suggested this wasn’t mere metaphor but pointed to a deeper shift: success would come not from dominant platform providers like Microsoft but from skilled practitioners working collaboratively in open source communities. In such a mature industry, he argued, Microsoft would hold no more importance than construction firms like Georgia Pacific or Kaufman & Broad.

The construction industry, Searls noted, had practiced what he called “open source” principles for centuries. Building materials, methods, and knowledge were openly shared and refined through peer review across generations. There was a strong history of meritocracy and mentorship, with experienced builders passing down hard-won knowledge to the next generation. This is evident in Architectural Graphic Standards, updated roughly every seven years through continuous peer review and incremental improvement. This wasn’t an abstract concept but a down-to-earth practice where the best ideas rose based on merit, not politics or corporate affiliation.

Drawing from Stewart Brand’s work in architecture and philosophy, Searls described “vernacular” construction: buildings designed not by professional architects but by builders and users who understood practical needs. This practical architecture evolved naturally, incorporating generational knowledge about maintaining and growing structures over time. These buildings stood in contrast to “magazine architecture,” which are art-focused designs that often proved impractical. Vernacular buildings embodied craft and practicality and improved as knowledge was shared and tested across projects. As Searls wrote, vernacular buildings are “everything not designed by professional architects — in other words, most of the world’s buildings.” Searls cited Richard Gabriel, a Distinguished Engineer and Chief Scientist at Sun, whose book on software patterns described building software for “habitability.” Gabriel used a New England farmhouse as his ideal, noting that “each part is well-suited to its needs, each part fits well with the others,” and inhabitants “are able to modify their environment because each part is built according to familiar patterns of design, use, and construction.”

Was Unix vernacular? In 2001, the answer was clear: absolutely. Searls cites Neal Stephenson’s observations that Unix represented a design from the hacker culture, not a company. Its command-line interface, with its consistent filesystem structure and obsessive abbreviations, reflected decades of practical, craft-driven refinement. This gave Unix a confidence and stability that commercial systems, contrived by corporate engineers, couldn’t replicate and embodied meritocratic traditions where the best solutions won through use and peer scrutiny. Searls quoted Stephenson: “UNIX, by contrast, is not so much a product as it is a painstakingly compiled oral history of the hacker subculture.”

The hacker culture and Unix’s development predated Moore’s Law and the modern software industry. MIT’s Building 20, a low-visibility, “no-style” facility, as Stewart Brand described, became legendary for enabling youthful creativity and experimentation. This “Low Road” culture mirrored vernacular construction, where function trumped aesthetics, in contrast to high-style architecture prioritizing aesthetics over utility. In places like Building 20, mentorship happened naturally, with veteran hackers guiding newcomers and sharing the community’s accumulated wisdom.

Drawing on Stewart Brand’s The Clock of the Long Now, Searls described civilization’s six layers, where slower layers like hacker culture set boundaries for faster ones like commerce. Brand noted that fast layers innovate, while slow ones stabilize. Hacker culture, rooted in nature and governance, gave software its open essence: freely shared, usable, and improvable by all. These qualities, vital to software’s foundation, aren’t commercial, as Searls emphasized: “These are values that do not—and cannot—come from business. They are not commercial values.”

The Internet embodied these vernacular principles, with almost natural qualities: nobody owns it, everybody can use it, anybody can improve it. Projects like Linux, Apache, and TCP/IP thrived because they followed this bottom-up, meritocratic model, where good code could come from anywhere and poor ideas were quickly discarded through community feedback. Corporate giants began to learn this lesson: Apple’s decision to open-source Darwin, adjusting its license after 70,000 hackers contributed, and IBM’s embrace of Linux, driven by internal engineering momentum and market changes, showed how companies could align with hacker culture’s principles, producing better results and attracting top talent.

Searls concluded that software companies faced a challenge: creating valuable infrastructure while generating shareholder returns. The answer lay in listening to engineers, who were building infrastructure organically, and recognizing what endured. Hacker culture’s deep understanding of software’s natural value—its ability to be shared, improved, and built upon—provided the foundation for software civilization. Companies aligning with these principles, rather than fighting them, would succeed.

Twenty-Four Years Later

Reading Doc Searls’ article now, in 2025, prompts reflection on how the software landscape has evolved. Searls was deeply embedded in the hacker culture of the early 2000s. But does that same culture persist today? The world has changed dramatically since then. Software ecosystems are more fragmented, with factions not always communicating. Development feels more atomized than it did two decades ago. International, domestic, and social politics now pervade many FOSS communities, unlike in 2000 when I joined Sun and such discussions were rare. Silicon Valley, once an American tech hub, is now a global economic powerhouse and has significant political influence in Washington. It’s totally different world.

I once viewed the FOSS community as roughly a single entity, but that no longer feels accurate. Perhaps I missed important distinctions back then. Today, I see diverse behaviors across FOSS communities. While FOSS is pervasive in 2025, corporate software giants are more powerful than ever and likely represent some of the most powerful institutions globally. We live in a world shaped by AI automation and algorithms, where opaque systems often replace the transparent human judgment and championed by early FOSS developers, challenging the freedoms hacker culture promoted.

So where does that leave developers today? Navigating this complex landscape requires revisiting the core principles Searls highlighted. The meritocracy and mentorship that defined hacker culture seem diluted in some FOSS communities. These principles are rarely articulated among young developers today, unlike two decades ago when they dominated every meetup. Some open source projects thrive, but they operate within intricate, disparate, and massive geopolitical systems with some stressing censorship and pervasive tracking of humans globally. This complexity is also evident in Bitcoin’s FOSS community, which navigates financial regulatory debates, unlike the technically focused, community-driven ethos of the early 2000s. Yet, I still hear Bitcoin developers articulating original FOSS principles—meritocracy, mentorship, collaboration, freedom—more strongly than some older, prominent developer communities. This highlights an opportunity to revive Searls’ vision

Searls’ argument about vernacular development, bottom-up collaboration, and the enduring value of open infrastructure remains insightful. With these concepts less frequently discussed today, they offer unique opportunities for developers to embrace foundational principles that will help build their skills, grow their networks, and improve their careers. The principles that made Unix and the Internet valuable —collaboration, openness, and practicality—endure, even as the landscape has transformed. The cycle continues. It’s time to learn again for this new age.

Andy Bechtolsheim, Vinod Khosla, Scott McNealy, Bill Joy at the Sun Reunion in Silicon Valley in October 2019.
Andy Bechtolsheim, Vinod Khosla, Scott McNealy, Bill Joy at the Sun Reunion in Silicon Valley in October 2019.

Mattias Karlsson: I think it’s Brilliant

Duke’s Corner Java Podcast: Mattias Karlsson: I think it’s Brilliant

Conversation with Mattias Karlsson, Java Champion and prominent developer in the Java community who was also honored with the Java Community Lifetime Achievement recognition at Jfokus in February 2024.

“I was shocked and honored — very humbled!” Mattias said about being recognized for his lifetime of achievements in the Java community by Sharat Chander of Oracle’s Java Developer Relations Team.

Mattias, a Stockholm-based engineer and long-time leader of the Stockholm Java User Group, shares his journey with Java, from its early days to its current role in today’s modern tech ecosystems. He also talks about the evolution of Jfokus, a leading annual Java conference he organizes, which has grown from a small Java user group into a major gathering of over 2,000 developers from diverse backgrounds around the world. Mattias highlights Java’s enduring appeal, driven by its robust JVM, backward compatibility, and vibrant community. He also reflects on the six-month release cycle, calling it “brilliant” for its balance of stability and innovation, and shares insights on mentoring young developers and using AI to stay updated. 

When talking about how students learning programming will inevitably encounter Java due to its widespread use in the industry, Mattias said, “Sooner or later they will end up with Java anyway.” 

Finally, the episode underscores the unique culture of the Java community and Jfokus as a conference for its blending of culture, professionalism, and a welcoming atmosphere.

Links: Apple | LinkedIn | Substack | WordPress | X

Here are some quotes from the conversation:

Java Community Lifetime Achievement Recognition

Surprise and Emotion of Receiving Recognition
Timestamp
: 00:01:35–00:01:45
Context: Mattias was unexpectedly honored with the Java Community Lifetime Achievement recognition at Jfokus 2024 in Stockholm, an event he organizes. The recognition came as a surprise during the opening keynote by Georges Saab and Sharat Chander. Mattias shares that the moment was deeply emotional, reflecting his long-standing contributions to the Java community, including his leadership of the Java User Group in Sweden for over 25 years. He notes the audience’s reaction and his own heartfelt response, underscoring the significance of being acknowledged by peers in a community he has dedicated much of his career to fostering.
Quote: “I didn’t know about it. I was really touched. People that were in the audience did see, you know, a little bit of tear of joy or whatever. I was really touched about it.”

Reason for Recognition
Timestamp
: 00:00:48–00:01:02
Context: When asked about the Java Community Lifetime Achievement recognition, Mattias attributes it to his extensive involvement in the Java community, particularly his leadership in running the Java User Group in Stockholm for decades. He reflects on his role in organizing community events, including Jfokus, which has become a cornerstone event for Java developers globally. His work has involved consulting, fostering collaboration, sharing knowledge, and building a vibrant community, which likely contributed to this prestigious acknowledgment. Mattias also mentions his surprise at being recognized, as he was unaware of the criteria or previous recipients, highlighting his humility and focus on community over personal accolades.
Quote: “Well, so I think it’s called Java Community Lifetime Achievements. So my guess is, and part of this is because I’ve been involved in the community for a very, very long time, running the Java User Group in Stockholm and so on.”

Feeling Honored and Humbled
Timestamp
: 00:03:23–00:03:28
Context: Mattias expresses deep humility upon receiving the Java Community Lifetime Achievement recognition, noting that he was shocked to be placed in the same category as notable figures like Bruno Souza and Venkat Subramaniam. He shares that he reached out to Sharat Chander at Oracle to understand more about the recognition, indicating his surprise and lack of prior knowledge about the honor. This moment underscores his modesty and the unexpected nature of the recognition, which he sees as a testament to his long-term dedication to the Java community through organizing events, speaking at conferences, mentoring developers, working in the field, and consulting with companies.
Quote: “So I was shocked and honored, very humbled!”

Jfokus and Community Building

Evolution of Jfokus
Timestamp
: 00:32:10–00:32:31
Context: Mattias recounts the origins of Jfokus, which began as an extension of the Java User Group in Stockholm he has led for 25 years. Initially planned as a modest one-day event in 2007 with an expected 200 attendees, Jfokus exceeded expectations when over 500 people signed up, creating logistical challenges but marking the start of its growth into a major Java conference. Now a three-day event attracting around 2,000 attendees, Jfokus has become a premier platform for Java and FOSS discussions, reflecting Mattias’s vision of scaling community engagement while maintaining a focus on cutting-edge technology and developer collaboration.
Quote: “So we were running the Java User Group and then we decided so maybe we should do a one day event and just to see how that works out and then that was back in 2007 and we were expecting 200 people and we had a venue for 200 people-ish and then suddenly we have 500 plus signed up.”

Jfokus Anniversary
Timestamp
: 00:31:25–00:31:35
Context: Mattias highlights the upcoming 20th anniversary of Jfokus, set for February 2026, as a milestone for the conference and the Java community in Stockholm. He notes that the call for speakers has just opened, signaling ongoing preparations for a significant celebration of the event’s history. This anniversary underscores Jfokus’s evolution from a small user group gathering to a globally recognized conference, reflecting Mattias’s long-term commitment to fostering a space where developers can learn, network, and share innovations in Java and related Open Source technologies. Here he ends the podcast conversation with a note on the longevity of Jfokus.
Quote: “I mean, we could mention that JFocus is having its 20th anniversary!”

Culture of Jfokus
Timestamp
: 00:36:05–00:36:29
Context: Mattias emphasizes the unique culture of Jfokus, which he intentionally designs to feel like an extension of a user group, fostering a sense of community and belonging. He aims to create an environment where attendees feel welcome and can openly engage with one another, akin to gathering in a friend’s living room. This approach stems from his experience running the Stockholm Java User Group, where community bonding was central. The feedback he cherishes most—that Jfokus feels like “coming home”—reflects his success in blending a warm, inclusive atmosphere with high-quality technical content, making it a standout event for developers worldwide.
Quote: “So the basic idea is that we look at this as an extended user group or like an extended community event. So we really try to mix the community feeling. Everybody should feel really welcome. Everybody should be open and transparent. Talk to each other. It should be a nice mingle. I mean, the best ever feedback I got at some point was like, Mattias, it feels like we’re coming home to you. We are sitting down with you in your living room, just like friends.”

Professionalism at Jfokus
Timestamp
: 00:36:31–00:36:56
Context: While prioritizing a community-driven atmosphere, Mattias also strives to ensure Jfokus operates with a high level of professionalism. He discusses the importance of making speakers and exhibitors feel supported, with seamless logistics, clear communication, and advanced presentation technology. This balance of warmth and professionalism is evident in the high-end production elements, such as quality lighting and cameras, which Jim Grisanzio notes during the podcast. Mattias’s attention to detail ensures that Jfokus delivers a polished experience, distinguishing it from purely corporate events while maintaining a community ethos.
Quote: “I want to run it like super professionally, super slick. I want all the speakers to feel that they are really welcome, get everything they need. Also with exhibiting partners, they should have a flawless session.”

Jfokus Attendee Mix
Timestamp
: 00:32:55–00:33:22
Context: Mattias describes the diverse audience at Jfokus, which includes a mix of senior and junior developers, as well as professionals from various industries such as banking, contracting, and startups. The conference attracts attendees primarily from Europe but also from places like the United States and Japan, reflecting its global appeal. This diversity underscores Jfokus’s role as a broad technology conference, not limited to a single sector, and highlights Sweden’s strong tech ecosystem, with companies like Spotify and Oracle contributing to a vibrant developer community.
Quote: “It’s very mixed. The conference is not like a company thing. It’s a technology conference. We have people coming from the banking industry, from the contractors, from all of the startups in Sweden are coming. We have senior developers, we have juniors, and we have people from all over the world.”

Java Technology and Its Appeal

Java’s Ubiquity
Timestamp
: 00:24:49–00:24:54
Context: Mattias shares his perspective on why Java is a natural destination for developers, given its widespread adoption across industries. He argues that regardless of where programmers start, the prevalence of Java in major corporations ensures they will absolutely encounter it eventually. This view is rooted in his experience working with companies in Sweden and reflects his belief in Java’s enduring relevance in the tech world.
Quote: “As long as people start doing programming, sooner or later they will end up with Java anyway.”

Java’s Stability and Performance
Timestamp
: 00:10:46–00:11:02
Context: Mattias praises Java’s unique ability to maintain both backward and forward compatibility, allowing code written a decade ago to run efficiently on modern JVMs. He highlights how advancements like virtual threads have improved performance without requiring developers to modify their code, demonstrating Java’s ability to evolve while preserving stability. This characteristic, he notes, sets Java apart and empowers developers to focus on innovation rather than maintenance.
Quote: “It’s both backward and forward compatible in the sense that, I mean, if I did write a Java program 10 years ago, I can just fire it up on the latest version of the JVM, best case and it will probably work fine and on top of that it will be faster and more performant than it was 10 years ago.”

Six-Month Release Cycle
Timestamp
: 00:16:38–00:16:41
Context: Mattias strongly supports Java’s six-month release cycle, which he calls “brilliant” for balancing innovation with stability. He recalls debates within the community about adopting this faster cadence, noting his advocacy for the change due to his experience with agile development. The regular releases provide stable updates, experimental features, and a clear roadmap, which he believes benefits developers by keeping Java fresh and predictable without breaking existing systems.
Quote: “So, I think it’s brilliant!”

JVM’s Technical Strength
Timestamp
: 00:09:07–00:09:14
Context: Mattias underscores the advanced technical ability of the Java Virtual Machine (JVM), particularly its garbage collection, which was a significant advantage in Java’s early days. He explains that the JVM’s sophisticated capabilities, often described as “magic tricks,” have been a cornerstone of Java’s success and enables robust performance and scalability that attract large corporations to the platform.
Quote: “I love the language, but also the platform, the JVM. So, the JVM does quite a lot of magic tricks that is technically really hard to understand how it works. If you go way back, just the fact that we had a proper garbage collection was, you know, a big thing.”

Java’s Scalability
Timestamp
: 00:11:51–00:12:07
Context: Reflecting on his time at King, the company behind Candy Crush in Stockholm, Mattias highlights how Java and the JVM enabled the backend systems to scale effectively during the game’s massive success. This experience reinforces his view of Java’s reliability and scalability, which are critical for handling the demands of high-traffic applications in major companies.
Quote: “So I used to work for a company called King, which that makes a very famous game called Candy Crush. And I mean, we were running the backend servers there on the JVM and Java, and that helped us scale up when that game became successful.”

Developer Experience and Learning

Advice for Young Developers
Timestamp
: 00:27:06–00:27:23
Context: Mattias advises young developers to focus on learning programming fundamentals, as Java’s widespread use ensures they will encounter it naturally and everntually. He emphasizes that mastering problem-solving and engineering principles is key, as Java’s prominence in industry—evident in companies like Spotify—makes it a likely tool for their careers. This advice aligns with his belief that Java’s ecosystem supports developers in building robust, scalable solutions.
Quote: “Every company is using Java, or most companies are. And if they don’t, they will be in the future. And I think that is a really interesting comment because it speaks to the fact that it might not matter to a student where you start as long as you learn the fundamental processes of solving problems with code and becoming an engineer, a software engineer, you’re going to have to learn multiple technologies. And once you discover Java, which you certainly will, then Java speaks for itself.”

Using AI for Learning
Timestamp
: 00:26:26–00:26:51
Context: Mattias shares how he uses AI tools, such as those integrated into IDEs like Cursor, to stay updated with modern Java features, particularly functional programming techniques. He notes that AI helps him bridge the gap between his older coding style and newer Java advancements, suggesting that students and developers can leverage AI for learning new frameworks and languages efficiently. This approach reflects his adaptability and openness to evolving technologies.
Quote: “So I’m using AI as a learning tool now. It helped me write code, but it also helped me to learn functional ways of doing stuff that I have not been so good at before. I mean, even if student is not doing that, I think that you can have AI supported learning for new frameworks, new languages, newer versions of Java or any other framework or tools.”

Early Java Experience
Timestamp
: 00:21:28–00:21:33
Context: Mattias recalls his early experiences with Java around 1998–1999, noting its stability as a standout feature despite initial drawbacks like slow startup times. He contrasts Java with other languages he used, such as C++ and Visual Basic, and highlights how Java’s reliability made it a compelling choice for web development and enterprise systems at the time.
Quote: “So one is that it worked. It was stable and continued to work.”

Transition to Java
Timestamp
: 00:19:53–00:20:00
Context: Mattias describes his transition to Java in the late 1990s while working at Ericsson, where he began using Java Server Pages for web interfaces to legacy systems. This marked his shift from languages like C++ and Visual Basic to Java, which he adopted for its growing relevance in web development. His early work with Java’s pre-1.0 versions laid the foundation for his long-term commitment to the platform.
Quote: “But then I think around 98, 99, I was moving into Java, and I was, like many, started with the web.”

Bruno Souza: My Greatest Pride is the Community

Duke’s Corner Java Podcast: Bruno Souza: My Greatest Pride is the Community

Jim Grisanzio from Java Developer Relations talks with Bruno Souza, who is a Java Champion, leader of the SouJava User Group in Brazil, and a member of the JCP Executive Committee. Bruno received the first Java Community Lifetime Achievement recognition in October 2022 at JavaOne in Las Vegas. “I was totally surprised! I was jumping up and down! I was so honored! It’s an honor to be a member of that group.” he said.

Bruno Souza is known as the “JavaMan” from Brazil and that nickname started back at Sun when Java was announced and Bruno started evangelizing the technology. Bruno’s message to the community was “Open Standards and Open Source” as he began his community building efforts around Java. He continually brought to Brazil FOSS and Standards experts for community discussions, and he advocated for a standards-based Open Source implementation of Java that would pass the TCK.

“Maybe my greatest pride, I think, is the idea of the Java User Groups community,” Bruno says. “We have OpenJDK for development and the JCP for standards, but for me the real Java community is the Java User Groups! These are all volunteers who meet and help others participate and learn.”

Bruno in recent years has been talking a lot about building reputation and career by embracing the open-source lifestyle — writing code in Java, contributing to Open Source, and helping build the community itself. Since our work lives in public mailing lists and open-source code repositories, we earn credibility by being visible, contributing, engaging the community, and helping others get involve as well, Bruno says. 

Bruno advises that career is a long-term project: “The more you work on it, the more you grow, the more results you have. So, the sooner you start the better. This is not a sprint! This takes time.”

Getting back to Java itself, Bruno, like most Java developers, prefers the 6-month release cadence over the older system of multi-year development and release cycles. There is a constant flow of technology now which allows for more interactions between the Oracle engineers and engineers in the community.

“Everything you see today in Java is possible because of the 6-month release process. I just loved it when the guys did that! I think it’s amazing! The fact that we now have two releases per year changed Java. I think we’re positioning Java to be even stronger in the years to come. I’m very excited about the whole thing,” Bruno says.

Throughout this conversation Bruno provides a wonderful history of Java since he’s been involved from the very beginning! “People don’t remember that Java was a community from the very beginning!” Bruno says. “We were able to look at the source code from the very beginning and that allowed us to build the community from the very beginning with lots of other companies joining.” And then the JCP was created to allow Sun and the community to discuss the standardization of Java. And then OpenJDK was a huge step because now Java would be everywhere with Oracle leading and building the community. “Java is more participative today under Oracle than during the Sun times.”

“Java + Open Source + Community: That’s what grows our career. That’s what grows Java too!”

Here are some links where the Bruno interview can be found in full or in clips: Apple | Flickr | LinkedIn | LinkedIn | Substack | WordPress | WordPress | X | X | YouTube. Here are all the interviews on Duke’s Corner. Here is Bruno’s full interview transcript. Below see more quotes from the interview:

Surprise and Honor of the Lifetime Achievement Award
Quote: “I was totally surprised! And it was very cool because, you know, you’ve been to keynotes on big events, and lots of things are scripted, lots of things are rehearsed. And I think with that one, the way they did it, allowed it to be real.”
Timestamp: 00:04:16–00:04:34
Context: Bruno describes his genuine surprise and excitement upon receiving the first Java Community Lifetime Achievement honors at JavaOne 2022 in Las Vegas, highlighting the authenticity of the moment.

Advocating for Open Source and Standards
Quote: “Open Source plus Open Standards. That’s what we need, right? You know, we can’t really just do free software, right? It’s not only open source. This whole idea of having open source software that is not standard basis, then you only have one implementation.”
Timestamp: 00:08:01–00:08:13
Context: Bruno discusses his early efforts in Brazil to combine open source with open standards, emphasizing the need for a standards-based, open-source implementation of Java to ensure broader applicability and community involvement.

Java User Groups as the Real Community
Quote: “But for me, the real Java community is the Java user groups! Because those are all volunteer-based leaders helping people to meet each other, to actually participate and discuss, and learn.”
Timestamp: 00:12:47–00:12:55
Context: Bruno underscores the significance of Java User Groups (JUGs) as the heart of the Java community, highlighting their role in fostering volunteer-driven collaboration, learning, and networking among developers locally and around the world.

Reputation as a Career Cornerstone
Quote: “Reputation is more important than your salary, is more important than your job, is more important than your house, right? Because reputation is going to give you all of that!”
Timestamp: 00:15:11–00:15:19
Context: In his career session, Bruno emphasizes the critical role of reputation in professional growth, explaining that reputation underpins long-term success and opportunities more than immediate material gains. Remember, reputation is actually a dependency for success.

The Power of Java, Open Source, and Community
Quote: “This merger of those three things — Java, Open Source, and Community — I think that’s what grows our career. That’s what grows Java too!”
Timestamp: 00:36:51–00:36:57
Context: Bruno summarizes his philosophy that combining expertise in technology like Java, contributions to open source, and active community participation drives both individual career growth and the advancement of Java as a platform.

Career as a Marathon
Quote: “Career is this long term thing that, the more you do it, the more you grow, the more results you have.”
Timestamp: 00:22:10–00:22:18
Context: Bruno advises developers to view their careers as a long-term endeavor, not a short term sprint, stressing the importance of consistent effort in building reputation and skills over time, rather than seeking quick wins. Also, he stresses that if you find yourself unemployed, that’s not the time to start networking. You have to always be networking and always be building your career.

The Impact of Java’s Six-Month Release Cadence
Quote: “Everything you have seen on Java today is possible because of the release cadence. I just love it when the guys did that.”
Timestamp: 00:28:31–00:28:40
Context: Bruno praises Java’s shift to a six-month release cycle, crediting it for enabling rapid innovation and fostering greater interaction between Oracle engineers and the broader Java development community.

Java’s Community Roots
Quote: “People don’t remember that it was a community from the beginning. You know, the fact that it was not Open Source, it was not Free Software, it had very complex license, but it allowed us to build that community in the very, very beginning.”
Timestamp: 00:30:29–00:30:46
Context: Bruno reflects on Java’s early days, noting that despite its initial complex licensing, and not having a standard FOSS approved license of the time, the ability to access source code from the start under the Sun license fostered a strong community foundation that contributed to Java’s success today. Over time, however, Sun released OpenJDK under the GNU General Public License (GPL) in 2006.

Oracle’s Role in Java’s Evolution
Quote: “Oracle released more coding to OpenJDK, they built a community, they maintained the whole idea, they maintained Java, they maintained the specifications. Oracle did the best it could have done. I think that Java today is more participative in OpenJDK than it was during Sun’s time.”
Timestamp: 00:33:51–00:33:57
Context: Bruno discusses Oracle’s stewardship of Java after the acquisition, suggesting that Oracle’s less protective approach compared to Sun allowed for greater community participation, enhancing Java’s development through OpenJDK.

Encouraging Broader Participation
Quote: “If you are the only person that does something and you want more people to come and help you in your user group, in your volunteer work, whatever it is that you’re doing, if you’re the only person that does everything and you want other people to participate, there’s just one way. You have to stop doing something!”
Timestamp: 00:34:23–00:34:38
Context: Bruno shares a philosophy on community leadership, explaining that stepping back from some responsibilities is essential to encourage others to contribute, thereby strengthening the community. Watch for this in communities. Leaders know how to do this to encourage more participation.

JavaOne’s Vibrant Return
Quote: “JavaOne was awesome! I really enjoyed the talks. I really enjoyed the people that were there and had great conversations. There’s people that came to JavaOne for the first time and they’re like, oh man, it’s such an amazing event. So I’m glad we’re back!”
Timestamp: 00:00:31–00:00:43
Context: Bruno expresses his enthusiasm for the return of JavaOne 2025, highlighting the event’s energy, the quality of technical talks, and the community engagement. It was a significant moment for Java developers new to the community and also established developers.

A Gift for Career Growth
Quote: “I wrote 15 emails, one for each chapter of the book that gives you one main idea from each chapter. So if you download the book, I’m going to send you all of those 15 emails.”
Timestamp: 00:38:36–00:38:47
Context: Bruno offers a practical resource for developers, sharing that he and Heather Van Cura wrote a book on career growth, and he provides free access to the first chapter and a series of emails summarizing key ideas to help developers apply these principles. The book is called “Developer Career Masterplan: Build your path to senior level and beyond with practical insights from industry experts.”

Honoring Java Community Pioneers

Since 2022, Oracle’s Java Developer Relations team has been celebrating the contributions of Java community members through a special Java Community Lifetime Achievement Recognition. These prestigious honors recognize individuals whose lifelong dedication to Java has advanced the technology and strengthened the community globally.

Java Community Lifetime Achievement Recognition


This unique program is led by Sharat Chander, Senior Director, Java Product Management & Community Engagement. As part of the program, I’ve been interviewing the community recipients on the Duke’s Corner Podcast to share their inspiring stories, technical insights, advice to new developers, and passion for all things Java. Their work embodies the spirit of Open Source innovation, driving progress through collaboration, contribution, education, advocacy, and community building.

This year represents Java’s 30th anniversary, and Oracle has been leading Java since acquiring Sun Microsystems in 2010. The ecosystem is now thriving around the world. And the Java Developer Relations team is committed to recognizing those who have shaped that ecosystem by empowering developers, solving complex problems, and sharing knowledge. From authoring influential books and highly technical newsletters to organizing transformative conferences and contributing code, these recipients have left a significant impression on Java’s evolution. Their efforts highlight the power of open, community-driven development, where individuals collaborate to extend the technology, innovate solutions, and mentor the next generation of developers.

The podcast interviews that follow reveal a shared ethos among the recipients — a commitment to continuous learning, problem-solving, and fostering human connections across vast networks of developers. Discussions also cover Java 25’s latest innovations with specific JEPs, the platform’s evolution from decades ago, and the recent six-month release cycle that enables iterative improvements.

The recipients also share personal insights about contributing to Java — from submitting code to OpenJDK to creating and running Java User Groups — emphasizing the importance of earning credibility by collaborating with other developers to integrate code and build the community. Their advice to students and new developers centers on learning how to learn, solving real-world problems, leveraging community resources, and building portfolios of work hosted in public repositories such as GitHub. These pioneers continue to inspire, which helps ensure the platform’s continued growth in a rapidly evolving tech market saturated with AI. The recognitions not only celebrate past achievements but also pave the way for future contributions, reinforcing Java’s role as a leader in modern Open Source software development.

And finally, during the interviews all of the recipients speak fondly of Sharat Chander who leads the program at Oracle. Shar has been the Java community’s ever present leader for the Java’s entire lifetime, starting back at Sun and now at Oracle. And it surely shows! Every recipient enthusiastically appreciates Shar’s tireless efforts to engage developers wherever they are and help grow the community.

Below are the audio podcast profiles of the six recipients honored so far, with summaries of their podcast discussions, the full transcripts of the conversations, blogs with quotes and context from the interviews, and links where the interviews appear in full or via clips on various platforms. This post will be updated as more individuals are recognized, celebrating the ongoing legacy of Java’s community pioneers.

Java Community Lifetime Achievement Recipients


Mattias Karlsson: I think it’s Brilliant
September 15, 2025 | Transcript: 77-Mattias-Karlsson.txt | Blog & Quotes
Links: Apple | LinkedIn | Substack | WordPress | WordPress | X

Podcast Summary: Mattias Karlsson is a Java Champion who was also honored with the Java Community Lifetime Achievement recognition at Jfokus in February 2024. “I was shocked and honored, very humbled,” Mattias said about being recognized for his lifetime of achievements in the Java community by Sharat Chander of Oracle’s Java Developer Relations Team. Mattias, a Stockholm-based engineer and long-time leader of the Stockholm Java User Group, shares his journey with Java, from its early days to its current role in today’s modern tech ecosystems. He also talks about the evolution of Jfokus, a leading annual Java conference he organizes, which has grown from a small JUG into a major gathering of over 2,000 developers from diverse backgrounds. Mattias highlights Java’s enduring appeal, driven by its robust JVM, backward compatibility, and vibrant community. He also reflects on the six-month release cycle, calling it “brilliant” for its balance of stability and innovation, and shares insights on mentoring developers and using AI. When discussing how students learning programming will inevitably encounter Java due to its widespread use, Mattias said, “Sooner or later they will end up with Java anyway.”  Finally, the episode underscores the unique culture of the Java community and Jfokus as a conference for its blending of culture, professionalism, and a welcoming atmosphere.


Venkat Subramaniam: I Teach Because I Learn
September 4, 2025 | Transcript: 76-Venkat Subramaniam.txt | Blog & Quotes
Links: Apple | LinkedIn | Substack | WordPress | WordPress

Podcast Summary: Venkat Subramaniam was recognized with the Java Community Lifetime Achievement honors by Oracle’s Sharat Chander at Devoxx UK in May 2024. Venkat is a Java Champion, founder of Agile Developer, and teacher at the University of Houston. In this conversation Venkat expresses humility about his accomplishments and credits industry giants and his passion for learning and sharing. He reflects on his decision years ago to focus on teaching and technology, writing books, and speaking at conferences and Java User Groups. In fact, Venkat praises Java User Group leaders as “unsung heroes” for their organizational efforts to build the Java community locally and globally. Venkat highlights Java 25’s evolving features like structured concurrency, scoped values, pattern matching, and the instance main method, which helps simplify the learning process for new developers. He also cites Java’s agile six-month release cycle, which helps improve the smooth evolution of Java, increases developer engagement, and makes Java more suitable for today’s rapidly expanding technology markets. Emphasizing teaching as reciprocal learning, Venkat advises students to engage mentors and senior developers to collaborate with juniors and welcome them into the community. He stresses that knowledge grows when shared. His mantra? Teaching fuels learning and he lives that ethic every day as he interacts with thousands of developers around the world.


Bruno Souza: My Greatest Pride is the Community
Recognized: October 2022 at JavaOne in Las Vegas, Nevada, USA
August 31, 2025 | Transcript: 75-Bruno-Souza.txt | Blog & Quotes
Links: Apple | Flickr | LinkedIn | LinkedIn | Substack | WordPress | WordPress | X | X | YouTube

Podcast Summary: Bruno Souza, a Java Champion and SouJava leader, reflects on his decades-long impact in the Java community, from early evangelism in Brazil to making the Java Community Process more open and fostering global open source growth. He credits Java User Groups as the “real Java community” for connecting and empowering developers worldwide. Bruno emphasizes: “Java + Open Source + Community — that’s what grows our career. That’s what grows Java too.” On career development, he calls reputation “more important than your salary, job, or house,” and urges developers to see professional growth as “a marathon, not a sprint.” Discussing Java’s evolution, Bruno highlights the shift to a six-month release cycle, saying, “Everything you see today in Java is possible because of the six-month release process.” He notes that this regular cadence has driven both innovation and stronger connections among Oracle engineers and the global developer community, encouraging continuous learning, open collaboration, and lasting opportunities for developers in the Java ecosystem.


Trisha Gee: It’s all about Relationships and People
Recognized: February 2025 at Jfokus in Stockholm, Sweden
August 18, 2025 | Transcript: 73-Trisha-Gee.txt | Blog & Quotes
Links: Apple | Flickr | Substack | LinkedIn | LinkedIn | WordPress | WordPress | X | X | YouTube

Podcast Summary: Trisha Gee, head of developer advocacy at Gradle, shares her 25-year Java journey, starting as a university student in 1997. Honored at Jfokus, she emphasizes Java’s community-driven ecosystem and the JVM’s performance as key to solving real-world problems. Trisha discusses AI’s role, noting that developers excel in problem-solving beyond just code generation. She advocates for continuous learning, sharing knowledge, and building relationships to empower developers. Her work at Gradle bridges technical and business needs, ensuring that the voice of the developer resonates. Trisha encourages new developers to engage with the community and embrace discomfort as a path to growth. On Java 25, she praises the six-month release cycle for enabling incremental improvements like pattern matching, which simplifies adoption. She advises students to use modern IDEs and resources like Head First Java to ease learning and to contribute by sharing knowledge at conferences.


Cay Horstmann: Java Still Vibrant After 30 Years
Recognized: April 2025 at JCON in Cologne, Germany
August 8, 2025 | Transcript: 72-Cay-Horstmann.txt | Blog & Quotes
Links: Apple | Substack | LinkedIn | LinkedIn | LinkedIn | LinkedIn | Flickr | Flickr | Flickr | WordPress | X | X | X | X | YouTube | YouTube | YouTube

Podcast Summary: Cay Horstmann, a celebrated author and educator, was surprised by his JCON recognition. Known for Core Java and decades of blogging, he discusses Java’s evolution, particularly Java 25’s recently implemented beginner-friendly features like simplified main methods. Cay highlights task-driven learning and unconferences like JCrete for sparking innovation. He advises students to focus on learning how to learn, a critical skill for navigating rapid technological change. His teaching philosophy emphasizes practical engagement over rote memorization, which helps prepare developers for lifelong growth in a dynamic field. Cay’s contributions continue to shape Java education and community engagement. He appreciates Java 25’s JEP 512 for compact source files, making learning easier, and values the six-month release cycle for steady improvements. Cay encourages students to tackle small projects and contribute to Java by exploring open-source opportunities.


Heinz Kabutz: Really Life Changing!
Recognized: May 2025 at Devoxx UK in London, England
July 31, 2025 | Transcript: 71-Heinz-Kabutz.txt | Blog & Quotes
Links: Apple | Substack | LinkedIn | LinkedIn | LinkedIn | LinkedIn | LinkedIn | WordPress | X | X | X | X | X | YouTube | YouTube | YouTube | YouTube | YouTube

Podcast Summary: Heinz Kabutz, creator of The Java Specialists’ Newsletter and JCrete unconference, was honored at Devoxx UK. His newsletter, launched in 2000, reaches developers in more than 150 countries and offers technical insights and building a global community. Heinz discusses JCrete’s interactive format, which fosters life-changing connections and innovation. He highlights Java 25’s features like flexible constructor bodies and simplified main methods, which helps ease the on ramp for new developers. Heinz advises new developers to solve real-world problems, build GitHub portfolios, and engage with JUGs to expand career opportunities. He also emphasizes the Java community’s generosity and collaborative spirit. He praises Java 25’s JEP 513 for flexible constructor bodies and the six-month release cycle for iterative enhancements. Heinz encourages students to solve math problems on Project Euler and contribute to OpenJDK by submitting verified bug fixes.


Stay tuned for more updates to this post as we continue celebrating the developers shaping the Java community via the Java Community Lifetime Achievement recognition! I’ll keep this post pinned to the top of this blog.