Transitioning to a Real Dev Team

You mean real humans will use this thing I’m building?

Got your schema wrong? Just drop your database and try again. Not sure whether you have your asset pipeline set up properly to render the same way in production as development? Push it up, find out.

Feeling like an imposter is still a thing.

This was a thing at Turing, but part of me wondered whether I didn’t feel like a real dev because I wasn’t one. Now I am one, but I don’t always feel it.


We worked 60–80 hour weeks at Turing. We worked weekends. Always, we were working. People warned me that the startup life was intense, that it involved long hours too. Every startup is different I’m sure, but I’ve not found this to be the case so far. We work hard; we have deadlines and are expected to meet them. We don’t have the beer-and-ping-pong culture that some startups do (part of why I chose the company I did, though that’s a different conversation), but a lunchtime game of Bananagrams is not uncommon. Quick iteration matters; there is simultaneously an emphasis on doing things well over doing things quickly.


This is one of my favorite things. I no longer have to make decisions about what to work on next or what the feature or bug I’m working on should look like. We have a Product Manager who works with our Customer Success team and the CTO to prioritize and frame the work. When I finish one thing, I go to the “Ready” column of our kanban board and grab the next one. This means I spend all of my time focusing on the parts I like best — the code. It’s great.



Senior Software Engineer |

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store