I just got an offer for a junior dev position. The place uses a lot of Scala and i'm not really familiar with it...

Either java with more features, better syntax and a more consistent type system, or some horrible third party JVM-haskell abortion, or anything in between.
The language is very liberal, it really depends on the team and the conventions or lack therefore they use.

Imo you should definitely take it and gain experienced. You can make a shitload of money as an experienced Scala dev. They're one of the best paid developers out there.

>gain experienced
*gain experience

That was my line of thought. It seems like it's really catching on for big data applications, so I was hoping to get some experience it it before it becomes the norm.

This. Scala is a good language, but its type system was a little too powerful and attracted haskell autists. If used as a terse Java with good type inference, like in Spark or Akka, then it's fine. But run away if you see a project using Scalaz.

Kotlin learned from that and crippled its type system a little to keep the haskell crowd at bay. But Scala still is a bit better language except for compile times.

Sorry but Scala and Kotlin are not even competing against each other. Kotlin is supposed to be a better Java, nothing else.

*Kotlin will also fade. Many people jumped on the Kotlin bandwagon but over time a lot of them have jumped back to Java because they did not see the point. Though I like Kotlin a lot, I think many people who jumped back to Java felt the same way. At first sight, Kotlin seems to save you a lot of time but in reality it doesn't. As abhorrent as it may sound, for some fucking reason it's also very difficult to move away from Java's style of coding because you get used to it.

Autism
books.underscore.io/scala-with-cats/scala-with-cats.pdf

Just avoid use Scala as Haskell

Wow, never knew pajeets feared the typelevel stack that much. Truly F[_] is what Jow Forums most fear

Waiting for your codebase to compile

Your anecdotal evidence is not particularly supported by any of the statistics. Kotlin's trend has continued to be a slow stead upward whereas Java has been hemorrhaging market share.

You're in for by and far the worst implementation of functional programming.

Decent language, terrible toolkit. But either way you're in for a pretty steep learning curve at first if you have no experience with functional programming.

Typelevel stack is fucking great. I use fs2 in production and it's amazing. Haskell is great too, but it's not an option for us, but even if it was I wouldn't consider it a huge step up. Sure, some of the default shit like Future is broken janktastic shit, and trait + case class is far too verbose for ADTs, but it's really not bad

country and salary?

yet another
>scala is meh but haskell is such a meme I can't reasonably use it for serious work so this will do, let me just import all these nonsensical concepts real quick
filthy haskell migrant.
If you don't integrate into the traditional OO culture you DON'T belong in scala and should go back to your socialist language and its lack of jobs. Scala is for OO programmers ONLY. Love it or leave it.

>Scala is for OO programmers
nice

Attached: 1532790707928.jpg (500x491, 65K)

Burgerland

Initial offer was 40k, I'm going to counter 45k

This my first dev job after working warehouse jobs for a long time. I don't have a degree, I went to a boot camp. The salary is pretty par for the course in my city with no CS degree or prior experience (cost of living is super low here). I'm just looking to get my foot in the door and going to a place that mostly specializes in back-end development and uses Scala seems like the right move.

(you)

Attached: 1542227998165.png (556x712, 16K)

Damn, that is exactly what I want to do. Age? How long have been programming? Any tips?

25

I started this year. Went from helloWorld.html to writing a full stack Java web application.

The only advise I'd give is to do lots of projects, put them all on GitHub, and be able to go into detail about the tech you used. A bootcamp isn't completely necessary, but it's helpful for building a resume of projects.

>Kotlin's trend has continued to be a slow stead upward whereas Java has been hemorrhaging market share.
Congratulations, you have ignored half of what I wrote. How the fuck are you going to measure Java's marketshare? Nobody uses Kotlin in backends, almost everyone uses Kotlin for Android apps. Also I never denied that Kotlin has been gaining market share. I have claimed that Kotlin will fade again because that's what "brand new and better" languages whose mere purpose was to replace another language have always been doing. Kotlin fills no hole. Many of my colleagues have tried out Kotlin and despite of everyone liking the language, nobody has ditched Java for it because in reality it doesn't make you code quicker or cleaner.

Thanks! If you don't mind sharing, what state are you from? I'm from Michigan and I hear there's a pretty big demand for devs here but not a lot of people to fill the positions

My state borders a state that borders you. That's all I'll say. I don't live in a super tech-heavy city, we're mainly known for healthcare. I'm sure if your area needs developers badly you can slide in with minimal experience as long as you have projects you can talk about. Half of getting in seems to be interview skills. Know how to talk about yourself and your dev skills without sperging out.

>Half of getting in seems to be interview skills. Know how to talk about yourself and your dev skills without sperging out.
...yikes, got any tips for that? heh

do a job with a high risk of death for about a year and you'll have confidence to take with you for a lifetime, user

>do a job with a high risk of death for about a year and you'll have confidence to take with you for a lifetime, user
anything barring that?

alternatively, what life-threatening jobs do you suggest? I certainly live a cushy life

Just b urself

That's a tough one. It's mostly confidence. Build solid applications you're proud of know the tech. It's normal to be nervous or anxious in an interview, but don't completely shut down.

Also one of the best tips I've gotten was don't give short answers to tech questions if you have experience in whatever they're asking you about. If they ask you questions about specific languages or frameworks, relate it to a project you've done if you've used it. It shows a deeper understanding of whatever concept they're asking you about.

I get where you're coming from but that's pretty retarded.
Just build good applications and know that makes them work. What languages do you currently know?

Thanks for this, /u/eed3si9n, it's very appreciated. Since moving to Haskell, I am continually in awe of the severe contrast in communities, not just in intellectual curiousity, but in diversity, too. You rightfully focused on 2 major pain points for women (or at least, for myself), which are unwelcome romantic advances, and a lack of assumed competence. The latter is by far the most frustrating for me, and it's one of the reasons why I have started to use more agender handles on social media (obviously barring this site).

I would like to add 2 additional pain points to the list:

Insulation vs accommodation. Some communities, in response to women asking to gain entry, will opt out of advertising their communities, and opt out of explicitly locating a diverse population, locking down the status quo. If communities are allowed to perpetuate these old-boy's clubs and silent meeting spaces, it only perpetuates Scala's diversity problems. Secret Slack rooms, secret gitter rooms, irc channels, etc.

No Zero Tolerance Rules. You want a more diverse population in Scala? Great! Then this needs to be taken into account when moderation rules are applied during interactions with more diverse members. Is this a call for a separate set of rules? No. This is a call for considering the context of Scala's diversity goals when applying the same rule set to different people. The anecdata suggests that women have wildly different experiences within tech, and many of them traumatic to varying degrees. Consider this when making decisions.

Without going into specifics, the Old Boys Clubs, the moderation tactics, and the assumed incompetence were some of the most infurating parts of working with Scala, and were a heavily weighted factor in why I left (along with 2 other women, all of us to Haskell). Consider being dropped into Scala and getting hit with a Do Not Hire list threat as a woman in tech. Good Luck.

Autism

reddit.com/r/scala/comments/9ysz5z/making_conference_a_safer_space_for_women/

I'm not reading that lmao

Attached: gold.jpg (600x656, 71K)

This is solid, saved for later

So I started about a month ago and I know the basics. I completed some MOOCs, one on Python. I learned a bit about OOP, basic stuff like control structures and inheritance and stuff, basic searching and sorting. Right now I'm learning to develop Android and iOS apps with a few crash course style tutorials.

What I'm picking up is that most of mobile development seems to be just implementing existing toolkits properly, unless I'm misunderstanding something, and the #1 skill I clearly need to have but currently lack is just reading and effectively synthesizing the docs. The docs are just so fucking long and meandering when a simple tut can show me a block of code with a breakdown for how it works (assuming I understand the basics already) and I grok the concept in like 5 minutes vs. hours of pouring over the official Apple docs for example and learning by trial and error and so forth.

tldr I know a bit of kotlin, java, python, swift
I am best at Python right now but like I said I have only been learning for a month

Can you guys giveme a sort of simple tl;dr checklist for what I need to know (on a basic level, like bubble sort and such) to get an entry level dev job?

For most entry level jobs it seems like they just want someone who's capable of learning whatever language and framework they use. Most of my knowledge is related to Java and most jobs I applied for weren't Java related. If you go into an interview and show that you have a depth of knowledge in one language they'll see that you can learn whatever they use.

I know that's vague as fuck but that's pretty much the gist of it. Build a functional phone application or web application and be able to talk in detail about how and why it works.

>Build a functional phone application or web application and be able to talk in detail about how and why it works.
Should it be full stack (aka my own back-end or API or whatever) or is a mobile app enough if I'm looking for mobile positions? Or am I thinking too narrowly by planning to get a job in mobile alone--should I cast a wider net?

I'd say go with a full-stack web app. In my experience most places are looking for web developers rather than mobile developers. And I'd assume most places who need mobile developers will take someone with web dev experience. Take that with a grain of salt though, I never got an email back from any of the mobile developer jobs I applied for though.

Definitely check Indeed or ZipRecruiter and see what's most needed in your area though.

definitely counter with at least 45, 40 seems a little low even for someone with bootcamp and already has some experience. Most entry level jobs are at least 60-80k for someone with CS experience, so I would say 50k would be fair

Thanks

I mean a QT gas station assistant manager makes 42k a year average.

No problem dude. Good Luck!

you too senpai

There were some details that were left out here concerning how interactions played out between Typelevel and Scalaz that were incredibly concerning, and inform the strength of the conflict. There are emails that show that Lars' ultimatum was continued with Lars messaging Tony's place of work twice , urging them to terminate his employment over Tony's response to Lars' theft of Scalaz (the emails are readily available through different avenues).

Lars had effectively removed all maintainers from Scalaz with the exception of his friends, and a few choice folks like Paul Chiusano and Runar Bjarnason, and effectively "taken" Scalaz, folding it into Typelevel without communicating it to the core maintainership (those whom he banned). It was only later, that he was convinced by a few of those that were left to continue with a fork and call it something else, stepping down from Scalaz.

Since that time, there have been verbal fights between Scalaz and Typelevel sympathizers over this conflict, culminating over the last few years in events such as supporting people calling for Do Not Hire lists, and with someone sympathetic to TL calling in a literal false rape threat so that Tony had to talk to the police. Typelevel leader Stew recently stepped down because he didn't want to give up the privilege of actively conflating Scalaz members with racists/neo-nazis. Vitriol like that extended even to Scala contributors like Scalaz's Kenji, and there was an active strain of denialism among Typelevel and Scala folks as this was going on that lent to escalating the conflict over time

Women In Tech
reddit.com/r/scala/comments/9a11p1/newbie_wondering_about_the_history_of_the/

>programming language has divrrrsty goalsss

Attached: images(2).jpg (358x240, 7K)

emi1ypi is that you?

Very. Java will give you a platform from which to climb, no doubt, but there's a steep learning curve with sub-par documentation. Read the Scala site's tutorials for Java devs for a good start