1. If your contract allows it (and it should), get more involved in public dev community. Your employer benefits greatly from making a small closed source core product, with a giant open source ecosystem around it. Write public articles. Working in a community larger than one single business is fun.

2. Start a company coding club, a "labs" division, work in a slightly more exotic language. Great if your employer gives you time, but using some of your own is worth it too. Work on non critical tools, creative experiments. Sometimes you stumble onto incredibly valuable ideas which would never have popped up if you had strictly followed stakeholder requirements.

3. Listen to your body. If you feel restless, go for a run. If you feel tired, take a nap. If you're stuck, wander around the company. If you feel down, go find a place with more than a dozen trees. And always have a notepad nearby for doodling!

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.

@bittersweet can I work for you?

the duties of modern corporate secretaries include the appointment of responsible and competent persons in many areas of knowledge. As a rule, they include graduates of legal or accounting courses who are able to adapt to new standards https://mediaonemarketing.com.sg/co... . At the same time, you need to keep your finger on the pulse of corporate governance and remain an excellent communicator between different social cohorts.

Interesting advice, thanks. I think they are not suitable for every team, because usually the Product owner manages the process according to its plan. I'd like to add that the main thing to remember is that effective management is about creating conditions, and not constantly interfering with operational activities. I highly recommend the Trello service. Connect the whole team and cut tasks on the virtual board. At every moment you see what and where is. And who does what. In general, everyone can see. I also advise you to look on Facebook for posts of successful product managers who share the secrets of organizing an exciting development process. I found there about two dozen posts on this topic and noticed that most often these posts had more than 35 thousand likes! I'm sure this is because their authors used the help of https://soclikes.com/ to get likes.