5 ms·
i started at a company as engineer #1 and my first task was to take an outsourced MVP built on heroku, port it from ruby to python, and make it work on aws. th
by 2c2c2c 4y ago
i started at a company as engineer #1 and my first task was to take an outsourced MVP built on heroku, port it from ruby to python, and make it work on aws.
there was seemingly no logical reason to do any of this-- the product was at an early stage with nearly no traffic. even if the product were to become immensely successful, the traffic would probably never require more than a single box.
but none of this seemed to matter. nor did the considerable amount of time making things just work. the ceo, who was at one point a technical engineer mind you, just wanted to be able to say his stuff ran on aws
situations like this are probably more common than you would think. it's purely a brand recognition thing for them
- barbecue_sauce 4y agoYou can't run Ruby on AWS?
- 2c2c2c 4y agoceo did not like ruby. neither did I! I only ever worked with it for the port.
- barbecue_sauce 4y agoI, too, do not like Ruby.
- avodonosov 4y agoAs the engineer #1 did you have any equity? If yes, was it OK for you to work on an unreasonable task? Was the company successful after all?
- 2c2c2c 4y agoYes I had equity. I'm fine working on unreasonable things to an extent. On the one hand in an early startup you have a lot of input on how things should work. On the other it can be hard to push hard against an owner's idea when you're in no position of power The company was acquired at an early stage by another private company.