51–54 of 54 posts
Actual LOL. So we have programmers, developers, software engineers, coders and now... Software scientists?? Oh well it will be a good filter on CVs.
I'm a software physicist myself.
Earlier quoted context omitted.
Maybe the author understands programming as "writing lines of code", and not as "architecting software". Architecture requires experience. Writing the fastest quick sort in a given language is an exercise for fresh young brains.
"Writing the fastest quick sort in a given language is an exercise for fresh young brains." I can't see the reasoning here. Surely it's a job for someone who has written previous sorting algorithms, understands the trade-offs between speed and memory, and understand the pitfalls that can be fallen into when sorting different kinds of data?
A fantastic article, and I hope we see more relevant research gathered under this banner. Not having a name for something can be a big problem in even knowing what's out there. As a side-point, I am often shocked that we don't see more research into how to make software teams more productive coming out of places like Google/Facebook/Microsoft etc, given that these companies (claim to) live and die by the effectivenes…
When I worked at an investment bank, the code quality was crap, and the staff turnover was high. Didn't matter, because they literally had enough money to throw at the problem and keep hiring more people.