chairleader

7 ms·

31.
by chairleader 10y ago
"Some of the most interesting and deadly aspects of the enemies were bugs caused by improperly terminated boundary conditions in the algorithms. Often these bugs produced behavior far more interesting and psychotic then anything I conc
32.
by chairleader 10y ago
You could try sketching out on paper or a whiteboard what control structures you would need to pull off the DSL, and then exposing those control structures as utility classes instead of a DSL. For example, if you are building up a queue of
33.
by chairleader 11y ago
Indeed, the relativism of all of this is very important. Can you put your finger on what you boss does that is unacceptable? Is it because of: * the way she/he makes decisions? * the way she/he provides feedback? * the way she&#x2
34.
by chairleader 11y ago
If you have an inconsistent naming convention in your directory structure, this could speed things up/save some memorization. I'm not a fan of adding features that make poor choices less painful, but I could see using it for a lit
35.
by chairleader 11y ago
Indeed, Rota's approach to teaching seems to mirror the application of mathematics in general... He acknowledges that concepts have prerequisites, and that certain topics are misleading or dead ends. You might even call the act of buil
36.
by chairleader 11y ago
OCR'd from the incident report: A Google Lexus-model autonomous vehicle ("Google AV") was traveling in autonomous mode eastbound on El Camino Real in Mountain View in the far right-hand lane approaching the Castro St. interse
37.
by chairleader 11y ago
I'm finding the description of the accident a little... passive. Has anyone found other reporting or even video of the incident itself?
38.
by chairleader 11y ago
By my read, it prints a list of all Ruby files in your project sorted by number of commits against them. It may take a long time to complete depending on number of files and number of commits. YMMV, I am not a BASH shell.
39.
by chairleader 11y ago
Funny you mention it, I'm also a bit anti-chaining for the same reasons. Do we need a cute name to describe the practice of optimizing code for maintainability? "Craftsmanship" speaks to the building process, what should we c
40.
by chairleader 11y ago
True, we are the ones responsible for our integrity and we often live with our mistakes, paying for poor design choices during later maintenance cycles. Just be aware that it can be easy to get lost in a yak-shaving exercise doing your clea
41.
by chairleader 11y ago
This is extremely validating to read. How many times have I battled with DRYists over which solution is "better." I've happened upon the pattern of code growth described here after years of encountering and resolving pain poi
42.
by chairleader 11y ago
+1 This is a nice reminder about how "organic" this domain is. I agree, even if I read this cover to cover, I wouldn't be ready to nail a bioinformatics job interview. As an armchair biologist (among other things,) this paper
43.
by chairleader 11y ago
Interesting set of articles. "Intuition isn't Optional"[1] could explain why pursuing simple solutions and good naming is important in software. http://betterexplained.com/articles/intuition-isnt-optional
44.
by chairleader 11y ago
I've used ditaa http://ditaa.sourceforge.net/ for similar diagrams, and this Jekyll plugin to use it w/in Markdown Documents: https://github.com/matze/jekyll-ditaa
45.
by chairleader 11y ago
Experienced composers and arrangers will have spent years writing on staff paper, building speed and accuracy. This shorthand and muscle memory will be irreplaceable for their target market. You get a sense of the experience watching the vi
46.
by chairleader 11y ago
I see a lot of promise here as well. I'm not sure if the world is ready to express everything in terms of graphs, though.