I'm glad that there's 97 things that professionals recognize that are important but what is the weight of importance of each topic? What are the priorities? For example, TDD, Kotlin, Uncheck your exceptions. (reading from the index).
But it's really going to depend upon:
- The business domain of your application
- Your non-functional requirements (performance etc)
- The technology stack
- The team
and most importantly: You. Where you are now career-wise, where you want to be.
That's ok, don't worry. haha Was kind of expecting that answer. I guess the trick is not 'panic' about learning every single topic right away but it's rather a nice guide for interesting topics that a Java programmer shold be aware of. I think I'm still a beginner so I'll take the books lessons as "Here it is, kid. This is a bunch of things that your fellow java seniors encountered till now. Go have a look at these."
As Trisha said, "It depends". And it really does! What each person knows and needs to know is dependent on so much more than will fit in a simple answer. What we hoped in the book was to be able to offer people a large enough sample and cross-section of what we think people should know, and in that people will be able to find their own path.
I yam what I yam and that's all that I yam - the great philosopher Popeye. Tiny ad: