If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

Software 3.1? - AI Functions

Moving beyond Software 3.0’s generate-and-verify loop, AI Functions execute LLM-generated code at runtime, return native Python objects, and use automated post-conditions for continuous verification. This is Software 3.1: where AI doesn’t just write code—it runs it.

Why LLMs Can’t Write q/kdb+: Writing code Right-to-Left

In my previous post I showed how LLMs struggle with coding in q/kdb+; having immediate feedback loops using the q-MCP server does help a bit, but could we do better? Diving deep, a first problem…

GitHub - sdzx-1/polystate: Polystate: Composable Finite State Machines

Polystate: Composable Finite State Machines. Contribute to sdzx-1/polystate development by creating an account on GitHub.

GitHub - Kaamuli/Bloxi: Check github for full desc: MIT – do what you want, just give credit.

Check github for full desc: MIT – do what you want, just give credit. - Kaamuli/Bloxi

AI Coding Agents

GitHub - Kimbsy/autology: A hot take on Lisp metaprogramming

A hot take on Lisp metaprogramming. Contribute to Kimbsy/autology development by creating an account on GitHub.

GitHub - approximatelabs/sketch: AI code-writing assistant that understands data content

AI code-writing assistant that understands data content - GitHub - approximatelabs/sketch: AI code-writing assistant that understands data content