It started with a simple idea: I wanted to create my own CV in pure Java. No big framework. No designer tool. No attempt to overengineer everything before I even had one page. Just Java, PDFBox, and the confidence every developer has right before a supposedly small task becomes a real project. At first I thought: how hard can it be? Very quickly I found myself inside the classic PDF generation loop: ...
Building a PDF engine in Java is a useful way to meet a lot of hidden complexity at once. Text measurement, pagination, styling, rendering order, reusable components, API design, testing, and performance all become visible very quickly. This is not a tutorial about drawing text into a PDF. It is a reflection on what I learned while building the layout engine behind GraphCompose: the hard part is rarely one isolated algorithm. The hard part is making many small rules work together until the final document feels reliable. ...
AI tools make some developers uncomfortable because they blur a familiar line. If a tool can suggest code, explain an API, draft a test, or refactor a function, does using it mean the developer is cheating? I do not think so. But I also do not think AI removes responsibility from the developer. Tools have always changed the work Modern development is already tool-assisted. We use IDE completion, static analysis, linters, formatters, frameworks, dependency managers, documentation search, and generated code. ...
On June 9, 2026, Anthropic announced Claude Fable 5, a Mythos-class model made available for broader use with stricter safety layers around it. On June 12, Anthropic added an update saying that access to Claude Fable 5 and Claude Mythos 5 was temporarily unavailable while they worked to restore it. That timeline is already interesting. Frontier AI releases are starting to look less like simple product launches and more like controlled deployment systems: a powerful model, safety routing, monitoring, fallback behavior, access policy, pricing, and operational risk all wrapped together. ...