seventh-chord

6 ms·

31.
by seventh-chord 7y ago
Genuinely curious about your last point (don't know much about the topic). Is english intrinsically better at this, or is it because of the presence of jargon? Is it a studied phenomena, or is it something most people feel?
32.
by seventh-chord 7y ago
Not quite sure what point the author is trying to make? He agrees that lines of code are a bad measure of productivity because, yet claims that the average he computes can help him predict future development times. Then he explicitly points
33.
by seventh-chord 7y ago
Whenever I try to use linux on hardware, either audio doesn't work without stuttering, video doesn't work without tearing or some package manager dependency issue rears its ugly head. From my perspective, it seems inconceivable to
34.
by seventh-chord 7y ago
There is absolutely no requirement from the hardware that the stack be any particular size
35.
by seventh-chord 7y ago
in languages like c, rust or go, where you can put arbitrary data on the stack, it seems to me as if such issues are less common because you dont have to worry about initializing pointers and allocating memory unless you actually want to p
36.
by seventh-chord 7y ago
"Making everything a reference: The Billion Dollar Mistake" is the talk I want to see
37.
by seventh-chord 7y ago
For norway, our central statistics agency[1] keeps track of anual traffic fatalities. They provide numbers for each year since 1946, though detailed statistics are only available since ~2000. In 1946, there were 161 fatalities and 675 grave
38.
by seventh-chord 7y ago
Regarding having tons of exit points, I find it actually adds no more cognitive load to use only a single return per function, compared to having multiple returns and keeping resource-freeing up-to-date for each. Most of the challenge in wr