Fair criticism of Jupyter Notebooks, and how hard it is to apply good software engineering: https://medium.com/@alexander.mueller/5-reasons-why-jupyter-notebooks-suck-4dc201e27086
It's hard to transition from code in a notebook to standalone program or reusable library in my experience. I think a less stateful design would really help.
miniblog.
Related Posts
Anthropic used Claude to write a C compiler in Rust (CCC). I've really enjoyed following the discussion.
The initial post shows how they wrote the harness with GCC as an oracle and a prompt specifying a design using SSA. The author has clear domain expertise.
https://www.anthropic.com/engineering/building-c-compiler
Igalia's post on self-hosting CI runners is a masterclass in build engineering. It shows dealing with weird API constraints, but still finding good designs.
I also learnt that some CI systems use OCR on Apple's installers to automate!
On building great engineering teams with UX empathy, and the role of product managers on engineering-led teams.
