Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
This sounds like a recipe to get fired, especially if you're working with a third party client (imagine taking a nap and wandering around at a customer's premises). Write public articles, start a company coding club, seriously? Don't you have a product owner who's responsible for prioritizing that long long backlog?
@fasttime Yeah I have some startup goggles on, and I'm in somewhat of a leadership position. But I've found "classic" office rules to be counter productive.
I encourage people to write tech blog articles, because it's good for their own personal development. When you write publicly about a technique or package, you're gonna do deep research, it's like a rubber duck on steroids. Blog articles written by employees are also good company PR, we've recruited several devs because they read our publications.
I encourage people to sleep, destress, run, meditate whenever they feel they need it, during office hours. Forcing yourself to work when nothing is happening is a waste of time — there's a reason "showerthoughts" are a thing. When you're stuck on a bug, go for a run, play a game, whatever works. An employer whipping employees into cubicles is a stupid employer.
And yes, I recently started 3 coding clubs at work. Out of the ~100 webdevs, half a dozen are experimenting with Rust, half a dozen are working on their first mobile app, and a few are taking Phyton/ML workshops. This results in greater developer happiness, but has also resulted in some tools which have proven to be more useful than expected. Of course we have backlogs, and our devs work 36h a week on that. For at least 4h, they must learn new things.