What devs are really doing in Silicon Valley: debugging yet another "undefined is not an function"
What devs are really doing in Silicon Valley: debugging yet another "undefined is not an function"
Funny, the article doesn't mention any of those topics at all (except for AI - but only as a way of introducing John McCarthy). Meanwhile we do do things like "finding all occurrences of a given word or pattern of letters in a text" quite frequently. And we are utterly dependent on technologies (e.g. databases, networks) based very strongly on the bread-and-butter content of Knuth's books.
I agree, though that for most of us, chasing down "undefined is not a function" and its variants tends to rule the day.
Hey, you're lucky. I'm not in silicon valley, so I spend all my time debugging "I had a problem with the app but it hasn't happened in about a week and I can't remember exactly what the problem was, I need you to fix it or I'm going to escalate to your manager"
I tell people this all the time when they ask what I do. I've met quite a few master plumbers, and they are extremely intelligent technical geniuses for the most part. I'm completely convinced that I would have been one of them (or some other trade craft) if I were born 50 years ago.
- Developers: Hazmat engineers
- CS: Civil engineers
Developers: Garbage truck service/maintenance department
Devops: Mechanic's apprentice who sometimes has to fill in for garbage truck drivers who no-show.
Contractor: Mobile service tech gets called in to weld up stuff when it's broken beyond what the in-house team can handle.
CS: Guys who plan the garbage trucks' route.
Not everything is "engineering".
Edit: You people take yourselves too seriously.
- Dev: Implementation
- CS: Design
edit: Yes, whether you feel "Civil engineering" is worse than "Hazmat engineering" is a subjective matter.