Earlier quoted context omitted.
It definitively is true of local universities. I've met people from the local university who have a master in machine learning, yet have never heard of docker.
This is a good thing. Opportunity costs are incredibly important with university educations because students have a limited time to learn. Why spend the time futzing with a tool like docker? It's not foundational to machine learning, so learning that tool takes away from time that could be spent learning something more relevant. And the student may or may not use it when they get a job.
My dad's resume and skills from 1980
591–600 of 611 posts
Re: My dad's resume and skills from 1980
#592Earlier quoted context omitted.
> there is nothing on the horizon which will plausibly replace it I'm not going to be making any bets - but the one project that has possibility is WASM. A mature, polyglot ecosystem on top of WASM runtimes with web-apis seem like it could displace JS in browser as #1.
Probably not. Unless you're rendering to another target besides the DOM (ie canvas) I doubt you see JS displacement as #1 in the browser. JS is not the performance bottleneck, the DOM itself is. And in the meantime, you've got 25 years of example code, component libraries, talent development, dev productivity tooling, browser integration, etc built up around it. And unlike other operating systems, the browser does no…
Re: My dad's resume and skills from 1980
#593Earlier quoted context omitted.
> there is nothing on the horizon which will plausibly replace it I'm not going to be making any bets - but the one project that has possibility is WASM. A mature, polyglot ecosystem on top of WASM runtimes with web-apis seem like it could displace JS in browser as #1.
Probably not. Unless you're rendering to another target besides the DOM (ie canvas) I doubt you see JS displacement as #1 in the browser. JS is not the performance bottleneck, the DOM itself is. And in the meantime, you've got 25 years of example code, component libraries, talent development, dev productivity tooling, browser integration, etc built up around it. And unlike other operating systems, the browser does no…
if we're talking on the level of 20,30,50 years, we may in fact be able to move away from a DOM-based web. and WASM is simply a binary spec, so it can adjut with whatever comes on the horizon. We've had similar sized giants rise and fall in that span.
Re: My dad's resume and skills from 1980
#594Earlier quoted context omitted.
It definitively is true of local universities. I've met people from the local university who have a master in machine learning, yet have never heard of docker.
This is a good thing. Opportunity costs are incredibly important with university educations because students have a limited time to learn. Why spend the time futzing with a tool like docker? It's not foundational to machine learning, so learning that tool takes away from time that could be spent learning something more relevant. And the student may or may not use it when they get a job.
And if you want to try two different deep learning frameworks, dependent on different versions of cuda, and want them to not break each other, God help you if you try that without containers.
It's not that they don't have a "course in docker". I understand that. It's that they haven't even heard of it, so they don't even know where to start to look for solutions to problems like that. I have been through that pain myself.
Containers is just one of so many easy things, that make your job so much easier, I've learned the painful way in 20 years as a developer in (mostly) non-elite companies, where no one else knew it either because they hadn't been taught at the local universities, because no one there knew it either.
Re: My dad's resume and skills from 1980
#595Re: My dad's resume and skills from 1980
#596That job market seems like so long ago. See job ad, type out a letter with your CV, wait for them to write back, somehow organize a time to meet, more rounds, and so forth. At least it must have been hard to spam out CVs. The guy seems pretty hardcore from my perspective. University training for all those techs. Of course hardware back then cost a lot of money so you wanted people who knew what they were doing. What…
My copy of K&R belonged to my dad and was from the early 80s! My job interviews in the 80s and 90s (college summer jobs, or the one time a company tried to get me to leave college for a job) had no whiteboard-coding-style technical skills components, aside from demos of software I'd written and general discussions of implementation details. One job I interviewed for was at Davinci Email. This was probably 1990-ish? T…
I had something similar happen in 92. The interview consisted of leaving me alone looking at one screen of Apple BASIC that came from their actual production code. The screen was nearly full of characters. I was supposed to tell them what that bit of code did.
I spent about 5 minutes looking at it, and though I think I could give the correct answer, I also realized I didn't want to work with this code base. I then thanked the interviewer and left.
The headhunter that sent me on this interview was quite irate that I had "embarrassed" them. C'est la vie.
Re: My dad's resume and skills from 1980
#597Earlier quoted context omitted.
In 2015 or 2016 o was taking the computer architectures class at my local university… the processor they based the whole course upon was the motorola 68000.
And why wouldn't they base it on that CPU? If you're trying to learn the basics of shipbuilding, you don't start by going on a deep dive into the construction of an aircraft carrier. It's a simple chip, with a simple instruction set, that can actually be taught to you in the time allotted over a three-credit class.
Re: My dad's resume and skills from 1980
#598Can we bring back this form of resume, please? Information is clearly organized, easy to read, easy to remember. No need for 5-star skills ratings, dual-colored backgrounds, unreadable fonts, and whatnot...
Re: My dad's resume and skills from 1980
#599Earlier quoted context omitted.
If you really find the agile processes you're using are adding tedium, why don't you do the agile thing and tailor them to your specific context? But I imagine we're probably using the same word to describe very different things.
The current implementation of Agile in most cases is pretty much the opposite of agile as described in the agile manifesto. In my team we have reduced the process to having a simple backlog which we work through. But I have seen other teams where you spend enormous amounts of time on planning but it’s frowned upon if you think any further than the next sprint. Just check off tasks without any thoughts about long term…
Granted, that is most of what I see: poorly implemented agile everywhere, usually half embracing SCRUM. I think that has more to do with the typical command and control nature of upper management though.
Re: My dad's resume and skills from 1980
#600Earlier quoted context omitted.
> Computers are older than you think. I doubt it. If by computer you want to mean any machine capable of mechanically doing some kind of calculation, then of course there are examples going back hundreds of years, or even millenia - the Antikythera device was without doubt a mechanical, astronomical computer, for example. But I wrote "the first commercial computer," and the first stored program, Turing complete compu…
There is a distinction between computer and stored program computers, and you're right that the first commercially available stored program computer appeared in 1951. (Though, interestingly, there was a 1936 patent application on the idea in Germany. And a barely functioning one was actually built in 1941.) But Turing complete computers predated that. In fact Turing's own design for a Turing machine was NOT a stored…
Does that matter? Depends on your point of view. What I meant by "how new it all seemed" then tells the tale here. Baruch could maybe see the future in 1945 because of his experience and vision. But by 1970 or thereabouts, almost anyone who touched it could see it, and millions were increasingly able to touch it, precisely because it was was commercially produced and generally available. Still not ubiquitous, as they are today, computers were nevertheless showing up in every corner of life.
So it's not that I think computers or information as a processing as a concept, or even as an occasional reality, were new around 1970. But computers as a phenomenon that would define the way interact with each other and the world, and computer programming as a skill that anyone could acquire, really were.