Clean code lies at the heart of a software product's success. Check HeartBeat!

Let's dive into code

We are a software development studio
specialized in helping entrepreneur
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

Words we wrote

A new gem for Contentful

Our team was approached by Contentful and asked to develop a Ruby Gem for working with the Content Management API for them. We took up the challenge and soon after Tomek W. “Warkocz” and Piotr sat down with the Contentful team and defined the needs and requirements drafting up a plan for development.

hacklab.pl - a higher level of programming

Ladies and gentlemen hacklab has launched!

On Saturday, 26th July, hacklab.pl, our secret pet project was officially launched. It is a training course of Ruby on Rails, aiming at the people who already know something about Ruby and Rails but want to learn more so that they can become professional developers. It is not a short nor shallow course. It's going to last 3 months with meetings taking up full Saturday and Sunday, happening every other weekend. It will end with a hackathon where the students will have to demonstrate their newly acquired skills by producing a real app.

Garbage In, Garbage Out; Why Definition of Ready Matters

SCRUM is a flexible methodology where being ready is fundamental to succeed. The term ready was first coined by Ken Schwaber and Mike Beedle in their book on SCRUM. Only a ready user story can be taken into a sprint and worked on by the development team to become a part of the product increment.

If a user story lacks consistency, the GIGO principle will most probably will pull in and you will get a messy piece of work in the end, irrespective of how good your team is.