HN user
Couple of big (agile) projects that I have worked had many "real testers" who weren't really coders (or couldn't really code). To them writing "natural language tests" was more suitable than producing code. The 'lower' level test-libs, that the acceptance tests relied, was either written some of the devs or the 'test-devs' in the test-automation team.
In the bbs-o-spheare there is talk that Nokia is actually supporting Jolla (patents, recruitings).
Couple of old projects (ha sw top on linux) that I've worked the soultion was using C and Python. C for the system stuff and Python for the CLI-part. Which worked quite nicely on that division. My personal taste would have been to use Python a bit more, but the division was 'set to stone' at the start of the project and some managers were inclined to change it.
One question comes to mind after reading this, as did with the Valve handbook, how do you tackle when it is time to "shovel shit"? Meaning that doing things that are, quite frankly, boring.
Same here. Now a days I just go to http://www.aggreddit.com for all my serious reddit needs..
programming
gamedev
linux
asm
C_Programming
cpp
cpudesign
embedded
gpgpu
hpc
coding
python
csbooks
compsci