tobyc
We're a digital consultancy and agency who build products for late stage startups, government agencies and financial companies.
We're in the need of full stack Rails and React Native developers.
We work on some pretty interesting projects and have a pretty great culture. We're remote, but we catch up in tropical locations as often as we can.
Email me your details: [email protected] Thanks!
If an early stage team is building a massively complex microservices based product, using a new type of database and deploying it via kubernetes — where a Rails CRUD app on Heroku would easily satisfy requirements for years. Then someone seriously needs to ask the question as to whether using bleeding edge tech is necessary, and whether it will impact the ability to iterate and hire.
Ambie (http://ambie.fm) is effortless music management for brands and spaces. We're a quick growing startup providing 24-7 streaming music to businesses across the world. We've just come out of the Techstars London Autumn program.
Our customers love us, and we want to keep it that way, so we need someone who always puts the customer first and who is a good communicator.
We have a fully functioning product, but there is a lot for us to do in order for us to keep up with our rate of growth.
As one of the early Ambie team members, you'll have to be comfortable with uncertainty. But you'll be having a massive impact, and will get to hear from satisfied customers all the time.
Our stack is primarily Django with a backbone front end. But we're evolving rapidly — so things will change. We're moving towards React for our front end, and technology for our back end is up for debate.
- The pay is competitive. - The environment is fun, flexible and interesting. - You'll have definite impact.
Send through your details to [email protected]
5:15 Wake up
5:17 Brush teeth
5:20 Put on workout gear
5:22 Walk 200 meters down the road to Crossfit
5:30-6:15 Crossfit
Works pretty damn well.
I think the difference between a fast programmer and a slow programmer often isn't that the slow one is methodically designing and making everything perfect, it's that the slow one has so many more inefficiencies in their workflow.
A good and fast programmer generally knows their tools inside and out, and they're willing to learn new tools when they need to (and not dismiss them because their current setup works good enough and it's what they know).
Speed isn't an indicator of good or bad quality. I would say that both mastery and improvement of tool is more of an indicator.