I've been thinking of taking a peek into Java, which I've never really written[1]. Is the general thinking that, for something like a Spring Boot application, it's much better to just start with Maven? I'll admit I am, aesthetically, displeased with the mountains of XML config I've seen in some tutorial articles, but I imagine it's a lot simpler to maintain over time than any DSL would be.
[1] slightly off-topic, but if anyone's curious why: I haven't been very impressed by any of the "Kotlin-first" JVM libraries I've seen (like ktor or exposed), I think coroutines are neat but much more suitable for main-thread-focused situations like Android apps than something more easily threaded like web servers (and with Project Loom hopefully upcoming in the next couple years this might be a moot point soon), and I don't like the JetBrains tooling lock-in (e.g there's no well-supported language server for Kotlin, unlike what Red Hat's been building for Java)
> There’s no excuse for not publishing a salary or salary range
There is nuance around what is competitive comp for different departments (eg. engineering vs customer support), and how current employees in the lower paid departments will perceive the difference in comp across departments. I am all for publishing salary ranges, but it doesn’t come for free, you will wind up with more ill feelings among team members in lower paid departments, even if you pay everyone market compensation. It’s probably still worth publishing salary ranges though, for all the reasons cited in the article, and that it saves everyone time.
Because, trust me, as someone who's worked at multiple B2C companies with large customer service departments, everyone absolutely knows, which is why us in the engineering department were always happy to buy the rounds at cross-company happy hours.