4 ms·
I changed careers via a coding boot camp. I have highly mixed feelings about how coding boot camps are sold, and run, but I think for some people such short t
by duxup 8y ago
I changed careers via a coding boot camp. I have highly mixed feelings about how coding boot camps are sold, and run, but I think for some people such short term training could be a sort of new future for trade schools.
This could be particularly useful if we're entering an age of sudden disruption as far as jobs and career paths goes where a career that once was might be gone (or greatly diminished) tomorrow. Provided business are willing to recognize and hire those people.
- exelius 8y agoThe change I see happening now is that many of the jobs people are hoping to “skill up” to are themselves being automated out of existence. A combination of targeted AI and good old-fashioned process automation are going to put a lot of white collar workers out of work; including software developers at the lower end of the skill curve.
- duxup 8y agoVery possible. People go where they think the right path is / they might like. I'm not sure anyone has proven to predict what the right path is yet.
- exelius 8y agoI mean, if I could tell you that I would use it to predict the stock market so I wouldn’t need a job. Of course, the fact that the smartest people in the world do exactly that is in itself part of the problem...
- walshemj 8y agoThey where saying that in the 1970's how do you automate even basic front end development of a web site today ?
- opportune 8y agoMake a tool that automatically converts a designer's spec/mockup into a performant webpage with high fidelity? Sounds very hard but certainly possible To be fair there are already a lot of services that do this. They are just so commonplace we don't think of them as automation. And they don't allow super complicated setups so they're definitely not quite there yet in the general case. I'm thinking of Wix, Squarespace, basic wordpress.
- asark 8y agoJust like the old gypsy woman said, today a huge percentage of white-collar office work could literally be replaced with a shell script or a couple days' work by someone who knows their way around excel. But it still hasn't happened and attempts to add more software to these jobs seem usually to do very little to improve efficiency, often just adding more jobs to support the software. Every time more software's added, actual automation gets harder, too, as more systems become involved. Pretty soon a couple macros and a script won't cut it, because there are so many pieces involved they'd certainly break all the time. I'm not even sure most office technology's helping that much. I suspect most of the efficiency gains from tech have been in a handful of "knowledge" work areas, and manufacturing. Plus new markets. The rest... might actually be losing everyone money.
- zitterbewegung 8y agoHave you heard of robotic process automation ? It looks promising to replace office people’s jobs .
- FiddlyPack 8y agoThis is actually kinda what the person you’re replying to is talking about. You have a piece of software that replaces some knowledge workers’ task. At first it seems like you are saving money, but the specifics of the task require an adaptable workforce over the course of years, and the RPA requires an adaptable collection of workers to learn from. Now, instead of just having a job that processes those inputs and outputs, you have the same thing but made more baroque by being connected to RPA, plus software developers to maintain the RPA software itself. Short term, it seems to eliminate workers. Shortly after those workers are eliminated, truth on the ground has changed, and now there’s an ADDITIONAL cost to updating the software, which is harder and more expensive to do without the workers that have been eliminated.
- exelius 8y agoRPA does eliminate workers. Modern RPA isn’t just “write a screen scraper and never think about it again” — you use BAs and line workers to (cheaply) build out a bunch of RPA integrations, see which ones are the most popular / valuable through usage data from your RPA platform, then implement those via less brittle methods as part of your existing roadmaps. The important part is that the front-end that users access stays the same — you’re basically just swapping an API call to an RPA platform with a direct API call to a backing webservice. This allows for rapid development of functional integrations delivering real business capabilities — without the overhead of an SDLC. It helps wrangle shadow IT tools into a manageable system and generates lots of structural data on how the actual users of the system interact with it to guide investment in feature development. The RPA scripts with little / no value will naturally fall into disrepair, while the valuable ones will be maintained / improved. I promise you, it’s way cheaper this way. Software teams stop getting inundated with one-off feature requests that take a ton of work to coordinate, scope, evaluate and test — even if they never get built. Business users get to eliminate time-consuming manual processes. Also keep in mind the first jobs to get replaced by RPA are the ones that have already been shipped offshore... An RPA team for a large enterprise is usually only 2 or 3 engineers and an army of BAs and PMs — but they’re replacing a bunch of individual projects that no longer need to be staffed.
- flukus 8y agoA tonne of mostly front end work is now done in tools like wix and even on the higher end wordpress has taken over a lot of it. The only custom front-end web design work tends to be clients with deeper pockets but local web design shops for small business are largely a thing of the past along with the hosting etc. Aside from the job losses we've lost a gateway into our industry for graduates.
- DoubleCribble 8y agoIndeed. The minimum skill required to find long-term employment becomes a much higher standard. Entry-level office jobs are going to vanish before most people realize. Many low level processes that are currently done by clerks/bookkeepers/analysts will be replaced by scripts.
- notfromhere 8y agoI feel like people pushing this sales pitch have never actually tried to implement these "AI" and "automated" systems.
- krisrm 8y agoIf you don't mind elaborating, what was your experience like with coding boot camp? I entered the profession "traditionally" (via a comp sci degree) so I don't know much about the boot camp experience.
- duxup 8y agoMy program was "full time" (5 days a week) for 12 weeks. The camp was through my local university, but really they had bought a snap in program from an outside company. The course was basically front end to back end via, HTML - CSS - JavaScript - Node - React (in that order). There were other items covered but those were the big focus. Little to no CS, CS theory, algorithms or anything like that. IMO it does a good job getting you started in a specific area and a place to keep learning / jump off from. My instructor was great, his assistants were horrendous (couldn't help with anything, seemed disinterested, straight up were terrible at debugging). If someone puts in the extra time (and they make it clear that you HAVE to put in extra time outside of class) a capable person can come out of the camp as IMO, a useful entry level web developer with potential and a good place to learn from. I have kids so my life for that time was basically, class - take care of family - code - sleep ... repeat. Actually I've kinda kept that up for a year now. I had a technical background (network engineer) for a long time and was working with engineering teams and had done some scripting and reading about coding here and there. Even just a little background can help a lot in a a class that throws things at you quickly. Other folks without a technical background could do well too (one was an accountant, another a director of some sort of organization, some worked odd jobs but were capable folks). The catch in my class was that they do NOT filter candidates in any meaningful way and that ws arguably the worst aspect of the class. There was a test but I think it was more of a sales pitch (it was virtually the same test as several other camps in the area). I'd say at least 50% of the class was unemployable, and the worst of it was they were often on everyone's team for group projects. These people were often a net negative impact, they just couldn't do it couldn't finish their own work, and created more issues than helped. I don't look down on them for it, because how do you know if you ... don't know? I think they were brave for trying. But IMO the class should have done evaluations and invited some folks to save them self some time and move on but of course that might involve a partial refund so ... doesn't happen. That might sound like I'm talking smack about folks in order to talk myself up, but having a class with people who are either not trying (shockingly there were those) and / or not capable really disrupts the flow of the class and the amount of material covered. Everyone struggled at various points in the class, but some from week two and then constantly from there on they were so far behind it was never going to click. There's a lot of "everyone can code" out there, it's BS, everyone can write it, but troubleshooting and coding and getting a good outcome is another matter. Despite the negatives I have good memories of the class, it was a great experience. I didn't have a traditional education and I loved going to class every day and working with everyone. I do wish the class had gone about twice as long and filtered out candidates (as someone said, it's a bootcamp, shouldn't people be booted?). I think the bootcamp system can be useful (let's put aside the robots and AI for a bit) but I do worry the companies involved might be so profit driven that they make it ... less useful for society as a whole. One side note, a few students decided to go back to school for a traditional CS degree and they really appreciated their bootcamp experience on top of getting into CS where they felt the theory can get a bit deep and academic. They feel their fellow students (and some professors) maybe can't see the forest through the trees / what they're actually learning as it would apply to actual programming you might do when you apply that theory. I've worked with some great CS grads since graduating and they're good guys, most know way more than I do, but no amount of CS can make up for deciding that "I have no idea what is going on, I'm going to dive into the code and see where it goes until I figure it out." Quite a few just want to ask someone, and then ask, and then ask, and ... I wish I had a CS degree and if it was an option I would do it in a heartbeat, I think it is a far superior path. But I do think the boot camp system "can" work, for the right people.