Oh heck nah.
And if you don't let people experiment during work, but only hire people that do, then that's a bad sign.
We found solutions and tools that better solve problems but to this day have still not been implemented.
Not everything needs a novel solution but not making room for innovation because the company is operating as a feature factory is boring.
Why would being up to date matter?
May I ask what industry you work in?
I thought he was going to say that it was something like a foundational R&D lab or cybersecurity firm
If anything, personal projects can end up being distractions from focusing singularly on work. Even though I'm entirely in favour of them, I also remember when I had a newborn at home and a family member in hospital, and such projects were not at all feasible.
I recently meet a programmer in his 50s, still working on Cobol. Sure, you aren't gonna hire him, but do you think he has any worries about his job?
Huh? What kind of stuff ya do?
At-work choices are rarely choices, because you just do the next thing the same way as you did the last thing. If you step out of line, management will reel you back in. A 'big' change is switching from Spring to Micronaut (or vice versa).
Some examples: I have pretty strong opinions about ORMs vs SQL. It would be interesting to discuss that on the job with someone who knows both well. But the guy you'll be talking to won't have tried SQL (beyond that academic thing they learnt at uni).
Discussions about languages and types? "Java is good because it has types and JS doesn't" was the level of discourse I got at my first serious job.
Having side projects at least indicates that they can try things out first-hand, own their own feedback loop, experience some surprises, and not just mindlessly cargo-cult "best-practices".
If you want to be able to experiment and change things, go to a startup.
I mean, it's your choice, but your loss too.
All the good programmers I know have side projects and live and breathe code. None of the mediocre/bad ones I know do.
Think of it this way: what's likely to make you a better programmer: spending half (0.5x) of every day on (a work-mandated subset of) code or spending most (1x) of every day on code? The answer is obviously the latter.
And it sounds weird, but most of my programming knowledge comes from outside of work, even the knowledge that I apply at work. Maybe it's because work naturally discourages exploration since you're focused on the company's priorities. For example, I'm never implementing a collection in C at work (I use `std::vector` and stuff). Yet doing that in my own time taught me why certain operations invalidate iterators -- a thing senior coworkers of mine didn't understand and which helped us catch a bug. :D
Young me would've enjoyed the process of building a thing, ignoring problems like maintenance burden, how fragile or brittle the new tool is, lessons learned from the old tool, etc. etc. (you know how it goes)
Current me will take a task and mull on it. No pen to paper for _days_, preferring a minor adaptation to the existing process, or discovering that the desire was misguided in the first place. The work not done and wisdom to not do it is worth its weight in gold.
Or people who used to be in their 20s.
8 hours of software development is more than enough practice for a developer. Having an employee with a well balanced life is superior to one who is unable to detach from his work.
I mean I do have side projects, but those are all in a language I'm not specialized in and often single class small helper programs.
And the best developer I ever worked with had zero public repositories in Github. Now that gave me some perspective.