Keynote – James Edward Gray II
summary
Argues code’s primary purpose is to communicate with the reader and shows concrete tradeoffs between quick spikes and long term design, claiming spikes often blow up later. Uses examples like dumping a one off report into a reports rake file, parsing IRC messages first with a giant regex then refactoring to StringScanner and small methods that actually work better, cites libraries like Sinatra and RestClient, mentions Google burn metrics and the pragmatic 80% rule for spikes versus the cost of refactoring.
AI-written summary · about
