Has anyone gone months without introducing observed bugs into production? To what do you attribute your defect-free code?
-
-
This has been my experience exactly. Think through what must happen. Think through appropriate ways to break that down with an eye towards building those pieces back up. Understanding is essential for reliability.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
For example, each part of the system could be run completely independently as it's own command line tool, but each command line tool was a _tiny_ wrapper of that particular component. So I could run shell scripts to test just video decoding, or just download scheduling, etc.
-
Basically, everything
@stuarthalloway said in his "Running With Scissors" talk, but using bash, Go's super fast compiler, and tiny wrapper CLI apps as my "REPL". -
Also made aggressive use of Go's struct embedding to emulate Clojure's ability to just mix and match keys in maps. Let me create aggregate configuration structures that could be cut up in to pieces easy for each subsystem or the various driver programs.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.