At Peak Games, one of the most important development practices is Code Review.
We believe that, with Code Review we have
In this presentation
"Is Kanban an Agile Method?" is a perennial question that comes up in our training classes. Who cares whether Kanban is Agile or not? It shouldn't matter. What should matter is whether Kanban helps business improve their capabilities and customer satisfaction? Whether Kanban improves the economic and sociological outcomes for those adopting it? Timeboxed increments are actually not described in the Agile Manifesto but they were core to almost all first generation Agile methods. We prefer to position Kanban as "an alternative path to agility.". Learn more in that session
Having a layered architecture brings some benefits to software development. Some of them are;
It is a very common practice to employ classical three tier layered architecture to separate UI, business and data access parts from each other. However, in order to achieve those benefits listed previously, we need to create some other architecture on top of that layered architecture to handle functional aspects which are usually cross-cutting those three layers.
It is possible to create such an architecture which provides a basis to obtain those benefits by employing model-view-presenter (MVP), observer and mediator patterns together. Indeed, some frameworks, such as Vaadin UI Framework, Spring Application Framework, Hibernate Persistence Framework, provide means to easily realize such an architecture in our enterprise projects.
MVP helps us to separate handling backend logic from UI rendering completely. Any UI event, such as button click, list select etc, is immediately translated into a corresponding business event, and is let to be circulated among other components via Observer and Mediator patterns. Those other components are able to handle business events that they are interested in, execute their functionalities, publish new business events, update UI and so on. Components are totally unaware of each other. They can be introduced into the system optionally, and even at run time. As a result, it becomes possible to achieve modularity and reuse both on micro and macro level in our enterprise applications.
From JavaSpaces, JINI and GigaSpaces to SpringBoot, Akka and meteor.js .The talk will give an overview of Javaspaces with a short comparison with the latest trends of Akka, Spring Boot, Spring Cloud, Meteor JS and Netflix components.
Will cover some of the major pitfalls when creating reactive applications as well as the added complexity that might come with these applications. Best practices when building micro-services and how not to fall in some of the traps out there.
Let me guess what you think. You think you are smart, you think you do a good job and you think you really love software development. You think you can program 24 hours a day if you are able to do so. You also think that software development is a profession and you are a member of such a huge great community. You feel proud of what you are belonging to. At this point I am sure that only a very few of you do your profession under the lights of ethics in software development. As in every professions, software development has a common set of ethical values, behaviors and rules. That might be the most forgotten and abandoned area in our profession and my main goal is to trespass it in this session.
