Hacker News Reader

I've had a (relatively) bad time with Scala codebases. The last one I was involved in was like a 6-minute wait between making a code-change and being able to run or test it. But I still wanna work with Scala devs.

I'd rather work with Scala devs on a Java codebase than Java devs on a Scala codebase.

It's not about intellectual appetite though. It's about not re-litigating the same crap at every new work place. Avoid mutability and nulls where possible, etc.

View on HN

> I'd rather work with Scala devs on a Java codebase than Java devs on a Scala codebase.

And Java devs on a Scala codebase is effectively the norm once your project enters BAU/maintenance phase.

One of Scala’s major issues is that it’s too easy to write Scava IMO

its a feature not a bug

The problem is that it is easy to write code that is not easy to read/understand afterwards. Especially if the code has a lot of operator soup and implicits.

Do people still do that? I thought that the whole "you can just google goobedygook" meme died already! ZIO for this reason has sane normal proper names for things for example.

Reply on news.ycombinator.com