4 ms·

It's certainly true, in most cases, that noodling around on your own is no substitute for professional experience. But where are the entry-level Haskell jobs t

It's certainly true, in most cases, that noodling around on your own is no substitute for professional experience. But where are the entry-level Haskell jobs that would get someone that experience? Only route in is academia?

wyclif 16y ago
Right. A certain degree of self-learning is necessary in order to reach the point where you are firmly ensconced in that professional engineering enterprise gig. Not to mention the fact that as that enterprise shifts to future, non-faddish frameworks, you are going to have to spend a certain amount of self-motivated time learning on your own to keep your skillset up to date, even if your current gig sends you to conferences and otherwise invests in you.
reeses 16y ago
Having a package or two on Hackage (or even better, in the Haskell Platform) will demonstrate effort and aptitude at learning, and give the opportunity to review your work. If you want to become strong enough to leverage yourself into a Haskell job, stop writing in anything but Haskell for non-production-work tasks. All your shell scripts--Haskell. All your recreational coding--Haskell. Picture yourself in a Shao Lin temple of Haskell. Also, think about the flip side of your question. Haskell is a pain in the ass for the first few months. If you haven't climbed a substantial part of the learning curve by the time you interview, you might discover that you hate it[1]. Part of the interview process is not just seeing if you can do the job, but that you'll stick around for at least a year and not quit because you don't like the environment. I normally wouldn't worry about someone trying to make a transition from Java to C#, but I would worry about someone trying Java -> Haskell without having broken through the "difficult" parts. [1] There's a lot to hate. Imagine, on the flip side, if you had to program in RPG II. You'd want out as soon as you realized you made a mistake. Admittedly, RPG of any flavor doesn't sound sexy, but you get the idea.

wyclif 16y ago

Right. A certain degree of self-learning is necessary in order to reach the point where you are firmly ensconced in that professional engineering enterprise gig. Not to mention the fact that as that enterprise shifts to future, non-faddish frameworks, you are going to have to spend a certain amount of self-motivated time learning on your own to keep your skillset up to date, even if your current gig sends you to conferences and otherwise invests in you.

reeses 16y ago

Having a package or two on Hackage (or even better, in the Haskell Platform) will demonstrate effort and aptitude at learning, and give the opportunity to review your work. If you want to become strong enough to leverage yourself into a Haskell job, stop writing in anything but Haskell for non-production-work tasks. All your shell scripts--Haskell. All your recreational coding--Haskell. Picture yourself in a Shao Lin temple of Haskell. Also, think about the flip side of your question. Haskell is a pain in the ass for the first few months. If you haven't climbed a substantial part of the learning curve by the time you interview, you might discover that you hate it[1]. Part of the interview process is not just seeing if you can do the job, but that you'll stick around for at least a year and not quit because you don't like the environment. I normally wouldn't worry about someone trying to make a transition from Java to C#, but I would worry about someone trying Java -> Haskell without having broken through the "difficult" parts. [1] There's a lot to hate. Imagine, on the flip side, if you had to program in RPG II. You'd want out as soon as you realized you made a mistake. Admittedly, RPG of any flavor doesn't sound sexy, but you get the idea.