Today I found myself referring to: File types In Linux/Unix explained in detail. Basically:
- Regular file (-)
- Directory file (d)
- Block file (b)
- Character device file (c)
- Named pipe file or just a pipe file (p)
- Symbolic link file (l)
- Socket file (s)
Also apparently there is a thing called a Door File on Solaris, but, alas, we’re not caring about that.
I’m reading this and I liked this:
The obvious skill I learned was how to write tests using a fancy testing framework, but the meta-thing I learned which has been even more useful is the fact that writing a test-case generator and a checker is often much more productive than the manual test-case writing that passes for automated testing in most places.
It’s not that these books aren’t useful, it’s that almost all of them are written to make sense without any particular background beyond what any random programmer might have, and you can only get so much out of reading your 50th book targeted at random programmers.
I think stories are so important, but here is a contrary idea: Be suspicious of stories | Tyler Cowen | TEDxMidAtlantic.
This one turned up in my feed today: There’s More to Design Than Data and Rationality. I feel like the author is discovering postmodernism. It made me realise that when people discover things they have the feeling like they’re the first (but they’re probably not).