3 ms·
I'm more self-taught than formally educated, although my background includes a mix of the two. So, in a sense, I hired myself at Fogbeam. As for how you might
by mindcrime 12y ago
I'm more self-taught than formally educated, although my background includes a mix of the two. So, in a sense, I hired myself at Fogbeam.
As for how you might go about getting that first job... I think one of the keys is "build stuff". I mean, it's cliche to talk about "Github is your new resume" but there is a lot of truth to the idea that "code talks, bullshit walks". Pick a project of some sort that interests you, and start building it. So much the better if it's something you don't feel totally qualified to build yet.
When you go in to talk to a prospective employer, if they're smart, they'll dig into your project and use that to help get a good feel for what you are capable of. It's OK if it's not perfect, as a smart employer will understand that you're green, and if you show the ability to actually ship something, you will be in good shape.
Beyond that, I'd say one top hint is this: Be ready to defend the decisions you made building your app, with reasons beyond "Because I heard X was cool on Hacker News". If somebody asks "why are you using Angular on the front-end and a REST backend built using Sling" then have some meat to talk about. If somebody asks "how could module FOO be implemented in a functional language?" (assuming it's not currently) be ready to talk about that. Better yet, be proactive... a conversation like this is very valuable:
Interviewer: Why did you X?
You: Well, I thought about X, Y and Z, and each has it's pros and cons. I would have gone with Z if this app were meant to scale to millions of users, but since it was mainly a learning project, I went with Y because $WHATEVER. I kinda ruled out X early on because $SOMETHING.
Letting passion show is good too. If somebody asks "Why did you build a machine learning library?" it's good if you make it clear that you did it because you are genuinely enthusiastic about machine learning and wanted to get some hands-on experience implementing the algorithms, etc., etc. It's not so good if your answer is "Well, it seemed like the kind of thing you could make a lot of money from". Not that wanting to make money is bad, mind you. But a genuine passion for a topic / interest area is much more interesting that strictly financial interest, IMO.
Anyway, build stuff, explore your interests, read and learn as much as you can, build more stuff, and you'll find something.
- notduncansmith 12y ago+1 for building stuff. As a fellow autodidact, I cannot stress enough the importance of proving that you can actually build maintainable software. To put this in perspective: typically, a degree is seen as proof of some basic level of knowledge. XYZ University wouldn't have signed this piece of paper unless you had demonstrated the ability to pick up and apply (at least some of) the programming/CS concepts required to be effective in a professional development environment. As a self-taught developer, until you build something, you lack this proof. Once you ship some code, though, you have concrete evidence that you can point to and say "See? I know what I'm talking about!". By the way, the big secret is that this is actually much more powerful than a degree; take advantage of it! If you can show employers that you can actually write good code, you'll have a huge leg up over the guys and girls that think they can just rest on their shiny CS degree (at most companies worth working at, that is). Hacking on open source projects is great as well, because it demonstrates the ability to work well with others - something I found a lot of concern about during my latest job search.