Software Engineering

Software Development

Software is a harness for computation

• Write code and experiment instead of talking and planning

• Keep experimental and mock data alongside production code

• Minimize restart times and restart the project often

• Compose functions and flow data through pipes

AI has compressed the time from idea → working app from weeks/months to hours. As a result, software is becoming more like content rather than just a utility. However, while content quickly fades, software accumulates value once built.

Anish Acharya on Twitter / X

https://t.co/MoVeOzXfVA— Anish Acharya (@illscience) January 15, 2026

https://x.com/illscience/status/2011893150265327693

Interactive high-velocity style development rules

A high-velocity style of software development

Some ideas from my personal style of software development based on exploration, regular code changes and keyboard speed

https://mihaiolteanu.me/interactive-dev

Simple sabotage for software

How to sabotage software productivity, in the style of CIA

https://erikbern.com/2023/12/13/simple-sabotage-for-software.html

Objective

• Functionally complete and useful even without new features.

• No security flaws and no additional patches needed.

• Minimal external dependencies at runtime (independent).

Software can be finished - Ross Wintle

You probably don't want to build "finished software". But what can we learn by thinking about it as a concept?

https://rosswintle.uk/2025/10/software-can-be-finished/