12 ms·
To answer each point in turn; 1. You're a new developer with no professional experience who wants a reasonably well-paid job on your terms rather than an inter
by onion2k 12y ago
To answer each point in turn;
1. You're a new developer with no professional experience who wants a reasonably well-paid job on your terms rather than an internship/junior role. You're going to end up doing the boring stuff. On the specific task you mention - that's either a fairly trivial exercise in regular expressions or a reasonably interesting task refactoring a codebase to use a proper database abstraction. Either way it's not that boring. I can think of much more boring coding things.
2. Don't look for roles at big companies then.
3. Every company has things that look bad from the outside but there's usually a reason for it. Don't judge. You'll be responsible for writing some pretty horrible code during your career. I guarantee it.
4. Some startups have plenty of cash and are absolutely desperate for developers. Look here: http://workinstartups.com/ http://workinstartups.com/ (if not there, there might be a more Netherlands specific version somewhere.)
5. Yes, you can network. Finding events is easy (Google, Meetup.com, etc). There's loads of them everywhere. Also, ask your tutors/professors. They'll be pretty well connected. And go old school - Google for local software companies, find their email addresses/phone numbers, and reach out to them. You will be amazed how happy people are to help you.
EDIT: One more thing.. don't underestimate the value in getting a job that isn't anything to do with coding. For example, working in a restaurant would give you plenty of 'soft skills' experience dealing with people. Being a 'people person' will set you apart from other developers later in your career. It's worth thinking about.
- wofo 12y agoGreat answer! Thanks! It gives me a lot of stuff to think about.
- trcollinson 12y agoThat was a fantastic answer. Just to add a bit to onion2k's excellent response: 1) You have a lot to learn about refactoring and working in codebases that aren't great. I have never once been upset with a junior developer who went above and beyond a task to try to make something better, especially those who ask questions along the way. Don't do the tasks they are for. Do accomplish the same result they are hoping for in a better way! And learn from it. (Refactoring, better tests, better OO or functional principles). 2) I have worked in very very large companies which have part time intern spots that pay much better than restaurants and grocery stores. 3), 4), 5) here here! Well said. On the Edit note: I want to point out that three of my very best software engineer colleagues started their careers in construction. One moved rocks at a quarry, one was a roofing and framing assistant, one did concrete contracting. All have a work ethic unlike any I have seen in a life long engineer. Not only are they brilliant coders, they have immense problem solving skills, fantastic people skills, and they don't complain nearly as much as everyone else.