Build better software with The Theory of Constraints | Swizec Teller
# scheduling workloads to run on humans
Some computational workloads in human organizations are best "run on a CPU": take one single, highly competent person and assign them a task to complete in a single-threaded fashion, without synchronization. Usually the best fit when starting something new. Comparable to "building... See more
Andrej Karpathyx.com
we have completely changed our engineering philosophy @every because of Claude Code
we called it Compounding Engineering:
Each feature should make subsequent features easier to build, not harder.
@kieranklaassen just wrote THE definitive guide to each step of... See more
Goldratt’s lesson:
System performance is limited by its constraint. Improving non-bottlenecks does not improve overall throughput.
For years, I’ve felt that writing lines of code was never the bottleneck in software engineering.
The actual bottlenecks were, and still are, code reviews , knowledge transfer through mentoring and pairing, testing , debugging , and the human overhead of coordination and communication . All of this wrapped inside the labyrinth of tickets, planning... See more
The actual bottlenecks were, and still are, code reviews , knowledge transfer through mentoring and pairing, testing , debugging , and the human overhead of coordination and communication . All of this wrapped inside the labyrinth of tickets, planning... See more