If your company pays for that, then that's cool!
Whereas with my workload and circumstances within the company, that's not realistic.
In the past 2 weeks, i've:
- worked on migrating large enterprise apps from Java 8 to Java 11
- worked on migrating those apps from Spring to Spring Boot
- worked on containerizing them and carrying over configuration parameters
- edited a whole lot of legacy code that was needed for all of that to happen and documented the process
- helped people deal with external integrations and PKI related configuration and Ansible
- helped onboard a person on the project and consulted other junior devs
- got called in to work on a PHP project even though i'm technically a Java dev
- consulted a person on how to use Figma to create designs for the app (even though i'll just have to develop it?)
- realized that the app has literally no onboarding instructions or documentation whatsoever, so set out to create those
- developed some scripts to seed the DB with test users and data, otherwise the app won't even allow logging in locally
- consulted with the clients about all of these things, waiting for additional feedback on that
- fixed a few bugs here and there, did the usual meetings, sprint estimation, architecture stuff etc.
As for how well i'm paid, i wouldn't necessarily use the word "highly":
https://blog.kronis.dev/articles/on-finances-and-savingsRegardless, that probably shows that there is a world of difference in both compensation and the workloads of people. While having the time to learn new tech on company time would be good, it simply isn't my current reality, nor is it the reality for many out there. Thus, if i don't want to have my skills become obsolete, i spend the occasional morning/evening/weekend working on pet projects. That needs to be taken into account.
Curiously enough, i've heard some people voice the opinion that their workloads actually lessened in larger companies where they also happened to be more highly paid.