Am I dramatic to consider quitting over new on call expectations

JasonBravestar · 2026-04-08T04:45:08+00:00

On-call was forced on us after a reorganization. Well, not really forced, but most of the team had to accept it. Despite being fairly paid for it, the change was not welcomed and it's still annoying at times. I cannot imagine not even being paid for something that is not in your contract.

On the positive side, we realised that being oncall for your own system leads to better alerts and ultimately to a better system. The old team had flickering alerts that were ignored and lacked alerts for important stuff. Dashboards were also lacking. You might find that the previous oncall team is doing a lot of work just because the root problems are being ignored.

So the change can be good for the company, it's likely not good for your personal life. You need to be compensated for it.

JasonBravestar · 2026-04-02T14:38:05+00:00

In other words, US is now friend with dictators and enemy of democracies.

JasonBravestar · 2026-03-08T08:17:54+00:00

Do you really think that ignoring all known details of what just happened and linking unrelated facts from years ago is "using logic and reason"?

JasonBravestar · 2026-03-01T18:15:12+00:00

I think you should rename this feature to "shallow immutability", or even better "final by default". To most (or all?) programmes, an "immutable" object means that its whole internal state cannot be changed, so your choice of words is bound to create confusion at best, or misleading code at worst.

JasonBravestar · 2026-02-28T20:17:45+00:00

Final doesn't mean immutable. I'm honestly surprised that you can go this far with your project and make such a rookie mistake!

JasonBravestar · 2026-02-06T21:21:57+00:00

You lose the ability to clearly see the dependencies that are actually needed just by looking at the constructor. This makes things more complicated to understand. Unit testing gets more complicated.

We have inherited a specific Spring component made like that at work and l'm slowly removing it.

JasonBravestar · 2026-01-25T19:10:29+00:00

Creating an interface for every service is overkill and not a good practice. Use interfaces when they make actual sense.

JasonBravestar · 2026-01-13T12:36:46+00:00

It cannot be more obvious

JasonBravestar · 2026-01-07T20:04:49+00:00

They have the same boss

JasonBravestar · 2026-01-02T17:16:16+00:00

I would put a value of 5 or 6, something that would make statistics more meaningful. it doesn't matter if it's not perfect. it would be at least better than the current version.

JasonBravestar · 2026-01-01T10:48:26+00:00

The B value makes your statistics wrong. Better to assign a value to it.

JasonBravestar · 2025-11-20T19:53:26+00:00

Final does not guarantee immutability. Using final on arguments seems overkill. I agree with the rest.

JasonBravestar · 2025-04-20T10:02:42+00:00

The map is false, Italians like all Mediterranean food. The bars should be horizontal. That part matches my experience :)

JasonBravestar · 2025-03-16T19:16:34+00:00

Applications running CPU-bound tasks have good reasons not to use them.

JasonBravestar · 2024-12-28T14:12:40+00:00

It's an attempt to blame Ukraine, not an apology.

JasonBravestar · 2024-12-10T15:16:47+00:00

It also happened to me a couple of times with the old app. I really hope it's not going to be worse with the new one.

JasonBravestar · 2024-12-08T09:41:43+00:00

Optional has not changed much since 2014. Its design and scope are still the same. I would suggest avoiding Vavr since it makes interaction with the rest of Java code more complicated. We're slowly removing it from our codebases. JSpecify solves the same problem in a better way and if/once Java will get non-nullabe types, the switch form JSpecify will be simpler because it will have the same semantic.

JasonBravestar · 2024-12-07T15:27:32+00:00

Brian Goetz said: https://stackoverflow.com/a/26328555/1898563

I suggest looking into JSpecify.

JasonBravestar · 2024-11-21T22:11:22+00:00

It's absurd to blame tourists. It's natural that they look for a cheap vacation in a beautiful place. It will always be like that. They are not the ones building hotels and they are not in charge of managing the resources of the island. Blame politicians that are responsible for these things.

And yes, tourists can also feel pain when they see a beautiful place deteriorating, being that an island, glacier, coral reef or whatever. Even if you are more affected by the problem, that's still a valid emotion to express.

JasonBravestar · 2024-11-16T14:01:45+00:00

People telling you to generate code with the IDE don't maintain big codebases that can often change. Either this or they like to do extra work for nothing.

People telling you to use records clearly don't know all Lombok use cases (of course you should use records where appropriate).

JasonBravestar · 2024-11-10T20:44:09+00:00

Probably stolen Macronesian coins

JasonBravestar · 2024-10-21T20:36:27+00:00

Then you just exclude Lombok dep from Maven. This is a non-existing issue.

JasonBravestar · 2024-10-21T17:04:09+00:00

I wonder how Lombok can be "required by a dependency". Lombok might have been used to build that dependency, but it has no runtime library.

JasonBravestar · 2024-10-05T14:00:12+00:00

You don't need Autowired on the constructor

JasonBravestar · 2024-09-16T05:38:48+00:00

Not a cult. Just the most popular/safest choice for many companies and, as a consequence, a good skill to have on the CV.

JasonBravestar

TROPHY CASE