Best of InfoWorld — October 2025

1. 1
   Article

   InfoWorld·34w

   Why we need junior developers

   Companies are increasingly avoiding hiring junior developers and relying on AI for basic coding tasks, but this creates long-term problems. Junior developers are essential for the future pipeline of senior talent, bring fresh perspectives to established teams, and provide necessary balance in team dynamics. Teams with only senior developers risk becoming siloed and lacking the collaborative knowledge transfer that occurs through mentoring relationships.

   257

   71
2. 2
   Article

   InfoWorld·30w

   What’s the Go language really good for?

   Go has evolved from a curiosity to a battle-tested language powering major cloud-native projects like Docker and Kubernetes. Known for its simplicity, fast compilation, and built-in concurrency features (goroutines and channels), Go excels at building distributed network services, cloud applications, and standalone tools. While it offers automatic memory management and cross-platform portability, it deliberately omits features like macros and produces larger binaries. The language recently added generics in version 1.18 after years of deliberation. Go's future remains strong in cloud infrastructure and network services, with emerging interest in AI workloads, though it faces competition from Python in ML/AI and Rust in systems programming.

   123

   11
3. 3
   Article

   InfoWorld·31w

   AWS DNS error hits DynamoDB, causing problems for multiple services and customers

   A DNS resolution error in AWS's US-EAST-1 region caused widespread DynamoDB API failures, affecting multiple AWS services and customers including Perplexity, Canva, Venmo, and others. The incident began shortly after midnight Pacific Time and was resolved within three hours through initial mitigations. The outage highlighted how single points of failure in cloud infrastructure can have global consequences, even when the root cause is isolated to one region.

   36

   2
4. 4
   Article

   InfoWorld·32w

   Java or Python for building agents?

   Choosing between Java and Python for AI agents should depend on your team's existing expertise and technology stack, not trends. While Python dominates AI development due to its accessibility and rich ecosystem, Java developers can build equally effective agents using frameworks like Embabel. Organizations will achieve faster AI adoption by leveraging their current tools and skills rather than switching to unfamiliar technologies. By 2028, 80% of generative AI applications will be built on existing data management platforms, reinforcing the value of working with what you already have.

   32

   6
5. 5
   Article

   InfoWorld·31w

   Anthropic extends Claude Code to browsers

   Anthropic launched Claude Code on the web as a beta research preview for Pro and Max users, allowing developers to use the AI coding assistant directly from browsers or smartphones without a terminal. The service runs coding tasks on Anthropic-managed cloud infrastructure in isolated sandboxes, supports parallel task execution across repositories, handles Git interactions via secure proxy, and automatically creates pull requests. It's particularly effective for repository mapping, routine tasks, bug fixes, and back-end changes with test-driven development.

   19
6. 6
   Article

   InfoWorld·31w

   Using the SkiaSharp graphics library in .NET

   SkiaSharp is a .NET wrapper for Google's Skia 2D graphics library, providing cross-platform drawing capabilities for Windows, iOS, macOS, Linux, and Android. The library serves as the rendering foundation for .NET UI frameworks like MAUI, Uno Platform, and Avalonia. Developers can use SkiaSharp directly to create custom visualizations and controls by working with canvases, drawing primitives, text rendering, bitmaps, and transformations. Microsoft and Uno Platform recently announced they will co-maintain the project, which currently lags behind the main Skia build by about two years.

   16

   1
7. 7
   Article

   InfoWorld·29w

   Will JavaFX return to Java?

   A proposal to reintegrate JavaFX into the Java Development Kit has emerged in the OpenJDK community, seven years after its removal in Java 11. The proposal argues that original separation reasons—JDK bloat, independent evolution needs, and Oracle-to-Gluon development transfer—are less relevant today due to modularization, synchronized releases, and open source availability. Oracle responded by stating they're investigating options to improve JavaFX accessibility within the JDK, though no specific plans were announced.

   13