steerb

5 ms·

1. 1.▲
   by steerb 14y ago

   Thanks for the clarification. This sounds valid. In my last question I was just wondering how or when you (or others) tend to improve their coding style. For me its mostly when reading other peoples code and noting that a) certain aspects a
2. 2.▲
   by steerb 14y ago

   This does really sound unusual. For me, the ratio of reading to writing is about 4:1. Are you sure you are not writing too much new code, because you didn't invest the time to properly understand the existing one? When you mostly work with
3. 3.▲
   by steerb 14y ago

   Using the heap layout, you can sometimes even eliminate branch misspredictions and subsequent (expensive) pipeline flushes. The basic idea is to allow your compiler to use predicated instructions. Do do this, you have to transform control d
4. 4.▲
   by steerb 14y ago

   This sounds somewhat similar to (software) transactional memory.
5. 5.▲
   by steerb 14y ago

   I tend to agree. Let's assume a sufficiently smart compiler can parallelize 90% of our hot code. Now considering Amdahl's Law, we cannot achieve a speedup greater than 10 and are therefore stuck. Adding 10 or more cores won't do any good to
6. 6.▲
   by steerb 14y ago

   I guess that the kernel cannot know that the application (in your case scp) will not try to touch the data ever again. The current default behavior, which you call crazy, does however favor programs which do actually need the data that was
7. 7.▲
   by steerb 14y ago

   Is this a way of saying one should always live on the edge of incompetence? Edit: I ask this, because I have difficulties applying your ideas on fields where I don't have any good teachers around (e.g., lets say I want to become a better co