Pros
- Training - Conferences, if you want to go to them - Pleasant developers, albeit mostly young
Cons
Culture -------- Previously a ThoughtWorks project, the ThoughtWorkers had with them a very team-oriented culture, with frequent lunch outings, game nights, and were very knowledgeable about the product and their areas of expertise. Likely due to costs, Amplify decided to end its contract with TW and began filling its ranks with full-timers. As the ThoughtWorkers left, the hangouts and great culture, of wanting to stay late and write code, just seemed to evaporate. Perhaps management thought they were the cultural leaders, but clearly could have studied up on the ThoughtWorker's culture and better attempted to continue it after their leave. Management also seems to know best. Tech leads will tell you how you're going to solve a problem, everything from technology to use to patterns. They seem to leave no decisions to the developer, and no job but to write the code. Frequent "retros", though the feedback often goes unused. The technology department seems somewhat too insulated from the rest of the company. Space ------- The open work area is incredibly noisy. The best way to get work done is to stay home. The build pipeline and systems resources ------------------------------------------------ The build pipeline is always broken, meaning you spend lots of time figuring out why. Trying to work with the systems team is like pulling teeth because there's always a fire to be put out. Vision ------- Short term, shifts weekly.