Duke's Corner

Jim Grisanzio

Duke's Corner is a forum for conversations with Java developers. Tune in to connect with the community and learn how developers are innovating with Java around the world. Host: Jim Grisanzio, Oracle Java Developer Relations @jimgris

  1. Paul Bakker: Go Build a Lot of Stuff!

    5D AGO

    Paul Bakker: Go Build a Lot of Stuff!

    This is the third 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. Register. Sessions. In this conversation, Jim Grisanzio from Java Developer Relations talks with Paul Bakker, an engineer and Java architect in California. Paul is a staff software engineer in the Java Platform team at Netflix. He works on improving the Java stack and tooling used by all Netflix microservices and was one of the original authors of the DGS (GraphQL) Framework. He is also a Java Champion, he's published two books about Java modularity, and he's a speaker at conferences and Java User Groups. Java Is Everywhere at Netflix Paul will present "How Netflix Uses Java: 2026 Edition" at JavaOne in March. The session updates previous year's talk because Java keeps evolving at Netflix. "Netflix is really staying on the latest and greatest with a lot of things," Paul says. "We're trying new things. And that means there's always new stuff to learn every year." Java powers both Netflix streaming and enterprise applications used internally and supporting studio teams. "Java is everywhere at Netflix," Paul says. "All the backends, they are all Java powered." Why Java? It comes down to history and practicality. The original team members were Java experts, but more importantly, "Java is also just the best choice for us," he says. The language balances developer productivity and runtime performance. At Netflix's scale with thousands of AWS instances running production services, runtime performance is critical. Netflix engineers stay closely connected with development at OpenJDK. They test new features early and work with preview releases or builds before official releases. When virtual threads appeared, Netflix engineers tested immediately to measure performance gains. Paul says they give feedback on what works, what doesn't work, and what they would like to see different. This just demonstrates the value of being involved with OpenJDK, and Paul says they have a really nice back and forward with the Oracle engineering teams. The microservices architecture Netflix adopted years ago enabled the company to scale. This approach has become common now, but Netflix pioneered talking about it publicly. Breaking functionality into smaller pieces lets teams scale and develop services independently. Most workloads are stateless, which enables horizontal scaling. Production services for streaming often run several thousand AWS instances at a time. Early on with Java Applets Paul's coding journey started at 15 when he got his first computer and wanted to learn everything about it. Working at a computer shop repairing machines, the owner asked if he knew how to build websites. Paul said no but wanted to learn. He was curious about everything that involved computes. Java applets were hot back then. With nothing online available, he bought a book and started hacking away. "It was so much fun that I also decided right at that point basically like, oh, I'm going to be an engineer for the rest of my life," he says. That's clarity for a 15-year-old. And it's remarkable. But Paul says it felt natural. He just started doing it, had such a good time, and knew that was what he wanted to do. When he started university around 2000, right during the dot-com bubble and crash, professors warned students not to expect to make money in engineering because the bubble had burst. Paul still remembers how funny that seems now. You can never predict the future. Initially, he learned Java and PHP simultaneously. Java powered client-side applications through applets while PHP ran server-side code. The roles have completely reversed now. Engaging the Community Paul attended his first JavaOne in 2006. "Those were really good times," he says about the early conferences when everything felt big and JavaOne was the only place to learn about Java. Back then, around 20,000 people would travel to San Francisco every year. It was the one and only place to learn what was new in Java. All the major news would be released at JavaOne each year. The world has changed. Now information spreads instantly and continually online, but Paul misses something about those early days. The more recent JavaOne conferences offer something different but equally valuable. Paul points to last year's event in Redwood City as a great example. While the conference is still big, it's small enough that attendees can actually talk with the Oracle JDK engineers and have deeper conversations. The folks who work on the JDK and the Java language are all there giving presentations, but they're also totally accessible for hallway chats. "That makes it really interesting," Paul says. This direct access to the people building the platform distinguishes JavaOne from other conferences. Java User Groups also played an important role in Paul's development. He lived in the Netherlands before moving to the Bay Area nine years ago. In the Netherlands, the NLJUG (Dutch Java User Group) organized two conferences a year, J-Spring and J-Fall. Paul would go to both every year. That was his place to learn in Europe. He has been continuing that pattern right up until now, which is why he is speaking at JavaOne again. Open Source software has also been another major aspect of community for Paul. He has always been active in Open Source because he says it's a fun place to work with people from all over the world solving interesting problems. Besides being a critical part of his professional career, it was also his hobby. Paul says the Open Source aspect with the community behind it is maybe his biggest thing that he really enjoyed over the years. AI Throughout Development AI now occupies much of Paul's professional focus. At Netflix, engineers use AI tools throughout the development lifecycle. Paul uses Claude Code daily, though other developers prefer Cursor, especially for Python and Node work. Most Java developers at Netflix work with Claude Code. The tools integrate with GitHub for pull request reviews, help find bugs, and assist with analyzing production problems by examining log files. Paul describes using AI as having a thinking partner to t all to and code with. Sometimes he needs to bounce ideas around, and the AI gives insights he might have missed or suggests additional issues to consider. For repetitive tasks like copying fields between objects, AI handles the grunt work efficiently. "That's the nice thing about an AI," Paul says. "While a person would probably get really annoyed with all this feedback all the time and like having to repeat the work over and over again, but an AI is like, fine, I'll do it again." Go Build a Lot of Stuff! When asked about advice for students, Paul's answer comes quickly and has not changed much over the years. "I think what I really recommend is just go and build a lot of stuff," he says. "The way to get to become a better developer is by doing a whole lot of development." That's timeless advice students can easily adopt no matter how the modern tools for learning have changed. Paul had to go to a bookstore and buy a book to learn programming. Students today have AI tools to help them and advanced IDEs. But the fundamental principle remains the same, which is to build interesting applications. Paul recommends that students come up with a fun problem and just build it. You learn by making mistakes. You build a system, reach the end, and realize the new codebase already struggles with maintainability. Then you ask what you could have done differently. Those real-life coding experiences teach you how to design code, architect code, and write better code. Paul also suggests that students use AI tools but not blindly. Do not just accept whatever an AI generates. Instead, try to understand what came out, how it could have been done differently, and experiment with different approaches. Use the tools available but really understand what is going on and what options you have. Some students and even practicing developers worry that advanced tools might eliminate their future role as developers. Paul says that nobody knows exactly how things will look in the future because tools get better almost every day now. But AI tools are just tools. Someone needs to drive them and come up with the ideas they should build. Plus, the tools at present are far from a state where you can hand them a task, never look at it again, and have everything work perfectly. Substantial hand-holding is involved. "Is our daily work going to change? Very likely," Paul says. "That's already happening." But he tries to see this change as a positive thing. "It's a new tool that we can use. It makes certain parts of our job more fun, more interesting. You can get more things done in some ways and be open to it." Why Java Works At the end of the conversation, Paul answered a simple question — Why Java? What makes it great? — with a simple and direct answer: "Java is the perfect balance of developer productivity and runtime performance." That balance matters where Paul works at Netflix. But it also matters for students learning their first language, for teams building enterprise applications, and for developers choosing tools that will sustain long careers. Paul's career started with Java applets 20 years ago when he bought a book and started hacking away. The language and platform has evolved dramatically since then, moving from client-side applets to powering massive backend services that stream entertainment to millions globally via Netflix. Through all that change, the core appeal remains — you can build things efficiently for many platforms and those things run fast. Paul Bakker: X, LinkedIn Duke's Corner Java Podcast: Libsyn Jim Grisanzio: X, LinkedIn, Website

    26 min
  2. Marit van Dijk and Anton Arhipov: 25 Years of IntelliJ IDEA

    JAN 29

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

    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: Libsyn Oracle Java Developer Relations: Inside.java, Dev.Java, Learn.java Specific Topics Discussed: IntelliJ IDEA 25th Birthday, The Java Dukes, What's new in IntelliJ IDEA 2025.3, Spring Debugger, Command Completion

    31 min
  3. Jeanne Boyarsky: Get Ready for Java 25 Certification

    JAN 21

    Jeanne Boyarsky: Get Ready for Java 25 Certification

    This is the first 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 $50 discount by using this code at checkout: J12026DCP. Register. Sessions. In this conversation, Jim Grisanzio from Java Developer Relations talks with Jeanne Boyarsky, a Java developer, an author, and a Java Champion based in New York City. Jeanne previews her JavaOne session, which will be a Hands on Lab for Java 25 certification. Previously, Jeanne was a guest on Duke's Corner in January 2024: Jeanne Boyarsky on Java, Learning, and Contributing. Preparing for Java 25 Certification Jeanne will be running a hands-on lab about Java 25 and getting ready for the certification: Becoming One of the First Java 25 Certified Developers in the World (or Learning New Features). The session will cover features added to the language from Java 17 to Java 25. Although the certification has not been announced yet, Jeanne is already preparing for it. "You can be one of the first people in the world to be certified if you come to my talk and learn about it and are ready when the test comes out," she says. The lab will walk through tricky questions and edge cases featuring new functionality, with coding practice to explore the features directly. Even if you are not planning to take the certification test, the lab provides a good way to learn about the new features. The session is designed for beginners with one to three years of experience. Top Features in Java 25 Several features particularly excite Jeanne. She highlights scoped values, which she describes as "a good jump from thread local in order to be able to share code in a nice, safe, contained way." She also appreciates unnamed variables and unnamed patterns because developers no longer need to use annotations to suppress warnings for unused variables. "You can just use an underscore," she says. Jeanne is particularly interested in stream gatherers because streams are one of her favorite features in Java overall. She was excited when stream gatherers were in preview, and now that they are officially released, she can use them in her job. "Nice that the excitement hasn't worn off, right?" Among the new features, Jeanne is especially interested in the new main method, as described in JEP 495: Simple Source Files and Instance Main Methods. "I'm super, super, super excited about the new main methods where you don't need a class and you don't need the whole static void mess," she says. This change makes writing code more succinct. Making Java Accessible to Students This change in how Java handles the main method enables new developers to learn Java faster. Jeanne volunteers at a high school teaching kids how to code in Java. In the past, teachers had to tell students: "Alright, public class foo, public static void. Don't worry about what any of that means. We'll tell you later." But Jeanne says that curious kids would ask what it meant, and teachers could only say that comes later. Now, students start with void main, braces, and IO print line. "It's obvious what everything does," Jeanne says. Void means it does not return anything, which makes sense to students. They can even use the Java Playground and start with just IO print line. When they move to the command line or an IDE, they only need the void main part without discussing the word class until they are ready to learn about classes and objects. "It makes their first impression of the language so much better, and it makes it so much faster and easier for them to get started," Jeanne says. She particularly appreciates the Java Playground because students do not need anything installed on their computers to start. They can write print lines, loops, and control structures, and by the time teachers ask them to install something, they are already invested in programming. "It's fun." Jeanne calls the Java Playground "awesome" and says it's a "really nice utility" even for experienced developers. She uses it herself for quick tests when she does not want to open an IDE. JavaOne on Oracle's Campus When asked about JavaOne, Jeanne describes the conference as moving to California last year, just outside San Francisco on Oracle's campus. "The weather was great, which is awesome because I live in New York City. There's snow outside right now," she laughs. The venue particularly impressed her. "It was nice because it was on Oracle's campus. You got a feel for it. It was pretty. There was a lake. There was a lot of areas to connect with people inside and outside." The conference was held largely in one building, with lunch in another building nearby, which made it easy to engage people repeatedly. "Even if you don't know people, the fact that they're at JavaOne means they're interested in Java. So, you can go over to anyone and introduce yourself." One of Jeanne's favorite memories from a previous JavaOne was meeting Duke and seeing her book in the Java bookstore. Advice for Students When asked for advice for students learning computer science, Jeanne recommends learning the fundamentals while using AI to help. "Rather than using AI to write the code, have it give you practice questions or do code review or ideas of projects," she suggests. Students also often ask what professional developers do daily. Her answer provides a realistic picture of professional software development. "Every day is a little bit different, but most days include a mix of meetings, working with my coworkers, code reviews, writing code, now with AI," she says. Problem solving takes many forms, from performance questions like "Why is this slow?" to security concerns about making systems more secure. A significant part of her role involves understanding what users actually need. "A lot of the time users ask for what they think they want and not what they actually want," Jeanne says. Through user interviews, she works to understand what they are trying to accomplish, which often leads to better solutions than what they initially requested. "So not just building what you're told is a huge thing, especially as you become more senior in your career," she says. The goal is to make users productive and happy, not just to code. Technology keeps changing, and for Jeanne, that constant evolution makes the work fun. She has embraced AI tools as coding assistants, using them for pair programming, generating tests, and suggesting next steps. When her team piloted coding assistants, they focused on choosing a tool rather than waiting for the perfect tool. "The important thing is to get a tool and get people going and using it and being more productive," she says. The learning curve is not high, and the tools pay for themselves almost immediately. However, Jeanne says that it's important to understand what you are doing rather than using AI to replace that understanding. "It's about understanding what you're doing and not using the AI to replace it because at least with the coding assistance, it's right 90, 95% of the time," she says. She talked about an example of asking AI to generate a regular expression while pairing with a junior programmer. The AI started writing it properly but then made an error. "I noticed it right away because I know what correct is," she says. After giving it another prompt with a hint, it produced the correct result. Without knowing what correct looks like, developers cannot effectively verify and fix AI-generated code. The AI Hype Cycle Regarding concerns about AI making developers obsolete, Jeanne is pragmatic. "I've heard that enough times that I'm a little skeptical," she says, adding that this is the third or fourth time some technology has been predicted to take all the jobs. Instead, she sees AI as enabling developers to accomplish more and make users happier. She has a big backlog "that goes on forever." She says it would be great if we could get more of it done and in the hands of customers. "I think we're at that phase in the hype cycle for AI where people are talking about AI like it solves all your problems, [but] it solves some of your problems. But because there's less acknowledgement of the ones it doesn't solve, it's easier to have that skepticism." When asked if AI represents a paradigm shift or just the latest tool, she responds: "Right now, I think it's the latest tool, but I do think we're going to get to the point where we're programming at a higher level." Connect with Jeanne: X, LinkedIn, Bluesky Connect with Jim: X, LinkedIn Duke's Corner Java Podcast: Libsyn

    16 min
  4. Chris Hermansen: Don't be Afraid to Create

    12/16/2025

    Chris Hermansen: Don't be Afraid to Create

    Chris Hermansen: Don't be Afraid to Create Summary Jim Grisanzio from Java Developer Relations talks with Chris Hermansen, a Java developer, consultant, and data analyst from Canada. Chris discovered Java in the 1990s and was drawn to its free accessibility and object-oriented design. He particularly appreciated Java's straightforward single inheritance model over C++'s complexity. But Chris's path to technology came through mathematics rather than computer science. He identifies streams as Java's most transformative feature for data analysis work and praises how it improved code readability and maintainability. On consulting, Chris cautions against Silicon Valley mantras like "fail often" when applied outside prototyping contexts, and he observes cultural differences in how engineers approach problem-solving with some preferring abstract discussion while others focusing on concrete data. Chris emphasizes that technology work remains fundamentally human and stresses the importance of listening, maintaining humanity in professional life, and avoiding corporate stereotypes. For students, he notes the differences between learning with modern IDEs versus the command line tools of his era when he learned to code, so he advises that new learners to try multiple approaches to deepen their understanding. His core message, which became the episode's title, is simple: "Don't be afraid to create." Discovering Java in the 1990s Chris discovered Java in the mid-1990 when Java was announced while working as a data analyst. "Java came along and it was free to use. It wasn't open source at that point, but it was free to use," he says. "And it really intrigued me because of its object-oriented approach to things, which was something that didn't come with the platform we were working on." Unlike the purchased software products he was using at the time, Java offered a free and accessible alternative that promised serious long-term value. He also appreciated how Java's design avoided the complexities of C++, especially the problems with multiple inheritance. He and a colleague had been discussing moving from Pascal to either C or C++, but his colleague had concerns about C++'s complexity, particularly around multiple inheritance. "The first thing that really jumped out to me was the straightforward single inheritance pathway and the use of interfaces to define contractual relations between code," Chris says. Java's approach to inheritance immediately stood out as cleaner and more maintainable. Features like array bounds checking and interfaces for defining contractual relationships between code further convinced him he was learning something that would age well. "I felt that I was learning something that would wear well over time. I wouldn't turn around and look at what I'd done 10 or 15 or 20 years later and say, yuck, what was I thinking?" After committing to Java and sticking with it through the learning process, he found it repaid his effort many times over. "I liked it and I stuck with it, and I found it paid me back enormously for my investment in learning." Career Path Through Mathematics Chris's path to technology came through math rather than traditional computer science. He actually stumbled into science during the registration process at school in the 1970s and eventually pursued math after deciding against engineering. His career took him through various mathematical applications, including consulting and data analysis positions in forestry. Java's Evolution: Streams and Beyond Regarding Java's evolution, Chris identified streams as the biggest feature improvement for his work. When asked about new features that have been useful in his applications, he immediately identifies streams as transformative. "I mean, streams was the big one. Streams just made a whole difference to the way you would handle data," he says. He contrasts the old approach of writing hundreds of lines of nested for loops with the more elegant stream-based approach: "And so streams has just made that a whole lot easier. And the code is so much more readable and maintainable than the old 500 line do loops that we used to have in Fortran that turned into the 375 line for loops in Java. Anyway, so streams is a big one, a really big one for me. The biggest, I would say." He also valued the introduction of templates (generics) in Java 5 or 6, which represented a significant evolution in the language and allowed applying libraries to custom classes. He praised the Java community for keeping the platform and ecosystem viable, noting that the combination of an active developer community and a satisfied user base creates a virtuous cycle that keeps the platform evolving and improving: "There's enough Java programmers out there, enough people interested in the continuing viability of Java that they keep it going, that they modernize it, that they solve new problems with it, that they make it perform better than it ever has before." He added a "big shout out to the garbage collection people that do that amazing stuff," acknowledging the often-invisible work that performance engineers at Oracle do to make Java faster and more efficient for developers. Throughout the discussion, Chris talked at length about developers, the user community, and the technology. He has a nice habit of mixing the issues seamlessly. Check out this gem below where he beautifully concluded that Java is far more than a language because it's really a movement. "The user community is, generally speaking, pretty satisfied with [Java]. And it's a broad enough user community. It's got people like me. It's got people still doing desktop Java. It's got people using it on servers. And there's a whole tool ecosystem out there. Personally, I prefer working right at the command line. I always have. But the application that I mentioned we built using NetBeans, which came out of Sun originally. And it's quite a nice IDE. I don't think it's the most popular one. It doesn't really matter. It's still a very nice one. And it gave us a big part of that long-term support. And lately, I find myself using other JVM languages. So it's not just Java. It's the JVM that underpins it, that has permitted a flowering of alternative approaches to things that, generally speaking, work very well together with Java. So, it's a pretty cool thing. It's a movement. It's not just a programming language." Consulting, Professionalism, and Cultural Differences On consulting and professionalism, Chris stresses the importance of contributing to the team to best serve customers. He cautions against embracing some Silicon Valley software mantras — such as "fail early, fail often" — when applied outside their intended prototyping context. "And I know failure is a thing that people talk about in software development. Fail early, fail often. But you don't hear consultants saying fail often. It's not a good look for a consulting company," he says. Instead, Chris focuses on engineering being technically excellent and using open communications to help ensure the team's success. "In a consulting organization, you really have to be a team player," he says. He clarifies that getting prototypes out for feedback certainly has merit: "Get something out there and [letting] people throw rocks at it and [recording] what they say [that's] false and recognize that, okay, you failed, but at least you moved the ball down the field. I'm a huge fan of prototyping." Throughout the years in his career Chris also observed cultural differences in problem-solving approaches around the world. He says that some cultures prefer abstract discussion while others focus on concrete data. "Never mind all these grand theories. Let's actually look what we have. And really, you know, like don't go down that rabbit hole either. Look at what you have and base things on the reality that you know about," he advises. He warns against getting lost in theoretical discussions: "Resist the old, you know, the medieval concept of how many angels on the head of a pin kind of thing. Just don't go there." The Human Side of Technology Work Chris emphasizes that technology work remains fundamentally human. Near the end of the conversation, Chris focuses what he sees as most important: "I would just emphasize maybe that we're human beings here and we're driven by our human desires and wills. And as you rightly pointed out, cultural things roll into that," he says. Despite all the technical discussion about tools, languages, methods, and preferences, the work is ultimately done by human beings with human needs and motivations. Cultural factors, listening skills, and collaborative team approaches matter as much as technical competence. "Remember, you spend a long time of your life at your job. And so, it's important that that contributes to your humanity and that your humanity contributes back." He encourages developers to remember their humanity throughout their careers, to contribute meaningfully to their teams and communities, and to avoid becoming caricatures of the latest corporate culture. "It's really important to remember that you're part of a group of human beings here. You don't want to be a Dilbert comic," he says, using the comic strip as a reference point for the dehumanized corporate worker trapped in absurd bureaucracy. On the importance of listening, Chris shares wisdom from a sign he saw years ago: "If God had intended man to speak more than he listened, he would have given him two mouths and one ear. Listen more, say less." When discussing custom solutions versus off-the-shelf tools, and after discussing how being familiar with algorithms allows you to blend approaches for better solutions, Chris delivers what became the title of the episode: "Basically, you know, if there's not something off the shelf that —  Don't be afraid to create!" This is a message that Chris encourages all developers to embrace because they have such advanced

    59 min
  5. Barry Burd: Teaching Java as an Art Form

    12/02/2025

    Barry Burd: Teaching Java as an Art Form

    Jim Grisanzio from Java Developer Relations talks with Barry Burd, a computer science teacher, an author, and the co-leader for two Java User Groups (JUGs). Barry is based in New Jersey and he's taught at the undergraduate level for decades. His journey with Java began in 2004 when he attended small user group meetings of just five or six people. Those gatherings, once part of the Amateur Computer Group of New Jersey, have evolved into the Garden State Java User Group and the New York Java SIG, which now regularly feature Java Champions and prominent speakers from the Java development community. The transformation of the two JUGs on the East Coast of the U.S. reflects the broader growth of the entire Java ecosystem globally.  Barry's teaching philosophy centers on passion, enthusiasm, and visualization. He works to help students see programming concepts as complete mental pictures rather than just syntax. His classroom approach emphasizes active interactions with as many questions as possible. He tries to create what he calls a party atmosphere rather than a boring traditional lecture setting. He believes strongly in meeting students where they are and encouraging those who love the material while supporting those whose passions may lie elsewhere. What distinguishes Barry's perspective is his view of computer science as an art form. He frequently compares elegant code to works of art. He asks students who question the practical value of certain technical concepts whether they would ask the same question in a course about the Mona Lisa. This artistic perspective extends to his appreciation of Java as well. He marvels at the language's thoughtful design, where features fit together as a unified whole rather than random pieces of technology thrown together haphazardly. Java's appeal for Barry grows from multiple sources. The language's backward compatibility has been crucial for his work as an author and a teacher. He says that only one program broke across multiple editions of his books over the years. He contrasts this long term stability with other platforms that change frequently and force him to spend time fixing previously working code. The elegance and careful thought behind Java's design resonates deeply with him. He appreciates the early decisions about inheritance and interfaces and the entire evolution of Java from the engineers under the stewardship of architects like Brian Goetz at Oracle. Barry says that the six-month release cycle introduced in recent years has injected new life into the Java ecosystem. He sees the platform as self-sustaining now with strong leadership that shows no signs of fading. Living near New York City, he says that financial institutions depend on Java's industrial strength reliability for obvious reasons. The technology serves two audiences well, he says, those who need rock-solid, enterprise-grade systems and those like himself who appreciate the beauty of well-crafted software. When asked why Java is so great, Barry says: "I guess the other reason is that it's good for industrial strength programming. People in the area of the world where I live in, close to New York City, in the financial district, rely on it. It's just not breakable the way other platforms are." If you ever have a chance to take a software development class from Barry Burd, take it. You'll love it.  Barry Burd https://x.com/allmycode https://www.linkedin.com/in/barry-burd/recent-activity/all/ Jim Grisanzio  https://x.com/jimgris  https://grisanzio.com  Duke's Corner Java Podcast  https://dukescorner.libsyn.com/site/  https://grisanzio.com/duke/

    1h 12m
  6. Mattias Karlsson: I think it's Brilliant

    09/15/2025

    Mattias Karlsson: I think it's Brilliant

    Jim Grisanzio from Oracle Java Developer Relations talks 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 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. Mattias Karlsson https://x.com/matkar   Jim Grisanzio https://x.com/jimgris   Duke's Corner https://dukescorner.libsyn.com/site   Podcast Archives, Transcripts, Quotes https://jimgrisanzio.wordpress.com/duke

    42 min
  7. Venkat Subramaniam: I Teach Because I Learn

    09/05/2025

    Venkat Subramaniam: I Teach Because I Learn

    Jim Grisanzio from Java Developer Relations talks with Venkat Subramaniam who 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, author, speaker, founder of Agile Developer, co-founder of the dev2next conference, and teacher at the University of Houston. In this conversation, which is part of an ongoing series honoring Java pioneers, Venkat expresses profound humility about his accomplishments and credits industry giants and his passion for learning and sharing technical knowledge. He reflects on leaving his own company years ago to focus on teaching and technology, writing books like Cruising Along with Java, and speaking at over 45 conferences and 30 Java User Groups — every single year! Venkat has one of the most impressive global speaking schedules of anyone in the Java community. Venkat praises Java User Group leaders as "unsung heroes" for their organizational efforts and 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. Venkat 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 to help welcome 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. Venkat Subramaniam https://x.com/venkat_s   Duke's Corner Java Podcast https://dukescorner.libsyn.com/site/   Jim Grisanzio https://x.com/jimgris

    41 min
  8. Bruno Souza: My Greatest Pride is the Community

    08/31/2025

    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. Bruno left Sun and then returned, and he also joined the JCP (Java Community Process). Now all these years later we have OpenJDK, and open JCP, and hundreds of independent JUGs that can participate in community building and also Java development. "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!" — Bruno Souza Bruno Souza https://x.com/brjavaman  https://x.com/SouJava  Duke's Corner Java Podcast  https://dukescorner.libsyn.com  Jim Grisanzio  https://x.com/jimgris  https://jimgrisanzio.wordpress.com https://www.linkedin.com/in/jimgris/

    40 min

Ratings & Reviews

4.8
out of 5
8 Ratings

About

Duke's Corner is a forum for conversations with Java developers. Tune in to connect with the community and learn how developers are innovating with Java around the world. Host: Jim Grisanzio, Oracle Java Developer Relations @jimgris