> Because the last thing I want is you designing or coding all day and night and then getting burned out and rage-quitting. Yet both examples of employees with

> Because the last thing I want is you designing or coding all day and night and then getting burned out and rage-quitting. Yet both examples of employees with hobbies are people who code outside of work. I'm certainly guilty of this, but I would suggest that unless you're 100% devoted to a single goal during the day, you can use your job as a means to tinker with code-related stuff you're interested in. For instance, the people doing ML and AI degrees should be doing it on company time, especially if it's benefiting the business. Ask your boss and you'd be surprised what benefits you can squeeze out. I'd strongly recommend getting into something more creative or totally orthogonal to your career. For example I've done a bit of pottery and learned some basic woodworking - both of which I'd like to improve on. Music or languages are two other hobbies which are generally accessible. You can sometimes find odd passions via work. I've done some projects in smart agriculture and it got me into gardening in a nerdy way. The science behind commercial horticulture is fascinating - it's half cutting edge research and half "old guy" expertise. My tomato crop was a lot better for it. If you want to really nail the hipster, rounded, programmer stereotype, get down to the climbing wall and start brewing beer. No surprises why climbing is popular with programmers. It's a lot of thinking, works just fine as a solo (or group) sport and tends to attract people who didn't enjoy "conventional" sports at school.