risedesk ergo chair and autonomus chair. 

Ikea dining chair is also not bad :D

Mid-Level Software Engineer at Other

Bikram Kashyap

I would personally go with project Hero, but with a few caveats/prework. 

- Have a good conflict resolution mechanism. Make sure all decisions are data driven, disagree and commit where not enough data, but call out all the risks. 
- Figure out how not to get into crunch mode for more than a month. This can involve setting up mechanisms to speed up the team's work. 
- Read books/learn what is needed. Look at it from a learner perspective, and make sure the team also learns fast. 
- Ensure management has visibility into all your contributions.  

Look at google's internal mentorship platform too.

### TLDR Version

Find some guiding principles and how to balance them.

Also remember, the more experience you get the more you can think of simplifying the process.

### Slightly longer version

Something that can help for small wins are:

1. Learn your style guide
2. Use linters and other code analyzers, they will catch a lot of issues.

For more in-depth:

1. Find ways to reduce code complexity and coupling.
2. Read some books like pragmatic programmer and see how you can use the tips in your development.