One more year code motion 2016 has brought us together in Madrid at the CEU University of Boadilla, on November 18 and 19. Like every year, there is always a main theme that covers the event, and this year they have been the containers. In addition, there have been talks on new concepts, how to manage the development of computer applications, architectures adapted to the times, consolidation of traditional languages and the presentation of other new topics that I will summarize in this article.
Codemotion it continues to be the best general information technology showcase, that is, it is the event in which more communities and disparity of talks can be found. This is because the rest of the events that take place in Spain are more focused on a technology and a technological profile. In fact, every year more companies in the sector try to be present in Codemotion, since the recruitment of new talents in this kind of events is gaining strength.
As always in Codemotion there are many themes that are recurring; For this reason, I recommend that you see both the articles and the agendas of previous years, since each year they place more emphasis on sharing the videos and presentations of the talks to, in this way, give vision to those who did not want or could not go .
Let's break down the talks this year in large groups:
Much has been said about docker containers, They are not the only ones, but they are the most used today. For those of you who have not heard of them (although I doubt it), this technology is here to stay and you will wonder why.
Containers, whether docker or of other types, they create a machine with the essentials to be able to start our applications or databases. This helps us to be able to lighten the creation of machines and not have to load, as is currently the case with virtual machines, with an excess of functionalities that do not add value to us. From these containers, other tools appear to manage them as it would be dockercompose, docker swarm, kubernetes and, surprisingly and with the possibility of mounting it for free on our machines, Microsoft Service Fabrick.
In this year's Codemotion, the most followed talks were those of kubernetes, which is a Google product and which the community follows the most, since it allows us to manage containers and, at the same time, balance and control them, streamlining management.
Containers were also given great importance for the ease of generating homogeneous development to production environments, avoiding the famous phrase 'it worked on my machine. ' And as they are light machines, also because of the speed and ease of creating, destroying them and having them only started when necessary.
How could it not be missing, and we already talked about it last year, here are the microservices. Today, almost all architectures try to create microservices or divide them as much as possible to avoid those monolithic projects that I like to call 'snowballs'. These balls start small but as time goes by and they progress, they include more functionalities, and what was an easy to maintain and well-documented project becomes crazy, with many fiddles and practically unmaintainable and difficult to refactor. Therefore, the world of software development is directed towards microservices, which are much more maintainable and easy to refactor and replace.
But of course, not everything is a world of roses, so I think I'd better tell you about it, I'll leave you an example:
PHILOSOPHY OF THE SOFTWARE WORLD
Not everything is technology and software at Codemotion. There is always a section to reflect on the importance of things and a job well done.
For example, on the one hand, reminding us developers and architects of the importance of databases (which we don't usually give it to), is this talk:
On the other hand, giving us an overview of the problems encountered by the developer in their day to day, and opening our eyes about it:
And finally, referring to the communication problems between the different participants in the development cycle (developer, director, client ...):
The world of developers has always been concerned with ensuring that their code works and is of quality. For this reason, Codemotion never leaves out application testing, whether unit, functional or navigation tests. Like other years, to simplify the use of JUnit, there are still talks of a great solution that is Spock (more information in the previous year's article). And, in the case of functional and navigation tests, there were talks on the use of robots and spiders, both to carry out tests and to create search engines, for example, for supermarket offers.
To end this article, I must indicate that Codemotion It has improved a lot from years prior to this one, taking into account the opinion of the audience and the communities, since this year the talks were chosen and valued by the communities themselves.
Although there are times when this could be dangerous, as it could provoke kingdoms of taifa, today we can be grateful that there are active and healthy communities. In addition, the stands are removed from the corridors passing them to the entrance and thus avoiding the traffic jams that arose when moving between rooms. More talks were also recorded and more uploaded slides than other years, although in my opinion you should try to reach 100% to give a complete vision of all. More workshop spaces were created for people who wanted more practice and less public speaking.
However, there will always be drawbacks, which should be used to improve, of course :-). From my point of view, the dinner of the guests of the talks and patrons was a bit uncontrolled, in the sense of not trying to generate interrelationships between the people attending. If you didn't know someone you were a little helpless. On the other hand, it would be good if the stands were at the entrance in a tent so as not to invade the venue and thus facilitate movement; but hey, as I said before, this year they have put a bit of a solution on it. Regarding the management of catering waste, I think it was a bit insufficient for the number of attendees but, yes, everything was clean from one day to the next.
The final reflection would be: yes to Codemotion to raise concerns about where the world of software development is navigating and to bring communities together in an event (which I am delighted to be able to attend and hope another year will be as a speaker). But, if you want to enjoy more complete talks and more specific topics, go to the talks of the communities and their meetups, since many of the talks that later go to Codemotion.
I leave you some references to communities and I hope you have enjoyed this article and try these meetups:
PS: We are waiting for you at the 101 Panel Tech Days: