@22 Interesting. We teach our students several different languages precisely so that it will be easier for them to pick up new ones later.
@wim_v12e this new job of mine is also the first job working exclusively alongside computer science degree holders. All my previous jobs I worked with programmers from the various engineerings or mathematics or the biological sciences or the arts. I kind of miss the diversity of ancillary skills, and I miss the assumption that anyone can learn to program without getting a degree in it.
@22 By the way, I think of myself as a "comput*ing* scientist", not a "comput*er* scientist". Computers are these essentially cobbled-together, Byzantine machines, always a only hair's breadth away from becoming a brick. Whereas Computing Science is the bright space of mathematics, logic, algorithms and datastructures.
Of course we have to use computers to turn these abstract concepts into concrete artefacts, and it can even be fun (I *love* programming), but it is not the essence.
@wim_v12e finally, a cogent and useful description of the dichotomy between computing science and that-other-thing-that-I-do-that-involves-computers!
I can say with tremendous certainty (having done grad school in electrical engineering) that, while I am glad capable people are researching computing science and appreciate their findings, I am very happy to have *finally* realized that I like living in the engineering world of making those nasty capricious computers delight my paying users.
@22 I wish my reviewers would sometimes use such words 🤣
I am engineer by nature as well as by training, and therefore I can't help but wanting to build working systems.
In my case, systems to do supercomputing on FPGAs. And in terms of peskiness, compare to FPGAs, GPUs are a walk in the park and ordinary CPUs are a dream.