Has anyone gone months without introducing observed bugs into production? To what do you attribute your defect-free code?
-
-
Replying to @potetm
Yes: Simplicity. I built a real-time video service that, after an extended shadow-traffic launch, ran for nearly a year with only one hiccup before I stopped paying attention to it. Extreme simplicity is what enabled that stability.
2 replies 2 retweets 9 likes -
Replying to @BrandonBloom
In other words, you methodically broke the system into parts, each of which you understood in their entirety?
2 replies 0 retweets 0 likes -
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.
1 reply 0 retweets 1 like -
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".1 reply 0 retweets 2 likes
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.
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.