5 ms·

I considered it a near miss when a Scala shop rejected me because I used Maven to compile their coding challenge. Clearly the company was full of over-complicat

I considered it a near miss when a Scala shop rejected me because I used Maven to compile their coding challenge. Clearly the company was full of over-complicaters and actively recruiting for it.

_vertigo 5y ago
How did that conversation go? “We like your solution but did you seriously just use Maven?” What did they say exactly?
- the_only_law 5y ago
  Yeah that’s got to be up there on the list for dumbest technical related rejection I’ve ever heard of, particularly if the code was done well otherwise.
- deleted 5y ago
  [deleted]
alexott 5y ago
I also prefer to use Maven to compile Scala code - it's much faster, better integrated with IDEs, etc.
deleted 5y ago
[deleted]
SOLAR_FIELDS 5y ago
As opposed to Gradle or SBT? If I'm being honest here, a quite significant part of day-to-day backend JVM software development positions is dealing with the build tool. While I wouldn't outright reject a candidate for not being familiar with the latest standard toolchain (Gradle), I would certainly consider it as one of many factors - Gradle is pretty complicated, yes, but also quite powerful in what it is capable of achieving. It's not as eyebrow-raising as, say, if you sent in a coding challenge compiled using Ant (which would, in fact, be quite a fun discussion to have with a candidate) but it would certainly be something considered.
- tlarkworthy 5y ago
  > If I'm being honest here, a quite significant part of day-to-day backend JVM software development positions is dealing with the build tool. perhaps, because your work has over complicated it [1]. [1] If you are doing multi-distributions or multi-repo stuff perhaps it's warranted, but those complex build features better be providing serious value to the business to be worth losing 10% of the development workforce's time on build tooling.
scalaIsKindaMeh 5y ago
That's silly but unfortunately this type of silliness is the norm in the industry.

I considered it a near miss when a Scala shop rejected me because I used Maven to compile their coding challenge. Clearly the company was full of over-complicaters and actively recruiting for it.

_vertigo 5y ago

How did that conversation go? “We like your solution but did you seriously just use Maven?” What did they say exactly?

the_only_law 5y ago
Yeah that’s got to be up there on the list for dumbest technical related rejection I’ve ever heard of, particularly if the code was done well otherwise.
deleted 5y ago
[deleted]

alexott 5y ago

I also prefer to use Maven to compile Scala code - it's much faster, better integrated with IDEs, etc.

deleted 5y ago

[deleted]

SOLAR_FIELDS 5y ago

As opposed to Gradle or SBT? If I'm being honest here, a quite significant part of day-to-day backend JVM software development positions is dealing with the build tool. While I wouldn't outright reject a candidate for not being familiar with the latest standard toolchain (Gradle), I would certainly consider it as one of many factors - Gradle is pretty complicated, yes, but also quite powerful in what it is capable of achieving. It's not as eyebrow-raising as, say, if you sent in a coding challenge compiled using Ant (which would, in fact, be quite a fun discussion to have with a candidate) but it would certainly be something considered.

tlarkworthy 5y ago
> If I'm being honest here, a quite significant part of day-to-day backend JVM software development positions is dealing with the build tool. perhaps, because your work has over complicated it [1]. [1] If you are doing multi-distributions or multi-repo stuff perhaps it's warranted, but those complex build features better be providing serious value to the business to be worth losing 10% of the development workforce's time on build tooling.

scalaIsKindaMeh 5y ago

That's silly but unfortunately this type of silliness is the norm in the industry.