ssrc

6 ms·

31.
by ssrc 3y ago
Well, there's the relatively recent Schön scandal. https://en.wikipedia.org/wiki/Sch%C3%B6n_scandal
32.
by ssrc 3y ago
What I've seen in my career is that when developers were motivated by joy and wonder like 2830 said, or by a sense of mission, etc. productivity and customer satisfaction was high. But when the emphasis turned to productivity (CMMI 5,
33.
by ssrc 3y ago
And yet at some complexity level you have things like ARINC 653 where the usual implementation is to have a classic RTOS running on each of the partitions provided by the "application executive", and today's serverland is hyp
34.
by ssrc 3y ago
I mean, I don't like shellfish and people tell me it's my loss, but as long as I have a balanced diet why should I care?
35.
by ssrc 3y ago
* This book, PAIP, by Peter Norvig * SICP, by Abelson and Sussman * Lisp (3rd ed), by Winston and Horn * The Art of Prolog, by Sterling and Shapiro It's like the same book written by different authors, and all of them are good.
36.
by ssrc 3y ago
In the late 70s to early 80s that wasn't an obviously wrong idea, especially because in the posts above, as I understand it, when they say hardware it mostly means microcode, which is more software than hardware. At that moment many ar
37.
by ssrc 4y ago
I try to write informative comments. That said, 99% of the comments I see are * Useless, like "locks the mutex" before a mutex.lock(). * Contrary to the code, like "This parameter contains the proc name without the instance&q
38.
by ssrc 4y ago
He would have looked like Omni-Man.
39.
by ssrc 4y ago
The jack-in-the-box (or hellraiser's box) style of OOP. You call a succession of 0 or 1 argument methods that change the object state until suddenly something happens.