This week: making money code harder to get wrong, why Shopify left React Native for native apps, the case for and against letting AI agents ship code nobody reads, eight ways to cut documents up for AI search, Java's own JSON parser, and a Blender engineering job that is open to remote applicants.
Fintech
Alvaro Duran · The Payments Engineer Playbook · 14 October 2026
If you build anything that moves money, from M-Pesa integrations to wallets and loan ledgers, this is a short, practical case for designing code so that mistakes cannot compile. Duran takes two ideas from the book Secure by Design: give each stage of a payment its own type, handing over to the next like runners in a relay, with states that only move forward; and stop passing raw strings and numbers around, by wrapping amounts and IDs in types of their own that carry their rules, so swapped arguments fail at compile time. His warning story is a startup whose records drifted a few cents from its vendor's until users saw a $5 purchase show up as $4.98.
Mobile
ByteByteGo · 20 October 2026
Shopify adopted React Native in 2020 and is now moving its apps back to native Swift and Kotlin. The reason is new: AI coding agents made writing each feature twice cheap, as long as there is a working app to copy from and a way to check what the agents produce. Shopify broke the rewrite into small checkpoints, each passing behaviour tests, a visual comparison with the old app, an adversarial code review and a developer's review. The Shop app went native in 12 weeks; Android start-up time roughly halved, from about 4.4 to 2.2 seconds, and the Android app shrank from 293 MB to 184 MB. Worth reading before you choose a cross-platform framework for your next app, and as a model for checking AI-written code.
AI
Pavan Belagatti · on daily.dev · 18 October 2026
A "dark" software factory, named after factories that run with the lights off, is a pipeline in which AI agents plan, write, review, test, ship and monitor code, and no person reads the pull requests: automated tests and checks decide what goes live. Belagatti's short post is a useful reality check on the idea. The biggest risk, he argues, is "comprehension debt": when production breaks, nobody on the team has read the code that shipped. His advice is to keep fully autonomous pipelines for repetitive, well-tested, low-risk parts of a system, and for most teams to keep people at the approval gates. His longer guide on DZone walks through each stage of such a pipeline, built around Port, the tool he uses.
AI
ByteByteGo · 17 October 2026
If you are building an assistant that answers from your company's documents, how you cut those documents into pieces decides what it can find. This issue sets out eight ways to do it, from fixed-size pieces with a little overlap, through splitting on headings or wherever the topic changes, to "late chunking", which reads the whole document first so that a line like "its revenue grew 3%" keeps track of what "its" means. Short, well illustrated, and a useful checklist before you blame the model for bad answers.
Java
OpenJDK · Naoto Sato, Paul Sandoz, Justin Lu and Stuart Marks · integrated for JDK 28
Java is getting a JSON parser of its own, in a new jdk.incubator.json module. It is deliberately small: it reads and writes standard JSON, with one type each for strings, numbers, booleans, null, objects and arrays, and leaves out data binding and streaming. The proposal says plainly that it is not meant to replace Jackson or Gson. It is aimed at the everyday job of pulling a few values out of a JSON response without adding a library, which takes a few lines in Python or Go and should in Java too. As with every incubator module, you have to switch it on with --add-modules before you can use it.
Jobs
Blender · Amsterdam · two openings, reported 16 October 2026
The open-source 3D tool used by animators and game studios is hiring a senior software engineer, who needs strong C++ and some Python for Blender's add-on API, and a junior or regular DevOps engineer. The DevOps role is in the office in Amsterdam, but for the senior role Blender says it will consider people who want to work remotely. If you write C++ and have contributed to open source, it is worth reading the listing.
How we pick: each week we go through the developer feeds we follow, read the originals, and keep the few a developer in Kenya would want to know about. Every link goes to the author’s own page.
