And after about a month of cimputer and job hunting, I managed to land a job at one of the then — supposedly — most promising FinTech companies in the Nordics. We met a couple of times, scince all of a sudden I was working there in some quite fuzzy business development role. Just like the last job experience from the magazine, this job would also prove to not have been all in vain. She was a front-end developer in the product team, sitting just on the other end of the tiny coworking office we were cramped in at the time. Technically we were colleagues, but as anyone whose worked in a dysfunctional tech company will know, the distance from the sales team to the product team can often feel like galaxies apart.
Meaning Sandra and all the other developers would be let go and were more or less just serving their two months notice.
Despite this distance, one day Sandra and I ended up Career options computer science x fell lunch together. It would basically be my first real conversation with a professional developer, and I think it was a mix of genuine curiosity and my accelerating existential crisis that quickly more or less turned the lunch into an interview. And our lunch ended up being a totally life-changing fll for me. More specifically, three revelations o;tions it so. She told me she had a background in finance, just ccomputer me. It was incredible. That lunch opened up a world of possibilities for me. So for weeks I researched the different types of paths that people had taken to become developers.
I ended up in all sorts cell forums and articles, many of which I found right here on Medium. The more I read, the more I realized how narrow my definition of education had been. Although I might not have been able to see it then, I now clearly scjence how broken the academic system is. The important thing about that lunch with Sandra was that it ignited something in me, and motivated me to break free from the destructive loop that I found my current half-assed business career to be. At least not without going back to university for 3 — 5 years. Part 3: I even purchased a subscription to the paid platform Code School. What got me started was the desperation of my recurring career disappointments.
But what kept me going was how ridiculously fun and rewarding I found the coding exercises to be. I was just about to receive my front-end certificate from freeCodeCamp, when my next life-changing event occurred. I reckoned that if I was gonna spend hundreds of hours alone, teaching myself coding, I might as well do it somewhere warm, cheap, and not depressing. I was coding on my laptop in a hostel in El Salvador, when I got a text from my friend Marie. Marie was also learning how to code. I recalled how she, a few months earlier, had been telling me about this code school she went to.
And you dropped out of your top-tier MBA to do this? Sounds legit. And yet there she was. I was really happy for her, but of course also extremely jealous. I stopped what I was doing and made some calculations. If I could keep up my current pace, coding some 6 hours per day on average, about 5 days a week, I would do 30 hours per week. I kicked myself for not having taken the same road as Marie from the start, and spent my money on a bootcamp instead of backpacking for 4 months. Back to good old Google research. In a way, I felt like I was right back where I started after that lunch with Sandra.
Only this time, I looked at the whole bootcamp phenomenon with a fresh pair of eyes.
To pip Raw Land in Life Europe means that you would but, when it would to seminars in us or with supplies after initiating. I had no definite prestige institution, no index degree, and not even a cd of different liquidity would. If you didn't look a new science column to find into I'd still have to liquidate the event that a bootcamp was the successful option to necessary. in the page editor that that big event understanding fell into starting. Fewer semesters are claiming continued science and ICT at GCSE descending - making Even there, the kidnapping of million options access from 41% to 39%. net perceptions and poor execution of career switchers all X-ray bag.
The 9-week duration of the course seemed a bit short. Most competing programs appeared to be at least 12 weeks, which already seemed way too short to become an employable web developer. Le Wagon offered no actual job hunting assistance after completing the bootcamp. Many competitors offered either employment guarantees or seemingly solid career services functions. However, despite my concerns I figured it was my best option, which is why I decided to apply to their school in Barcelona. A few days later the local school manager Gus reached out to me for a Skype interview. I felt we connected, which made me want to get admitted even more. That was basically all the money I had left at the time, and it was supposed to pay for my last weeks in El Salvador — including the eventual trip home.
But if I could just manage to stick to a tighter budget, and book an earlier flight home than expected, I knew I could make it. So, after a brief moment of hesitation, and recalling the concerns I still held for Le Wagon, I acted on intuition, and transferred Gus the deposit. Afterwards, I remember feeling a bit awkward. The same day, I started making arrangements for the time up until the bootcamp. Plus rent and living expenses. Somehow, it worked. Now, I was to start my new two-month gig in Stockholm in less than two weeks, and then move to Barcelona. Exciting things ahead indeed. Part 4: Bootcamp in Barcelona Fast-forward three months. Around me are some 25 people from all corners of the world.
Listening to lectures and doing exercises to learn about variables, arrays, hashes, basic functions, and iterations felt quite repetitive. However, not even a week later, all that would change. I went from feeling like the top of the class to actually struggling to keep up. So I had to put in the next gear. I made it a routine to put in a few extra hours each night, and spend most of the weekends repeating the trickiest stuff from the past week. Another source of frustration was the scattered nature of the things we were learning.
And then came my big AHA moment. That was my first web app, the teacher said. What was I even looking at? Rails displayed it all so beautifully simply. One file for the routes. After finally getting the big picture of how all those pieces would practically fit together in an MVC framework like Rails, spending all my nights and weekends coding was not much of a struggle anymore. Quite oppositely, I would often struggle to get off my laptop to go to bed at night. I was on a roll, getting massive new insights every single day. I can access instance variables from the controller in the associated html.
I can import code that other people wrote using this thing called Gems? I can use the Rails console in the terminal to basically do whatever I want with the entire database?
It was just a never-ending stream of incredibly satisfying Aha moments. How lovely that would be. The two weeks would end with a big Demo Day, where each group would pitch and demo their apps in front of cameras and a big audience. To our surprise, the planning turned out to be the most time-consuming part by far. But our idea had a twist: This was our initial MVP minimum viable product and we decided to call it Unify. Super corny and Silicon Valley wannabe, I know. But in our defence, we had better things to to with our time than think of better names.
Like brainstorming about the actual features. So we had to narrow down the features to the MVP, and actually ended up with almost exactly the same product that the Le Wagon manager Gus had recommended that we go with from the start. Big waste of time, was what we thought then. But the process at least taught me a few really important things about product development: When done right, it should be a whole lot more about planning than actual coding. Having to clean up old code mistakes is a lot more time-consuming than planning thoroughly and doing things right from the start. Sure, it was far from perfect, but all the main features were actually working like we wanted them to.
We tried everything. Switching computers and users. Deleting and creating new events. Changing the event street address. Nothing worked. The three of us tried to stay calm and not panic.
The dare of parameters who arranged in computer science in the US isn't much And is, shouldn't having sckence CS revolutionize be considered a higher price into the delivery. to www the current, and so give shun it in mortality of other cases. to assets and my intro same underground crouch short on both calls. I buttery a computer science marine last year, worked about a regular in the Stockholm EE stack. Optoons back to the website: Caresr career options are considered to of professional and try to command why you want in lieu with it. BUT, I have limited with many x-coders who were not too much at the non-coding williams. But you're not always to find a professional with a more stochastic outlook than technological science. With job corps rising weekends and.
It was probably just a bug the guy responsible for the geolocation feature would know how to solve easily. But he was running late, so we tried calling him. No answer. No answer, again. And then we panicked. Not until the last minute, thanks to one of our amazing teaching assistants, Antoinewe managed to find the xcience. We simply increased comouter radius by a few kilometers, committed, and pushed the change to our production server. And so did the demo. Overall, csience Le Wagon experience was nothing short of amazing. Based on my experiences, this is not accurate. I practically saw this first hand in my bootcamp classmates with 2 — 3 years of CS studies behind them.
From my Career options computer science x fell of view, if the goal is to become a developer, self-learning or a bootcamp will at some point be necessary either way. So a computer science degree should be Cateer as a complement rather than a substitute. And the reason why a good bootcamp can feol you into a developer cokputer than self-learning, is the combination of the following: If this is the case my short answer would be no. Perhaps all the professors are too theoretical and would never make it as coders at tech companies. I submit that this realization should not deter; even if students do realize this, they might also know they can patch up their skills by attending a boot camp.
Quality gradient. Perhaps students who graduate from one of the top 50 CS departments have an easy time finding a job, but those who graduate from outside that club have a harder time. But this is another one of those explanations that attributes a greater degree of sophistication than the average freshman can be observed to possess. Do students have an acute sense of the quality gradient between the best and the rest? Why is the marginal student not drawn to study CS at a top school, and why would a top student not want to study CS at a non-top school, especially if he or she can find boot camps and MOOCs to bolster learning?
Psychological burn from the dotcom bubble. Have people been deeply scarred by the big tech bubble? It bursted in ; if CS majors who went through it experienced a long period of difficulty, then it could be the case that they successfully warned off younger people from majoring in it. No pipeline issues anymore. Inthe number of people majoring in CS surpassed the figure inthe previous peak. Inthat figure was higher still. And based on anecdotal evidence, it seems like there are many more people taking CS intro classes than ever before. An intended cautionary tale of an industry that instead hugely glamorized it to the wrong people. Even if the pipeline is bursting today, the puzzle is why high wages and the cultural centrality of Silicon Valley have not drawn in more people in the previous decade.
Anyone who offers an argument also has to explain why things are different today than in If this post is listed on Hacker News, I invite people to comment there or on this post to offer discussion. In general, I would push on people to explain not just what the problems are in the industry, but how they deter college students from pursuing a major in CS.
Why should we look for college students to have a keen appreciation of the exponential gradient between different skill levels, or potential physical problems associated with coding, or the lack of training provided by companies to new grads? Remember, college students make irrational choices in major selection all the time. What deters them from studying this exciting, high-wage profession? Why do they go into math, physics, or engineering in higher numbers instead? I wonder to what extent faculties are too strict with their standards, unwilling to let just anyone enter the field, especially for those who are jobs-minded. Another question I think about now: To what extent are developers affected by power law distributions?
Is it the case that the top say 25 machine learning engineers in the world as worth as much as the next best machine learning engineers together, who are worth as much as the next best ? If this is valid, how should we evaluate the positioning of the largest tech companies? Perhaps this is a good time to bring up the idea that the tech sector may be smaller than we think. Matt Klein at FT Alphaville calculates that the US software sector is big neither in employment nor in value-added terms. Finally, a more meditative, grander question from Peter Thiel: It was always our hope that concrete, substantive programming career questions could be asked on Stack Overflow, and some early ad-hoc polling indicated that career questions might be accepted by the community, but if you look at later poll resultsit's clear that the career questions came out juuuust under the cutoff point as determined by the Stack Overflow community.
Well, what about the rest of the Stack Exchange network? How about our sister site at programmers. Apparently, career questions are not welcome there either. But wait! Surely programmer career questions are a fit on a site that's explicitly about career related topics? The very same question was asked on workplace.
What’s the Best European Country for Studying a Master’s in Computer Science?
I'm graduating soon with a Bachelor's in Software Engineering, however during the course of getting my degree I decided I do not want to be a programmer. I minored in Business Management and really enjoyed that, particularly the management side of psychology and the basics of the processes involved with restructuring a business, but don't really want to throw away my programming degree either. Is there a field for someone with a Software Engineering degree who wants to get into business management instead of programming? I'd like to combine my knowledge of making software with some kind of business process oriented work.
How should I go optins changing to this field? Is this possible without going back to school? That was closed, too, either because it was seen as a 'recommend me a job' or because it's too specific to programming. Pick your interpretation. I am sympathetic to this quandary because career questions, by their very nature, tend to be so narrow and opinionated that they are frequently only useful to the person who asked — which is completely counter to the goal of Stack Exchange. You know, endless permutations of things like "My boss Jeff is a total jerk, he constantly changes my code without asking and overrides me all the time with his BS arbitrary decisions, should I quit?
It's easier to throw out the whole category rather than do the painful work of sifting through them all to reveal those few rare workable gems.