Geo Information System: Architecture

Bad-ass development of scalable systems with lots of user requirements, tight schedules and limited resources? Ask me how!

This article is about our GIS-system architecture. Read on to learn how we dealt with all requirements!

I’m continuing the series of articles about developing a Geo Information System for 2GIS company.

In the first article I described the requirements we gathered. Now it’s time to talk about the implementation.

Continue reading “Geo Information System: Architecture”

Geo Information System: Requirements

Bad-ass development of scalable systems with lots of user requirements, tight schedules and limited resources? Ask me how!

This is the first article in series about building a Geo Information System. Here I’m going to tell you about user requirements we gathered before we rushed into development.

I’m starting a series of articles about building a geographic information system, or GIS-system. With a great team of smart and very dedicated developers, we created a robust scalable solution that our users were happy with. Or, almost happy. You can never make users completely happy. Sigh.

Continue reading “Geo Information System: Requirements”

Design your code for readability

So, how do you usually code?

You have a task: add this thing to that place. First thing you do – you find where “that place” is and how to get “this thing”. To do it, you read the code.
Reading happens every time you need to do something, doesn’t it? If something doesn’t work, or you need to optimize it, or add one more tiny thing, you search for the place in the code and read it again. And again.