myg204

10 ms·

61.
by myg204 13y ago
I recommend the xv6 source and commentary. Here's the link: http://pdos.csail.mit.edu/6.828/2012/xv6.html (has a pdf you can print out along with C code listing, and with nice references). It's very simi
62.
by myg204 13y ago
Even his comments on that wm config file are a great read...inspiring to see such thoughtfulness on all levels.
63.
by myg204 13y ago
Correct. One can see that very well defined in the NASA/JPL software guidance documents. Definitely not agile, but works for their situation.
64.
by myg204 13y ago
Very nice list. I have read maybe 30% of the books listed, and I agree, they do contain great and subtle insights. Definitely books that I like to pick up again and again. I'd add those 2 to the list: (i) "Programming on Purpose
65.
by myg204 13y ago
Corollary (from my fortunes file): Deleted code is debugged code. - Jeff Sickel
66.
by myg204 13y ago
> Discretionary bonuses are full of shit. It's both a carrot and a stick for the company over the employee.
67.
by myg204 13y ago
A lot of the verbosity in Go comes from error handling; the language forces you to deal with errors (I think it's a good thing, some may disagree). Expressiveness is real, 'duck typing' does give it a feel of scripting langu
68.
by myg204 13y ago
May not be normally distributed, but follow a power law (fatter tail)
69.
by myg204 13y ago
IMHO, (1) is the not only think that counts in the end. A 'failed' (as in (1)) concept may have a second life in future works. Also, in the case of plan9 some ideas did get traction (UTF-8 for example), some didn't so it's not all bad. Com
70.
by myg204 13y ago
Yes, (1) commercially it went nowhere, (2) technically it's a complete working os with original ideas implemented in a masterful way. Not bad I think!
71.
by myg204 13y ago
Simplicity in design is still a panacea, only good programmers can do it on non trivial systems. Go will allow for better clarity, but beautiful code will not write itself.
72.
by myg204 14y ago
or have it run every time you save a file
73.
by myg204 14y ago
Interesting answer. Those 2 bits are great, had to highlight them... The poetry lies in what those machines do; the art is in the output. To me, writing a boring program whose code is very clever is like writing a boring poem in beautiful c
74.
We Are What We Quote(opinionator.blogs.nytimes.com)
1 points by myg204 14y ago|0 comments
75.
by myg204 14y ago
Phillipe Flajolet (algo research, passed away in '11)
76.
by myg204 14y ago
Ah, yes indeed. I suppose yes/no scheme may be applicable to command line tools where the user actually has to type, in the model ui world, it's not really applicable.
77.
by myg204 14y ago
A random idea, maybe an alternative is to label the buttons w/ the actions themselves, i.e. no message + Y/N,Ok/Cancel labels. For Example, instead of: Would you like to cancel this transaction? {Yes,No} just have: {Continue Transaction|
78.
by myg204 14y ago
Go is 3 years old. Also, golang addresses more than just this issue, the concurrency approach is interesting for example.
79.
by myg204 14y ago
One exception though. Piping unix command this way allow handling of _very_ large file (stream model), whereas R requires loading the whole content in memory.
80.
by myg204 15y ago
Oh, would love one too :) username at gmail dot com. Thanks!
81.
by myg204 17y ago
The upper class is not wearing FCUK, they're wearing Hermes. It's the middle class that's wearing FCUK.