GameBoxed team has been talking for a while on what’s happening on our tech side.
Our fellows and me are sharing this experience to other communities.
Through last few months we’ve been talking to various communities:
- Java devs via Confitura, Polish dev conference by devs for devs
- SRUG (Silesian Ruby Users Group)
- Eurucamp SPA workshop
- and of course DRUG .. Most promiment Ruby User Group in whole PL
We do have a bit of experience doing software for customers. We did it in Java when it was still cool.
We did Python too.
Last few years we’ve focused on Rails. A funny & not well known fact is our team members talked to DHH way before he became a celebrity, in times where on JAOO he had just a few of listeners. How funny – later – all major platforms & frameworks were cloning the Rails style.
What is GameBoxed style and how it’s unique?
It’s a mix of few more-or-less known approaches in software and organization style that leads us to develop better software and have fun at the end of the day.
- being domain driven and focusing on it first
- having elegant code, separating layers, code being more readable
- writing down business logic and rules in usecases
- having working app prototypes early, to demonstrate and validate it ASAP
- knowing backend is important, but leaving it as the last puzzle
- responsive app through the use of Single Page App in the browser
- having distributed team, so we can have best people we can
- delivering in agile manner – more kanban and programmer’s anarchy way – to provide more scalable and maintainable products
- and last but not least.. doing Gaaaamezzz, maybe not hardcore ones yet, but still fun enough :)
I will elaborate on few of those topics in the following mini series. So, today introducing on why important backend is left as the last one