3 ms·
From personal experience developing at all levels of the stack, I think my job breaks down into something like * 40% UI (visualising states, handling user in
by algesten 10y ago
From personal experience developing at all levels of the stack, I think my job breaks down into something like
* 40% UI (visualising states, handling user input, feedback, etc),
* 55% moving data around (read an XML file, translate it, push it into db over there)
* 5% algorithmic work (given input of x million records, figure y out)
The UI stuff I already did in Javascript, however it turns out that one single threaded process can shuffle a lot of data around (resource efficiently), if I adopt an async programming style. I know NodeJS is not the only language that does async stuff nicely, but it's rather convenient to have the same language everywhere (though I recognise Javascript is not the most elegant).