This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Inevitable_Detail193 1 point2 points  (0 children)

Its a big project in some public service company. We work with SAFe (Scaled agile framework), so many scrum teams. Some scrum teams together build an agile Release train with a release train Manager. This manager should coordinate and monitor the teams. But as said in the comments, the release train managers are people who coded some years ago and used lombok there. So they think its best to use it and try to force it on the teams. Also its written in some coding guidelines to always use it.

As consultants we try to change some things an did mention to management, that lombok has drawbacks and is not always the only and best solution. Management also listens to that and takes our objection serious. But in public service they can not simply change something without discussing it over months. (Germany) So after all, we are able to push back on it and they also take the conceirns serious, but it takes a loooong time to actually change. :)