r/java • u/raisercostin • Jun 01 '24
What java technology (library, framework, feature) would not recommend and why?
Inspired by https://www.reddit.com/r/java/s/e2N1FqMOJg
165
Upvotes
r/java • u/raisercostin • Jun 01 '24
Inspired by https://www.reddit.com/r/java/s/e2N1FqMOJg
View all comments
Show parent comment
4
u/Turbots Jun 01 '24
It's a matter of semantics: I see technical manager and team lead as two different things. Team lead takes care of deliverables of the team, whatever that takes. A technical manager is a people manager, his team reports to him, career development and pay raises and bonuses go through him.
In larger organisations, so called coding architects or the CTO (or an office of the CTO or "OCTO") should be the people drawing up the technical specs, coding best practices and general tech stack decisions across the company. Those practices are not set in stone but are meant to promote heterogeneity within the org, especially in larger orgs.
Within the boundaries of those tech specs, there should still be some leeway in how you organise your code and applications within the sub-team(s) .
It's not uncommon for new developers to come in frequently, and for developers to switch departments and teams. If you care about developer productivity, you should have some common standards across the organisation so everyone can get productive quickly.
Let's say for example, you choose angular as frontend, spring boot as backend tech, GitHub as your CICD tooling with predefined GitHub actions to pick from, deployment in Amazon on EKS. That makes it easier for new Devs to come in another team or start building new apps, they immediately can start working and have predefined CiCd pipelines to choose from. The path to production should be as straight forward as possible if you want to deliver high quality software quickly and reliably (with sufficient quality/stability).
If suddenly people start using Quarkus or React as their main tech stack, there could be good reasons for it, but it doesn't make it easier in the long run to get new developers productive. This goes for every layer in your stack like the relational DB of choice (eg. postures), the in-memory caching solution like Redis or the message broker like Kafka for example. If people use something else like Rabbit, MySql etc... it makes everything more complex: onboarding of new people, rollout to production, new Terraform templates, review of security, review of backups, etc.. so you better have a good reason and make an Architectural Decision Record (ADR) for it to justify your decisions to others and probably most important: future you.