How exactly are the meetings structured? I.e is someone leading discussions? Does each person go around and share thoughts? Etc
[1] https://people.freebsd.org/~lstewart/articles/cpumemory.pdf
I’ve lived with a celiac sufferer before and I’ve never heard of something that extreme, but everyone’s different.
The reaction was caused by the micro-brewery that had opened next door and all the wheat dust in the ventilation system.
https://en.wikipedia.org/wiki/Coeliac_disease#Dietary_challe...
No company I’ve worked at has ever had dedicated time for reading papers or articles
Maybe I’ve only worked at outliers?
We also often played board games. My favourite was playing secret Hitler with my team that one time. That was fun! (I managed to become "untouchable" while also being Hitler. That's a memorable moment!)
What I meant with "menial coding" is those jobs where people have to submit TPS reports on how much hours they spend for each customer. Reading a paper such as this one [1] is typically not directly necessary for being a good frontend developer, but it might stimulate someone to develop into a more fruitful employee in the long run. Managers would have to explain to their customer why time is being spent on that, and that requires some vision and creativity, which is not always a given.
One company had a +1 day. You worked 4 days, had 1 day for learning - everything relevant for the job was fine.
Even if you have enlightened technical management, it's helpful if you don't force them to spend political capital justifying groups like this. Getting our enlightened CTO to spend a few hundred dollars on books was easy when we were a startup. Once we got acquired, making that argument to unreceptive higher-ups wasn't worth it for anybody.
My team almost always can find an hour between tasks organically so I’ve never really had to push