Probably the most painful thing for software developers is to be restricted in technology choice which they want to use in a development. You pay for a conference ticket, listen about new cool frameworks, development approaches or tools... Then you return to office with huge enthusiasm and desire to try at least something on real project. Unfortunately such initiative very frequently meets resistance from different sides: team members don't want to learn something new, a manager thinks it is risky, a product owner hurries with a next release, etc.
JVM is too small for two leaders. That’s how I want to start a post about Java vs Scala. By the way, I had used Java for a long time, but then switched to Scala and wasn’t happy with that decision. Luckily I have understood how to use its features in order to be more productive developer. Make yourself comfortable, it's going to be a very interesting conversation about marketing in a programming languages world. Yes-yes, exactly conversation, because I encourage my readers to write comments with their thoughts about the topic.
Hello again! In the previous blog post I explained TDD theory in general, without close reference to Java, but in this part we start a TDD practice. Our goal is to go through all phases of TDD: from requirement analysis to refactoring of tested code. All this we will do on example with Java, JUnit and 'fake' requirements.
Welcome to an introduction in Test Driven Development (TDD) series. We will talk about Java and JUnit in a context of TDD, but these are just tools. The main aim of the article is to give you a comprehensive understanding of TDD regardless of programming language and testing framework.
Finally I write to my blog. I'm so excited, because more then 6 months I haven't wrote here. I do not want to make excuses, since I worked on another projects and now I'm ready to present them. If you are belong to 10 000 of my regular readers you definitely know that my blog is an educational in general. And I'm really glad to announce my new direction of development - e-learning.
This article will be about State design pattern. It is one of behavioral design patterns. You don't need to know many theory to understand the main concepts of the pattern. The post will be break in several parts where I will provide information about situations where the pattern need to be applied, cons and pros which it has and an example of usage.
This time I want to talk about Strategy design pattern. In this way I start articles about behavioral design patterns. These kind of patterns represent some schemas of interaction between objects to make a code more flexible and well organized.The most essential point of this approach is loose coupling between objects.
The one of creational design patterns is a Prototype design pattern. Despite that the Prototype is the creational pattern it distinguishes from other patterns by a concept. I mean that the Prototype in some sense creates itself. I'm going to explain it bellow. All magic of the Prototype pattern is based on a clone() method of a java Object. So…