Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:Write Code. (Score 1) 540

Write code that interests you, sell it or give it away, and build up a body of work that you can point to.


I'll second that, as well as the suggestions to
- get a SQE-type job, coding unit or API tests and
- look at small companies and apply for those lower-end Programmer jobs anyway.

Those things are what I did and... well, actually, after programming for a good long while I'm now a QA manager who does quite a bit of tool-and-test coding and playing mentor to more "junior" programmers... pays better than my last programming gig, whatever you think of QA work.

Anyway... the truth is, many companies "lie" in their job descriptions, especially in terms of years of experience they'd settle for. Less than 3 years experience on a job advert means they'll consider your QA work, especially if it includes some programming of some kind somewhere.

The problem with too many years of QA work is that, eventually, the hiring manager will wonder if you really can write code of your own, or if you really desire to... they'll wonder why you didn't get a programming gig at some point, and you'll have to convince them that the last program you wrote wasn't for a CS class.

Ultimately, to get that programming gig, you need to have written code on projects that produce something you can talk about or show off. JCR says to write code that interests you; as with all things in life, that's going to be what you enjoy and are more easily successful in, so it's great advice. If you can also write code where you work ( even if it's less interesting to *you* ), that's good to do, if you remember it and count it as programming experience on your resume and in interviews.

The important thing is to gain experience writing code, if you want to convince someone that's what you have experience doing. Write code at work, on your own, or, as many suggest, as part of an open-source project... however you do it... write code... have something to talk about in your interview besides test plans and button clicks.

User Journal

Journal Journal: Reply to bad stories with "mod STORY down" comments. 3

I think I've finally reached the breaking point with regards to stories on slashdot that just plain suck. Stories which are dupes of very recent stories, stories which include ( often intentionally ) just plain wrong, inflamatory, trolling statements, stories that don't pass the "laugh test" for credibility.

Journal Journal: Why meta-moderating is fun...

I've always found an odd pleasure in meta-moderating posts. Today, I realized a big part of why it's actually pretty fun :

These are the posts that other people found interesting, insightful, informative, funny, trollish, offtopic, and otherwise attention-grabbing. Someone bothered to moderate the posts you're looking at. So, right off the bat, it's a selection of the best, worst and most entertaining posts that you're looking at.


Journal Journal: Track stocks of companies that slashdot hates/loves! 1

Lord Dwoemer gets credit for inspiring my first /. journal entry! He wrote :You know, someone should set up a Slashdot fund and make it available to view on a website. Just a fantasy stock market thing that would track the stock prices of all the companies Slashdot loves to hate.

Slashdot Top Deals

Save yourself! Reboot in 5 seconds!