The AI IDE for prototype to production. Kiro helps you do your best work by bringing structure to AI coding with spec-driven development. Kiro turns your prompt into clear requirements, system design, and discrete tasks. https://kiro.dev/

A continuous profiler/logger for Python with microscopically small recordings, no overhead, and super-fast rendering using PyScript https://github.com/micrologai/microlog

Java just turned 30. For a language everyone loves to roast as “verbose” and “corporate,” it somehow powers banks, Netflix, and an entire generation of Minecraft coders. In this video, I walk through why Java survived when so many “better” platforms didn’t - from the JVM’s “write once, run anywhere” promise to enterprise reliability, Spring’s rise, modern performance (JIT/GraalVM), and the broader JVM ecosystem. Happy 30th, Java. You’re boring… and that’s exactly why you win.

In the evolving landscape of software delivery, platform engineering has emerged as a discipline focused on enabling developers to ship reliable software quickly, safely, and consistently. One of the most powerful principles shaping this movement is the idea of shifting left—bringing traditionally late-stage concerns (like testing, security, and infrastructure) closer to the beginning of the development lifecycle. What “Shift Left” Means Traditionally, many software quality, security, and operational checks were performed late in the pipeline—sometimes only after code reached staging or production. This created bottlenecks, expensive fixes, and slow delivery cycles. The shift left philosophy moves these activities earlier (“to the left” on a timeline). Instead of catching issues at the end, teams build guardrails and feedback loops into development workflows so developers discover and resolve problems early. In the context of platform engineering, this shift means embedding operational excellence, security, and compliance directly into the developer experience through tooling and automation. Why Shift Left Matters in Platform Engineering Platform teams exist to reduce friction for developers, not add new layers of complexity. When applied effectively, shift left practices: - Accelerate Delivery – Early detection of issues reduces rework and shortens release cycles. - Improve Quality – Developers catch bugs, vulnerabilities, and misconfigurations before they reach production. - Enhance Security – Security scanning, policy enforcement, and compliance checks are embedded into CI/CD pipelines. - Boost Developer Autonomy – Self-service platforms give engineers the ability to deploy infrastructure and services safely, without depending on centralized ops teams. - Lower Costs – Fixing issues earlier is significantly cheaper than addressing them post-release. Examples of Shift Left in Platform Engineering 1. Infrastructure as Code ValidationPlatform teams provide automated checks for Terraform, Helm, or Kubernetes manifests so developers know immediately if their infrastructure definitions violate policies. 2. Integrated Security ScanningTools like Snyk or Trivy can be built into pipelines, ensuring vulnerabilities in dependencies or containers are flagged before deployment. 3. Automated Testing EnvironmentsDeveloper platforms can spin up ephemeral environments on-demand, letting teams test features in production-like conditions without waiting for shared staging environments. 4. Observability by DefaultPlatforms can auto-instrument services with logging, tracing, and metrics so developers gain visibility into performance during early stages of development. 5. Policy as CodeGovernance checks (like Open Policy Agent) shift left by allowing rules to be enforced automatically in pipelines and developer tooling.

Hugging Face has unveiled FinePDFs, the largest publicly available corpus built entirely from PDFs. The dataset spans 475 million documents in 1,733 languages, totaling roughly 3 trillion tokens. At 3.65 terabytes in size, FinePDFs introduces a new dimension to open training datasets by tapping into a resource long considered too complex and expensive to process. https://www.infoq.com/news/2025/09/finepdfs/