3 ms·
The problem is you haven't caught up with what computers have become: a utility. They were a novelty when you were growing up, but they are a utility now. What
by cheez 11y ago
The problem is you haven't caught up with what computers have become: a utility.
They were a novelty when you were growing up, but they are a utility now. What that means is that people who deal with computers are going to be professionals ranging from the spectrum of architect to plumber: there are more plumbers than architects.
Do you think your plumber had an innate desire to be a plumber? No. They looked at their options, picked one and executed.
That's what the future looks like for computing. So, if your child was always going to be the type to be an architect, they'll be one. Or they'll be a plumber.
- mstade 11y agoI use the plumber analogy all the time, but most programmers I know vehemently resist this notion. I find nothing wrong with being a plumber, and think many of my colleagues would do well in realizing they aren't high flying architects but actually just well compensated plumbers.
- lsaferite 11y agoBeing a plumber is actually a good career. You can't outsource it, you always need them at some point, and the hourly rate is quite high. Maybe you could automate it? At the point tech can automate all aspects of a plumbers job, we'll have automated most jobs (IMHO).
- cheez 11y agoRight, it's not at all a bad career. But even within plumbers you have a spectrum: "fix my toilet" <-> "winterproof this house"