The problem with that is that it requires you to know the people you want to communicate with.
Say I know a family member is at an event and I hear a tornado hits it, there's an earthquake, fire, terrorist attack or other massive event. I may not be able to get through to the people I do know there and I probably won't know the people that are trying to get information out.
A while ago I tried to be in a larger facebook group and having more than one window open would grind my machine to a halt. Every single tab wanted it own Ajaxy Chat GUI.
Slack should have just made a pretty GUI on top of the existing IRC protocol. I remember being able to be in dozens of chat rooms on a machine less powerful than a RaspberryPi.
What I want and what other people want are different things. There are people that would be happier being an electrician or electrical tech but get driven into EE for multiple reasons.
With the amount of work we have I would be better off with a dozen high school students that were interested in mechanical stuff and had taken a Python crash course. We tried the India route years ago, it didn't work. I don't need a full blown Engineer or CS major. I don't even want an Engineering or CS Intern. I want someone that can read documentation and has taken Algebra II. That's it.
And there are a lot of people that would fit that. Some may cap out as 'programmers', others may go on to be engineers or CS majors. But it's the "VocTech" that has been lacking in the US. It's what every other profession and industry has done.
Engineers didn't go away when Engineering Techs appeared. CS majors aren't going to go away when "CS Techs" are trained.
You don't need your electrician to understand field theory and RF. You don't need your plumber to know Reynolds number. The "shortage" that we have in industry is too many CS majors and not enough coders.
Are you saying that there is no problem solving involved in skilled trades?
HVAC, plumber, electrician, pipefitter, steamfitter, etc all have their own sets of issues and problem solving involved.
Now a VocTech trained coder may have a limited set of problem solving skills. I wouldn't expect a VocTech Python programmer to be able to solve a VocTech Node programmer's problems anymore than I would expect a plumber to be able to solve an electrician's problems.
at the checkout counter
Since when is a cashier a vocational tech / skilled trade position? Or garbage picker or assembly line worker?
How should I break it to all of my peers that they're too old to do their job? Especially the new ones that just got hired?
If you have the right skillsets you will never be unemployed.
However I feel like if half of the older slashdotters got into an interview they'd spend the entire time telling the interviewer why their technology stack was wrong.
hire experienced people who get the actual job done with less lip and grand design dreams.
Because Slashdotters who hear about schools designed to train people with experience they lose their minds that 'coding' is now a VocTech level position. You can train someone in a specific skillset in a fraction of the time it takes to give them a full theoretical education.
There is a difference between accedemic theory and real life.
And that is where a trade comes it. Trades focus on the 'real life'. You don't hire an Electrical Engineer when you need an Electrician, why would you hire a CS major when you needed a 'programmer'.
I'm not seeing the problem. Google didn't hire him to turn on PCs. There's a reason they hired someone (you) at a much cheaper rate to handle low level stuff like that. So that the PhDs they hired in a specific area could focus on doing PhD level work in their area.
We always joked that the PhD'd engineers were easy to spot, they were the ones with velcro shoes. Being extremely intelligent and knowledgeable in a very narrow window doesn't make you intelligent or knowledgeable in all other ones.
An MD could tell you the theory and practice behind putting in an IV but a Nurse is going to be the one better at doing it. Long ago the medical community figured out that wasting someone with 12+ years of post HS education to put in something that someone with much less education could do was extremely expensive.
Our Mechanical/Electrical/Aerospace engineers don't do their own IT. If something stops working it's IT's job to fix it.
A CS degree makes you a coder as much as a Mechanical Engineering degree makes you a Mechanic or HVAC installer and as much as an EE degree makes you an electrician.
The majority of CS majors I know can't even tell you how a processor works on basic principles.
Why should they? That's a CompE major's domain.
The world undergone a mitosis since CS was first founded. I wouldn't expect a CS major with a PhD in one domain to have PhD level knowledge in another CS domain.
Current task from the boss: Classify these engineering plots using neural networks.
I bought myself a head start with TensorFlow. How portable is your code going to be?
Coding and programming is a means to an end for most professions. The farmer that fixes his tractor isn't a mechanic. Doesn't make his money being a mechanic and just knows how to fix tractors because it is a tool they use to get what they're really after.
No doubt Woz could code circles around me for what he was coding for. That's not why I or any of my peers write code. It's a tool to get a job done and move on to the next job.
Ding ding ding. You get it. We don't have a bullpen of programmers to throw at every problem and develop a program in C. We have Mechanical, Electrical, Industrial, Aerospace engineers that know engineering and maybe VBA, probably Matlab and now more often than not Python.
We have Marketing, HR, and PR majors that are given a task that they're doing over and over again and knocking out a script to automate some TPS reports that used to take them a day to generate. Aggregating data from some excel spreadsheet to another excel spreadsheet.
Python is to the point where the non-programmers can benefit from code.
Slashdot Mirror
That's upper middle class. You're still one health injury or job loss away from not being in that bracket.
"Rich" is when you don't have to worry about any of that.
So think of Rust as a highlevel portable C abstraction.
Why use compiled language of the month when assembly has been around for decades, is well understood and does exactly what you want?
How long before I start replacing C with C++? 6 months? A year?
Last time I went to Vegas ~2 years ago my hotel had the most secure network of all.
One on one could get on. When you could get on it was near dialup speeds. I have no idea how they host tech conferences.
What is this, where am I, what year is it.
/me understands this reference.
The problem with that is that it requires you to know the people you want to communicate with.
Say I know a family member is at an event and I hear a tornado hits it, there's an earthquake, fire, terrorist attack or other massive event. I may not be able to get through to the people I do know there and I probably won't know the people that are trying to get information out.
A while ago I tried to be in a larger facebook group and having more than one window open would grind my machine to a halt. Every single tab wanted it own Ajaxy Chat GUI.
Slack should have just made a pretty GUI on top of the existing IRC protocol. I remember being able to be in dozens of chat rooms on a machine less powerful than a RaspberryPi.
Election season is over. US, UK and France have all held their elections. Maybe there isn't anything for the bots to retweet and talk about any more.
For 99.9% of it is just noise. However in an emergency situation it's an easy way to disperse information.
Shit /r/RedPill and /r/MGTOW are leaking.
https://unlimitedville.com/
What I want and what other people want are different things. There are people that would be happier being an electrician or electrical tech but get driven into EE for multiple reasons.
With the amount of work we have I would be better off with a dozen high school students that were interested in mechanical stuff and had taken a Python crash course. We tried the India route years ago, it didn't work. I don't need a full blown Engineer or CS major. I don't even want an Engineering or CS Intern. I want someone that can read documentation and has taken Algebra II. That's it.
And there are a lot of people that would fit that. Some may cap out as 'programmers', others may go on to be engineers or CS majors. But it's the "VocTech" that has been lacking in the US. It's what every other profession and industry has done.
Engineers didn't go away when Engineering Techs appeared. CS majors aren't going to go away when "CS Techs" are trained.
Theoretical pays off if you need theory.
You don't need your electrician to understand field theory and RF. You don't need your plumber to know Reynolds number. The "shortage" that we have in industry is too many CS majors and not enough coders.
You cant just teach people how to problem solve.
Are you saying that there is no problem solving involved in skilled trades?
HVAC, plumber, electrician, pipefitter, steamfitter, etc all have their own sets of issues and problem solving involved.
Now a VocTech trained coder may have a limited set of problem solving skills. I wouldn't expect a VocTech Python programmer to be able to solve a VocTech Node programmer's problems anymore than I would expect a plumber to be able to solve an electrician's problems.
at the checkout counter
Since when is a cashier a vocational tech / skilled trade position? Or garbage picker or assembly line worker?
How should I break it to all of my peers that they're too old to do their job? Especially the new ones that just got hired?
If you have the right skillsets you will never be unemployed.
However I feel like if half of the older slashdotters got into an interview they'd spend the entire time telling the interviewer why their technology stack was wrong.
"Simulink Embedded Coder? Simulink Sucks. It's closed source. You should be hand writing all of that in C".
"CAN? CAN is a terrible insecure protocol. What you need is a good ole fashioned RS485 network for your vehicle bus"
"dSpace? That is terribly over priced. You should just knock out something similar with a RaspberryPi and Arduino!"
hire experienced people who get the actual job done with less lip and grand design dreams.
Because Slashdotters who hear about schools designed to train people with experience they lose their minds that 'coding' is now a VocTech level position. You can train someone in a specific skillset in a fraction of the time it takes to give them a full theoretical education.
There is a difference between accedemic theory and real life.
And that is where a trade comes it. Trades focus on the 'real life'. You don't hire an Electrical Engineer when you need an Electrician, why would you hire a CS major when you needed a 'programmer'.
Comic-Con or any other fan fest
Or professional sporting event, theater, concert, etc.
I'm not seeing the problem. Google didn't hire him to turn on PCs. There's a reason they hired someone (you) at a much cheaper rate to handle low level stuff like that. So that the PhDs they hired in a specific area could focus on doing PhD level work in their area.
We always joked that the PhD'd engineers were easy to spot, they were the ones with velcro shoes. Being extremely intelligent and knowledgeable in a very narrow window doesn't make you intelligent or knowledgeable in all other ones.
An MD could tell you the theory and practice behind putting in an IV but a Nurse is going to be the one better at doing it. Long ago the medical community figured out that wasting someone with 12+ years of post HS education to put in something that someone with much less education could do was extremely expensive.
Our Mechanical/Electrical/Aerospace engineers don't do their own IT. If something stops working it's IT's job to fix it.
A CS degree makes you a coder as much as a Mechanical Engineering degree makes you a Mechanic or HVAC installer and as much as an EE degree makes you an electrician.
The majority of CS majors I know can't even tell you how a processor works on basic principles.
Why should they? That's a CompE major's domain.
The world undergone a mitosis since CS was first founded. I wouldn't expect a CS major with a PhD in one domain to have PhD level knowledge in another CS domain.
(alleged) problem.
https://www.google.co.uk/searc...
Current task from the boss: Classify these engineering plots using neural networks.
I bought myself a head start with TensorFlow. How portable is your code going to be?
Coding and programming is a means to an end for most professions. The farmer that fixes his tractor isn't a mechanic. Doesn't make his money being a mechanic and just knows how to fix tractors because it is a tool they use to get what they're really after.
No doubt Woz could code circles around me for what he was coding for. That's not why I or any of my peers write code. It's a tool to get a job done and move on to the next job.
What hardware support does it have?
I have yet to see a job opening for model based design using scilab/xcos embedded design.
Most offices don't have a bullpen of programmers.
Ding ding ding. You get it. We don't have a bullpen of programmers to throw at every problem and develop a program in C. We have Mechanical, Electrical, Industrial, Aerospace engineers that know engineering and maybe VBA, probably Matlab and now more often than not Python.
We have Marketing, HR, and PR majors that are given a task that they're doing over and over again and knocking out a script to automate some TPS reports that used to take them a day to generate. Aggregating data from some excel spreadsheet to another excel spreadsheet.
Python is to the point where the non-programmers can benefit from code.