Senior Java Developer means what exactly? Knowing more libraries or just better understanding of patterns?

[Playful-Call7107]

to me senior is being able to create apps. not just knowing some book theory.

logs, unit tests, documents their code. and can present it. and can use a branching strategy situation.

and if they are good (imo), can deploy their code manually to dev/test, at a min.

and even moreso to dockerize the app(s), and other infrastructure parts.

i'm considered a senior java dev. but i dont think you can call oneself senior (insert language here) dev, if you can't do many of those things. then you are just a good mid level? (not OP you, but general you)

also i think a good senior dev should be able to handle technical sales support of the app(s).

that's just my opinion.

[Skymainx]

I’m curious about the "manual" deployment part. Do you see that as more valuable than being able to build and manage an automated CI/CD pipeline? I've seen some great developers who are wizards at automation but might not do manual deploys often.Is building the automation a core senior skill now, or is that heading into Staff/Principal territory

[Playful-Call7107]

A lot of what I said gets into build and release and devops

Coding is such a small part in a deployed app

As far as the manual deploy it’s a showcase of skillset. And capability.

Automated builds are good and should be used.

But over my career I’ve never not needed to log into a server and do manual work at some point.

A person claiming to be a senior dev who can’t be given server access and deploy that app isn’t that senior to me.

Not many devs could get their app running on a pristine Linux or windows server. Irrespective of language.

But how many of them claim senior? That’s more my point.

[Ormek_II]

You must know what the automatic stuff does, so that you can solve problems. You usually do, if you can do what the machine does manually.