You’re in for a technical interview. They ask you a question, and you have to build a system or to write some code, either on a whiteboard (brr!), on a piece of paper, or on a laptop at home. And then you discuss it with the interviewer.
Some enjoy it, and some dread it. But if you are going through it, it means the end of the process is near! And you really want to show the best side of yourself.
I led more than 120 interviews. Here are some common mistakes I noticed the candidates make.
Continue reading “11 Mistakes To Avoid On A Technical Interview”
What’s common between software and opera houses? Building of both often goes overtime. Read on to know why and what should you do about it, as a client or as a developer.
Many software projects go overtime. Software developers get blamed for that, laughed at, scorned at.
But guess what: it’s not only software developers.
Many building projects also go overtime, and most noticeably of all, perhaps, opera houses and concert halls.
Continue reading “What’s Common Between Opera Houses And Software Projects, or 10 Reasons Software Developers Go Overtime”
You know how the software developers are always mocked because they don’t comply with the time limits? Read this article about my experience of hiring a team of freelancers who went way over the deadline.
Not so long ago I hired a team of freelancers to work on a project of mine.
Everything started as it usually starts. I found several teams, some through friends and some – through a website. I met with team leaders, we discussed my requirements, we agreed on time and on a budget. I picked the team that looked the most reliable to me, they rolled up their sleeves and started to work.
Continue reading “How I Hired Freelancers Who Went Way Over The Deadline”
How to make the roads better?
What about roads on a map?
Read to learn what graph (and non-graph) algorithms we implemented to make the roads good.
One particularly nasty and cold day, in the middle of February, our users, cartographers, came to visit us, developers. And they looked worried.
We offered them hot tea and chocolate candy. By gentle nudging and careful questioning we managed to understand what was bothering them.
They wanted the roads to be good.
Continue reading “How we checked road graph correctness”
When I read an article or a book about architecture, framework, approach, or tool – I focus on “why” it was built or applied one way or another. Not “what” they did, not “how exactly” they applied it – but “why”. Read here to know “why” I think it’s important.
What interests you when you read an article or a book about an architecture of some big system, or about new frameworks, or design patterns, or some new fancy tools?
To me, the most interesting thing is why they did it like they describe.
Continue reading “The most interesting thing is “why”, not “what””
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”