Sounds like a startup, and with the small scale in mind, it should be whatever the team is most comfortable with. And ideally something that isn’t too hard to hire more people for. Makes me wonder what made them pick Java in the first place for the prototype, if there’s no love for it.
Edit: For task management, issue board etc. it’s probably best to let the team(s) choose/vote for what they enjoy working with, rather than prescribe it from the top. Your process is more important than what task management tool you happen to pick
I think it’s a part of their convention over configuration philosophy. Say what you will about it, there are obviously drawbacks.
But I’ve noticed that it makes it easier to quickly understand new codebases in my organization. Everyone are using Next.js and all the apps have about the same file layout.
I’ve conducted many interviews that starts off with asking questions about projects. Many candidates sound like rockstars. They even nail all sorts of technical follow-up questions.
Then when I start asking coding questions, and I’m not talking leetcode here, more similar to fizzbuzz, they can barely write an if-statement. My conclusion is that some people are great at talking, but you really need to test the technical abilities too.
Impressive! Curious how you went about building this. Did you follow a similar journey to the poster, by exploring other Spotify services in addition to the public API?
Edit: For task management, issue board etc. it’s probably best to let the team(s) choose/vote for what they enjoy working with, rather than prescribe it from the top. Your process is more important than what task management tool you happen to pick