Feedback driven development

All modern software development methodologies are focused on increasing the feedback and taking advantage of it. One of the fundamental assumptions is that trying something out (getting feedback) is more valuable than the cost of doing it wrong. This works fairly well if we are getting quick and reliable feedback. However, does this equation still apply if we are not getting timely/quality feedback?

Continue reading


Implementing uniqueness validation in JPA

One of the typical things one often needs is uniqueness validation across Entities. For example making sure that each user account has unique username. Implementing this check is somewhat complicated in JPA/Hibernate because they will send pending changes in current Unit of Work (EntityManager, Session) to database before executing any queries against same Entity.
Continue reading

One team – one language

In many multicultural teams it happens that people start talking to each other using their native language. Main problem is that this way we effectively cut off those in the team who do not understand given language. This essentially means that osmotic communication doesn’t work. If topic is discussed in a language that everybody understands then everyone has a chance to join conversation even if he/she was not addressed when discussion was started. However, if non-common language is used then there is high risk that full potential of the team is not used when decisions are made.
Continue reading