Great on the surface. Not entirely sure about the happiness metric.
Pros
- The tech stack, working with Go, NATs and Cockroach on CQRS - Pair programming - helps with remote only role on top of other obvious benefits - Retrospectives and demos of work just completed to own team - Challenges in the scale of moving to a multi-cloud agnostic solution
Cons
- The relationship between business/product and engineering is not very strong. - Lacks top-down design thinking. Could be a team thing but in that team it was very much lets have a brainstorm and then code - No documentation on the business problems being worked on, no doubt contributes to a lack of high level design. Also, no or little documentation on technical solutions that have been agreed upon and such as new architectural implementations or generally on how things work. - Pair programming. It's almost 100% of the time which is good when you start but you can't stop the flow of work to ask every question you need to ask about how something works. Therefore, you need to do a lot of learning outside work. - Culture might not be for everyone
