> Does the interesting 1970s “programmer” job still exist?
Sure! Go right there: https://www.linkedin.com/jobs/cobol-jobs/
And enjoy the not-bloated-at-all systems you'll find there!
111–120 of 246 posts
> Does the interesting 1970s “programmer” job still exist?
Sure! Go right there: https://www.linkedin.com/jobs/cobol-jobs/
And enjoy the not-bloated-at-all systems you'll find there!
Earlier quoted context omitted.
The fact that R has such buy-in despite being a rather awful programming language (a friend of mine worked on the next Lisp-like version of R under Ross Ihaka, and the next version is based on the fact that current R is a bit awful) is precisely because it offers such convenience to non-programmers. In my sister company, they have data scientists, and data engineers. The data scientists write their algorithms in the…
Can you elaborate more on the "algorithms in JS" bit? What libraries/tools are they using? Why JS versus Python or JVM languages?
Earlier quoted context omitted.
Seconded. "Data scientists" and "being most comfortable writing in JS" just sounds strange to me.
I don't want to pile on but that sentence strongly reminded me of the oldish saw about "a data scientist is a programmer who lives in SF". I've never heard of anyone using JS for data science. What might it have that's anywhere comparable to the tidyverse or numpy/scipy/sklearn?
Again, I don't know why, it struck me as odd also, but hey, whatever they're doing, it works for them.
Something about this article strikes me as a thinly-veiled complaint about poorly designed object-oriented systems. Take, for example this comment by the author: >Even if the money were half of what today’s coder gets paid it might still be a better job because one is spared the tedium of looking at millions of lines of Java that do almost nothing! What all those millions of lines of code are is abstractions, decoupl…
nit: is it "about poorly-designed, object-oriented systems"?
This post states that a data scientist uses compact languages such as SQL and R. Genuine question - do people really believe that being able to write and understand complex SQL makes you a data scientist? I ask because, I've been writing some of the nastiest, most difficult looking SQL around for probably at least 15 years. And yet, I would NOT call myself a data scientist because I know and can work with data and us…
Something about this article strikes me as a thinly-veiled complaint about poorly designed object-oriented systems. Take, for example this comment by the author: >Even if the money were half of what today’s coder gets paid it might still be a better job because one is spared the tedium of looking at millions of lines of Java that do almost nothing! What all those millions of lines of code are is abstractions, decoupl…
There was a sign on the door to the Vax Lab at the University of Maryland that said "Department of Research Simulation".
Haha, it seems that quite a few scientists in academia are simulating the act of performing research ;)
https://medium.com/@donhopkins/designing-user-interfaces-to-...
Edit: misspelling.
only if "software engineer" is the new "system administrator"
This doesn't make any sense. My job title is "software engineer" I never do any system administration. I produce code in python, javascript, C and SQL; never do any sort of administration. Sure, I occasionally deal with linux since our servers are linux and so some knowledge of it is useful, and I use unix tools pretty extensively (in OSX) since I prefer to write code this way. All the "software engineer"s I know hav…