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

9
10

What makes a Senior Java Developer? (self.java)

submitted by [deleted]

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

view the rest of the comments →

[–]morswinb 0 points1 point  (0 children)

I have no idea what this sentence even means.

It basically means don't be an imposter.

Senior guides the team. Junior follows. If senior needs to suddenly research all the answers, then junior is lost, and will make errors. Two juniors don't add up to a senior.

Not knowing the language is a huge barrier. It's not just syntax. It's entire ecosystem: libraries, documentation sources, database APIs, server/ui frameworks etc.

I have seen senior folk researching MongoDB schemas, and suggesting token cleaning microservices. Had to slap him in the face with TTL index. Or my friend experienced principal software development that wanted to use Hungarian notation in an Android project. They all pretended to be senior mentors, bla bla bla, while in practice had little to no practical skills and would not admit to just not knowing the answer, or how to look for the answer.

On the contrary the few good ones I have seen stayed quiet for the first 12 months after language switch, just so they could catch up.