The creeping IT apocalypse
191–200 of 279 posts
Re: The creeping IT apocalypse
#192Technically minded, astute engineers are great at solving problems. In an ideal world, we'd be using our ability to solve complex real world problems. I'd much rather the Golang engineer equivalent 20 years from now solve critical watersupply issues to a village, than writing API's with flame graphs. Full disclosure: CS engineer by love and training.
Re: The creeping IT apocalypse
#193While I think this essay has some good points, it ignores the problem that I always see with this idea - people. I really wish the business people I deal with on a daily basis could have their business requirements met by such automation, cause it's the least fun part of my job. But the don't because I don't care how awesome your cloud provider tools are, they always come to me with some weird requirement or platform…
I wouldn't even mind if they even had "those requirements". That would be a huge step up. Oftentimes the requirements are not written down and stuck in tribal knowledge. And woe betide you if the tribe is an outsourcer or offshore team. About half the time, they're unintentionally leaving knowledge in the heads of their meat-robots, and getting the information transferred out of those heads is painful and time-consuming, because "set of procedures for meat-robots" is effectively what they're hired for.
If the procedure is periodically performed, I often get pretty good results just asking for copies of the resultant emails reporting completion, and working backwards from there. Automation at this layer of staff work is considered exotic developer-realm, needs-a-budget-and-a-project-manager effort, even for what most HN readers would consider relatively trivial multi-hour or multi-day scripting work.
The abruptness and agony of automation sweeping through these layers in the upcoming years as the tooling to discover, capture, distill, and maintain these requirements with tight synchronization to software teams maintaining the code behind the automation are going to be politically challenging, as a lot of these people have zero notion what they're doing can be automated away, even as they consume the results of ML in their daily lives.
And I'm rather glum about teaching these people how to perform the automatation themselves. The reception I've gotten to my offers to help them get on the track to learning programming and automation have been very underwhelming. Even if someone doesn't "get it" about coding, just the exposure to the thinking patterns would help me enormously cut down on unnecessary meeting times, as there are still way too many people whose conception of automation is closer to "can't they/you just...[magic/mind-read]?"
Re: The creeping IT apocalypse
#194Read my response to this article here: https://medium.com/@robertcorey1/hey-moron-you-better-start-...
Re: The creeping IT apocalypse
#195Earlier quoted context omitted.
You're being rather reductive. Just because someone is in a 'working class job' doest diminish their intellect. I've encountered many working class folks with a lot of knowledge in the fields they were in (electricians, plumbers, mechanics, etc).
Those aren't working class, they're tradesmen. At least IMO. Working class to me means Walmart, Mcdonalds, and Jack Generic Construction LLC.
Working class to most people just means that they do manual labor. They work outside and in factories building and moving physical things be it burgers or buildings or balloon animals. The key seems to be that they don't generally sit at a desk with a computer on it for 8hrs a day.
Re: The creeping IT apocalypse
#196This kind of change has also impacted me. It shows up when I'm trying to give students advice about starting their careers, and I realize that the first jobs I had (system administrator, SOC worker) have been replaced by robots. Especially in the SOC, I was a "Tier 1" analyst that would do monitoring (watching a bank of green lights waiting for one to turn red) and first level triage and analysis. This has been repla…
What you're describing is _training_; and the act of training employees has long since gone out of vogue in western markets.
Re: The creeping IT apocalypse
#197This has been happening since the 1970s. Or earlier. I don’t really think of it as an apocalypse. IT skills have never had a long shelf life. Any time you are a technology expert at your company, in IT, the technology landscape will shift under you. This is the Red Queen Hypothesis in action. People who ran mainframes in the 1980s became trusted experts and then most of the jobs evaporated. Same thing happened to peo…
Another worry is recession and the popping of the tech bubble. Sooner or later the bubble has to popped and that's going to cause a lot of pain throughout the tech industry. Should be interesting to see how the industry rebounds and in what form. Will VR be the new "hot thing" like smartphones were after the 2008 recession.
I don't think so. Mobile phones were already a significant thing before 2008 and the morph to smartphones was already in train (first iPhone was 2007).
VR still has to emerge from a relatively small set of niche use cases. Augmented / Mixed reality is more likely, given the ubiquity of good cameras on smartphones. Arguably AR/MR will let the phone manufacturers keep pushing device upgrades for longer, as the smartphone market saturates.
Re: The creeping IT apocalypse
#198Author here - I'm serious when I say that I'm happy to be a sounding board if you're at a career crossroads. Twitter DMs are open @forrestbrazeal.
Ok, question: What exactly do you mean by this: '“senior application developers” who munge JSON in C#' Why did you choose to JSON and C# in particular here?
Re: The creeping IT apocalypse
#199Earlier quoted context omitted.
In my experience, companies say 3-5 years but this requirement is written by someone in HR translating what the hiring manager said. The hiring manager is more likely to hire someone who has less than 3-5 years of experience, or even hire someone with zero experience, as long as the candidate demonstrates aptitude. The trick is to write your resume so it gets past HR's filter, but without putting bullshit on it. It's…
> The trick is to write your resume so it gets past HR's filter Any tips on how to do that?
The theory here is that programs that automatically scan resumes for keywords will always find the ones they are looking for.
I can’t say I have tried this or know how well it would work in practise.
Re: The creeping IT apocalypse
#200Earlier quoted context omitted.
How many solid universities still have IT programs? At UIUC as of 2016, the IT program was nonexistent.
I have not found one yet. My son currently is enrolled in CS and his first 2 years of school are filled with humanities, history and a few more irrelevant courses all to keep some profs employed. His next two years will be filled with more useless courses and by the time it's all over will have cost 50k + (he lives at home and goes to a State School). I feel like he could have taken a 6 week Java/Python/whatever and…
1. If you want a very specific skillset to do a very specific job, there are more opportunities and options today than ever before. Self-study, MOOC, bootcamps, certs, etc. Pros: fast, efficient, focused, practical, immediate. Cons: the specific/narrow focus may leave you with gaps you won't even be able to appreciate until too late.
2. If you want a more general education, Universities are there to provide. You'll get not just immediate hands-on-keyboard skills, but math and CS-theory background, and also also communication skills, discipline, diligence, social networking, perspective to be a team lead one day, etc.
Now, I do believe universities have a LOT of optimizations to make; a student's life tends to be sucky in many ways it doesn't need to. I've repeatedly found and heard of the difference in attitude between a college/bootcamp of "You're the paying customer, we'll provide knowledge", and university attitude of "you are irrelevant, be grateful, and jump through the hoops jump for the privilege" - whether from the ever-increasing admin/bureaucracy cohort (sometimes helpful, often power-blinded), the obscure rules and difficult processes, or some of the tenured professors. But again, the information is out there, the choices are available - and overall there's never ever been a better and easier time to acquire knowledge.