Let's dive into code

We are a software development studio
specialized in helping entrepreneurs
turn ideas into awesome products.

Love & Passion

We work with the web, mobile and data


Don't be shy!
Ask us about


/Awesome Design & Elegant Code/

/iOS & Android

/Ruby on Rails/


code quest is small by size, but big by ideas. We love our job and develop soulful products that are a pleasure to use, distinctive, and reliable.

Development of quality web and mobile applications is our mission, at the same time strong background in machine learning algorithms is what makes us stand out from the crowd.

Play
See how we do what we do!
Don't take our word for it.
Check what other says.

The latest entries from captain’s log

All those words we wrote

Rails Girls Warsaw

Rails Girls workshops are coming to Warsaw again. They will be held in the beginning of February and have already received hundreds of applications. code quest is a part of the event and our own crew will be teaching the ladies how to enter the coding world...

6 reasons why startups should outsource development work

Startupers encounter many hidden obstacles on their way to producing their dream product. These include the technological drawbacks, such as founders coming from non-technical background, or having no technical knowledge; limited time resources (a one person can do only so much work in a given time, so if you focus on marketing, somebody else will have to do the team and product management); money matters (with limited financial resources you have to think twice and spend it wisely), and so on.

If you ever wondered why outsourcing development work is so popular among startups, we have compiled a simple checklist of the reasons for it.

Read our article to see the full list and the reasoning behind choosing offshore teams as your service providers.

Playing the Planning Poker. Is it worth it?

People suck at estimating things, especially when it comes to the time required to complete a task. And developers, who are people, in case you forgot, suck at estimating the time required to code a feature or the feature’s difficulty. We must be born optimists as we usually underestimate and very rarely overestimate, and we are so bad at estimating that in 1979 a new term was coined by Daniel Kahneman and Amos Tversky to describe this phenomenon. We all fall victims to the infamous Planning Fallacy.