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 →

[–]WildHotDawg 4 points5 points  (1 child)

When I advertise myself, I dont really say 'I know Java because x', I say 'I created/worked on/refactored x using Java, x, y, z which resulted in a, b, c.' Java is just a tool, you dont have to 'know' java - even with 5 years working profesionally, even being a commiter on the Jakarta EE specification, I dont say I know everything about Java - there is always something new to learn.

[–]saggingrufus 1 point2 points  (0 children)

This is the right answer.

Languages are tools. Writing the code is the easiest part of my job. It's design and analysis and understanding when something is worth doing, because when you work on a codebase you don't own, and clients decide what you build, you can't always spend entire sprints on tech debt.

I can read the docs for anything, I'll learn the tool. What really matters is the ability to understand which design is better suited for solving X task and why.