5 ms·
Think about how demoralizing it must be to work on that project. Especially if you're a new person and all full of hopes and ambition. You end up stuck on a de
by reaperducer 9y ago
Think about how demoralizing it must be to work on that project. Especially if you're a new person and all full of hopes and ambition. You end up stuck on a dead-end project that was designed to fail, and it doesn't matter how hard you work, it is bound for the roundfile.
- camtarn 9y agoBeen there, done that - twice. Amazon has a tendency to spin up internal startup-like groups to try out a bunch of fairly random ideas and see which ones stick. As an example, I worked in one team whose brief was literally just "We want another IMDB to sell ads on, but for a different vertical. You pick." - we created a user-generated music encyclopedia because it seemed like a good idea at the time. It sank without trace after three-four years of almost-zero usage - although we did have a few fanatical users who submitted literally hundreds of thousands of edits. It was ... odd. It really is demoralizing to work on a team which is started to pursue a dubious idea with no market. You have to go in each day and ignore the nagging doubts that tell you that in two years, the team will dissolve and you'll be onto a different project. The only thing that keeps you going is that the tech is usually interesting and fun to work with, and occasionally a team can pivot onto a different idea. The aforementioned team spun off a separate team focused on getting artists to pay to customize their Amazon pages, a bit like IMDb Pro. A different team building a (doomed) external tool inspired a colleague to start a micro-team and build what became a well-loved internal content creation tool. On the other hand - while the environment isn't great for doing startup-like teams (twitchy lawyers, bureaucracy, lack of external interest because you're just another Amazon product instead of a shiny new startup), when the product fails you ultimately still have a job.
- Twirrim 9y agoSeems ideal in some regards. Problems to solve, and opportunities to learn, and if it all falls apart you're just moving on to another new problem to solve.
- camtarn 9y agoIndeed. I had a lot of fun working on some of this stuff. Just gotta ignore that nagging doubt that it's all pointless. At least I could console myself with the thought that, while I probably wasn't going to make a difference to the world, I wasn't going to harm it. The more conscientious of my colleagues over in the advertising teams didn't have that comfort...
- jordan801 9y agoI am currently doing that. It sucks, but it pays the bills.
- ekovarski 9y agoBut isn't this going to eventually gnaw at you? Nobody wants to be relegated to a zombie employee status just to maintain the status quo on a project. Folks like to be challenged as this is ultimately how you grow.... my 0.2c
- camtarn 9y agoThe dead-end projects can still be interesting and challenging, and you can learn a lot from them if you're just treating them as personal development. My first involved preparing a user-generated-content website to scale to 200 hits/second. The second saw us attempting to squeeze an HTML animatic editor (like storyboards, but with music and audio) onto a 7" tablet with severely limited memory and CPU. Of course, as I mentioned above - sometimes just "this is gonna make me a better developer" doesn't quite cut it for two-three years. It's easier to find motivation if something is a challenge and you reckon it's got even a slim chance of making a difference in the real world.
- heavenlyblue 9y agoDevelopers tend to forget that technical solution is only a part of the problem. Projects that don't have a market tend to have less politics since no one really gives a single one, so you definitely miss at least on this; or the actual skills of massaging the product into user acceptance (since you don't really have any true users).