Ovidiu Mățan : Dennis, the local team has grown a lot since you came to Cluj for the first time, offices changed and new projects came. Tell us a few things about your journey and why it was special.

Dennis Raabe: It was a special journey, indeed. Besides the many successful projects delivered, the growth of the ECC team from around 40 associated to more than 800 today, what always impressed me most, was the passion and commitment of this young team. From the very first day, I knew that their special drive to show what they are capable of and 'the yes we can' attitude will help us achieve great things together.

This journey began two years ago, and many changes were made until we get where we are today with our bug bounty. In this article we share general knowledge on bug bounty programs and our personal experience on launching and maintaining a program.

Published in Issue 96 Read more

One of the first decisions most projects face, regardless of the development landscape or technology, is "Which development methodology should be used? What fits better for our application and landscape?" This topic gets more and more attention and it's currently a subject of debate. There are many articles debating if the developers creativity is not restricted by adopting standard steps to be followed. This comes up as since the chosen methodology determines how the project's development is organized. The two most known methodologies are Waterfall and Agile. Although SAP has ASAP for ERP implementation, in SAP software development Waterfall and Agile are both famous. The article will draw some ideas around the way of choosing the best fit for the developed software in SAP world.

SAP Solution Manager is an application lifecycle management (ALM) platform provided by SAP, which helps you implement, maintain, run, and adopt all enterprise applications - even non-SAP software - while supporting business innovation, business continuity, and operations.

We are not living in the Stone Age any more, we are social human beings and we should be also social engineers. It was long time ago when a project was a one-man show, so we have to learn to collaborate, we have to learn how to work in mixed-skills teams and how to share ideas and solutions in order to have a successful life as code writers. According to Tudor Girba1, as developers we spend about half of our working time reading code. Why reading code? Because the current code bases are growing every day, and with each task we have to implement,we will end up reading code more than actually writing it.

There are 4.77 billion mobile phone users spread all over the world. They can choose between 2.8 million apps on the Android platform and over 2.2 million on Apple's App Store. Mobile phones are used in schools, on the streets, in the buses, inside personal cars, everywhere. The statistics confirm that it's a real challenge to deal with the mobile device diversity. The app should work and look good on all devices, regardless of their size, orientation or capabilities. Currently, the most popular screen size is 5.4 inches (i.e. iPhone 6) because it was rated as the best size that fits the human hand. Recent studies show that most users hold their phones with one hand and that they prefer portrait mode. However, they often rotate their devices from ergonomic reasons.

Besides the official Docker documentation, there are several good sources on the Internet where you can read about how to kick-start your dockerized environment on your project, including Stack Overflow Docker tag, official Docker images for MySQL, and Postgres. Unfortunately, there aren't so many places where one can read about the failures in setting up Docker in various common use cases. You may wonder "why would anyone be interested in such a thing?" I think the value of such stories lies in the fact that we discover how such solutions work by trial and error, many times - pretty much the same method applied by a 2nd grader. Do you find yourself in a similar situation? You probably do, so the ideas from here will bear some value to you.

The artificial intelligence field is strongly connected with Big Data technologies. One of its areas deals with the study of natural language. Computers can be taught to recognize certain patterns in the processed texts and, based on them, they can automatically classify sentences, phrases or even full documents in predefined groups. Using open source instruments, one can easily configure such a project, capable of classifying text, based on a prior automatic learning phase, using a preset input data.

The brisk rise of modern social media led to the development of tracking tools, which have as unique purpose the monitoring of the written content published on social networks sites. These software products become inefficient when they are applied on tasks which are rich in visual content, with too little or inconsequential written information.

It's time to be honest with ourselves and admit that we do not treat our frontend code the same way we treat our backend code, and this shows. When we talk about our code, we talk about applying the rules of clean code, about keeping it simple, about writing unit tests. Yet, when it comes to writing our frontend code, we knowingly skip all those rules that we usually self-impose.