4 ms·
I've finished Martin Odersky's Scala Course. I've built a few small play2.0 apps. I've used Scala to solve ~20 Project Euler problems, and I'm fiddling around w
by pkinsky 13y ago
I've finished Martin Odersky's Scala Course. I've built a few small play2.0 apps. I've used Scala to solve ~20 Project Euler problems, and I'm fiddling around with parsers and scalaz.
However, all the Scala positions I've found are looking for engineers with experience using Scala in production. How can I make that jump? Are there any opportunities out there for junior engineers who are proficient in Scala?
- jorgeortiz85 13y agoSend me your resume: jorge@foursquare.com
- pkinsky 13y agoThanks, sent!
- deleted 13y ago[deleted]
- efuquen 13y agoDo you live in NYC? The place I'm working at now was looking for some people, not necessarily with production Scala experience. Not sure if they're still looking, but first off you would have to be living the greater New York area :-)
- eranation 13y agoIf you are in the UK, let me know...
- pkinsky 13y agoI'm on the other side of the pond, sadly.
- chiurox 13y agoIf finding a Scala position in the US (I assume) is already this difficult, here in Brazil it's infinitely harder. I guess our startup is one of the very few that has a fairly large system in production running on Scala, Play, and Akka. It's next to impossible to find people with experience yet alone experience in production. The key is to find people genuinely interested in learning.
- ropiku 13y agoI went the other way, started working at Twitter without knowing Scala and it wasn't hard. We also have great internal Scala classes. Feel free to email me for more info (see profile). We're just looking for smart people, you don't need to have experience with Scala.
- pkinsky 13y agosent, thanks!
- rybosome 13y agoBe careful; once you've been working in Scala, going back to Java is unpleasant. =)
- seanmcdirmid 13y agoI worked with Scala at EPFL during my 2 year post doc (in Martin's group). I later started working for Microsoft, and found the transition to C# to be initially painful but not incredibly so. I'm now a happy C# programmer, though I take a lot of liberties [1] with the system, and I also use C# mostly to build programming systems of my own [2] (though Scala has had an everlasting influence on my own work). C# is a bit more advanced in Java (they have lambdas), and in someways better than Scala (reified generics). But the best thing about C# is that...it forces you to to settle on less elegant but functional designs in a "worse is better" style. I found myself obsessing over my Scala code to come up with perfect solutions because...I could...while in C# perfect solutions obviously don't exist. C# relieves the burden of choice, which is an interesting trade off to keep in mind when designing PLs. [1] http://bling.codeplex.com/ http://bling.codeplex.com/ [2] http://research.microsoft.com/apps/pubs/default.aspx?id=189802 http://research.microsoft.com/apps/pubs/default.aspx?id=1898...
- rybosome 13y agoThat's actually a very fair point - when it comes to usability with respect to the functional style, sometimes less is more. I think C# is actually a pretty good example of a pragmatic language that offers FP to make your life easier, but doesn't beat you over the head with it. If I could choose between Java and C# purely on the basis of the language, there is no question that I'd choose C#.
- pkinsky 13y agoIn my (limited) experience, for expressions make for some of the most concise code I've seen. So many problems can be represented as a chain of Options or Futures mixed with standard {val x = expression y} expressions.
- seanmcdirmid 13y ago
- dberg 13y agosend me your resume developer@huffingtonpost.com
- pkinsky 13y agoThanks, sent!
- sbilstein 13y agoLinkedin uses Scala for many different teams. My team does. Apply and tell the recruiter you want to work for a team working with Play with Scala.