Twelve Mistakes in Agile Manifesto

  • 1698 words
  • 7 minutes to read
  • comments

Nowadays, Agile Manifesto is a Bible of numerous software teams. It contains 12 principles which show us how software development should be organized. These principles were invented in 2001. Generally, I like and agree with all of them. However, in practice, most software teams misunderstand them. Consequently, here is a summary of what's going on and my interpretation of each principle.

Key Roles in a Software Project

  • 308 words
  • two minutes to read
  • comments

I believe that several roles should be present in a majority of software projects. Managed by Teamed.io according to the principles of XDSD, we've got all of them in our projects. However, beware that in other management methodologies, these roles may have different meanings. This blog post is mostly for people who work with us, either as clients or freelancers.

Data Transfer Object Is a Shame

  • 488 words
  • two minutes to read
  • comments

DTO, as far as I understand it, is a cornerstone of the ORM design pattern, which I simply "adore". But let's skip to the point: DTO is just a shame, and the man who invented it is just wrong. There is no excuse for what he has done.

Singletons Must Die

  • 449 words
  • two minutes to read
  • comments

I think it's too obvious to say that a singleton is an anti-pattern as there are tons of articles about that (singleton being an anti-pattern). However, more often than not, the question is how to define global things without a singleton; and the answer to that is not obvious for many of us. There are several examples: a database connection pool, a repository, a configuration map, etc. They all naturally seem to be "global"; but what do we do with them?

How to Hire a Programmer

  • 1163 words
  • five minutes to read
  • comments

I get asked this question very often: Where and how do you find and hire a good programmer? Since I'm a programmer and I manage software projects, I'm supposed to know the tricks. I do, of course; there are many of them, but the list below succinctly summarizes the most important ones.

Don't Use Java Assertions

  • 240 words
  • a minute to read
  • comments

There are basically two ways to validate a situation in Java and complain when something unexpected happens. It's either an exception or an assertion. Technically, they are almost the same, but there are some small differences. I believe that exceptions are the right way to go in all situations and assertions should never be used. Here's why.

11 Mistakes Conferences Keep Making

  • 1404 words
  • 6 minutes to read
  • comments

I was talking yesterday with a few friends who were software conference organizers. They were asking about my opinion of the conferences I've recently attended. Basically, they were interested to know what I would suggest for improvement. So, I decided to summarize it in a list of the most typical mistakes all conferences keep making and give them some ideas. Remember, I'm judging from a speaker's position. The most serious mistakes and pieces of advice are at the bottom.

Who Is a Project Manager?

  • 1996 words
  • 8 minutes to read
  • comments

A project manager is very often confused with a leader. However, they are two very different things. A project manager is the one who predicts the future, while a leader is the one who builds it. And, in my opinion, a perfect project manager is much more valuable for a project than a leader. If a leader is valuable at all...

What to Worry About in Convertible Notes

  • 2086 words
  • 8 minutes to read
  • comments

"Convertible Notes" is what you most likely will hear the first time you get money for your first startup. They will give you cash asking to give them the convertible notes (or SAFE, which is very similar). Convertible notes are just a few pages of paper with two signatures at the bottom. Not too much to worry about. It's basically a contract between your startup and an investor. Let's see what exactly it says and what you, as a founder, should pay attention to.

Keynote Clowns

  • 660 words
  • three minutes to read
  • comments

Over the last six months, I've attended 18 conferences and heard over 30 keynote sessions, mostly about software development and management. I think I now know all the secrets of a successful keynote speaker. It doesn't look so difficult to become one. Here are my thoughts.