quasit1

5 ms·

1. 1.▲
   by quasit1 5y ago

   I've spent 10 years writing security critical C code. There's no problem writing secure code in C. You just have to stop being clever and prioritize security above "speed". Your code will probably be fast enough anyway.
2. 2.▲
   by quasit1 5y ago

   I agree, I have worked at 3 different places that implemented demo-driven development. It always looks good the first couple of weeks or even months, but then it goes down hill, just as you describe. So much important work is not really pos
3. 3.▲
   by quasit1 5y ago

   I've worked in such places. The reason it is that way is because you will receive a broken description/specification/story of what you are supposed to implement. You have a choice to make when that happens, you either impleme
4. 4.▲
   by quasit1 5y ago

   I feel as if it depends a lot on the code. I sometimes read code for fun. Some code read like an essay, some like a book and other code read like a collection of poetry. So I feel as if all 3 can apply, sometimes some of them at the same ti