Blog

/Blog
Blog2019-03-22T13:28:48+03:00

December 2018

Rewriting a Perl legacy application

December 19th, 2018|Categories: Perl|Tags: , , , , , , , , , , |

Our Perl division has worked on several large scale Perl projects over the years, each with its own set of challenges. However, in almost every case, there was a common denominator, the fact that they were under one form or another of legacy status. This article is about how we tackled one of those projects and rewrote a Perl legacy system in modern Perl. The decision to rewrite it was taken after client consultation and taking into account the current state of the system and the desired state of the system. Refactoring it completely was not an option as

Evozon Featured in The Clutch 1000 as a Top Software Company

December 11th, 2018|Categories: Company News|Tags: , , , , , , , , , , , , , |

a Recently, Clutch unveiled their annual leader’s list and for the first time ever announced The Clutch 1000. We are happy to announce that we made the Clutch 1000 – a list of the top agencies, software, web and mobile app development companies. We not only made The Clutch 1000, but were also recognized the top software development company in Romania in June. This year, we were was also named one of the top Managed IT service providers on their sister website, The Manifest - a platform dedicated to helping business buyers find the best service providers by providing

November 2018

Tackling Legacy Projects: an Experience in Perl – Free Ebook

November 22nd, 2018|Categories: Perl, Perl Case Studies|Tags: , , , , , |

There are several definitions for legacy code that have similar points, but overall people interpret the notion in different ways. For some it’s code without unit tests, for others it’s old code, for most it’s both. It’s not necessarily something vigorously debated, but opinions differ on what makes code legacy. In this short ebook you’ll find more than just definitions, but a different perspective on legacy code in general and what it represents for Perl. To make things a bit clearer, the ebook also contains one of our experiences with a Perl legacy code project and the challenges that

A Project Template For Getting Started With Django And Docker

November 7th, 2018|Categories: Python|Tags: , , , , |

If you’re working on a Python application in Django and you’re wondering how can Docker make your life a bit easier, then you’ve come to the right place. Given Docker's omnipresence across various operating systems it's crazy not to use something that gives you a consistent development and deployment experience. The old days of wondering why it works or doesn't work just on your machine should be gone. Ever heard this in your office? "just recreate the virtualenv" "it works on my machine" "can't run the project on my " "the project broke my computer" Docker is a fast

September 2018

Women in Tech Cluj on Mentorship: A Meetup

September 7th, 2018|Categories: Community|Tags: , , , , , |

Ever heard about the women in tech movement around the world? It comes in different names and shapes, from Women in Tech to Women Who Code, and from Girls in Tech to Rails / Django / name-a-framework Girls. The purpose is pretty straightforward: get more women to code and, generally, get them into tech. Their aim is to create a safe space where women can share, learn, grow and support each other in matters of career, development, and so much more. Their first meetups rolled in, and, for their third event, they felt like Mentorship was a topic they

Efficient Code Review Process

September 4th, 2018|Categories: Guides, Technical|Tags: , , , , , , |

Code review is not a new topic, but is for sure one of the most overlooked activities in software development. As software developers we are a team of people that try to get stuff done, and the best teams that get stuff done have open, collaborative cultures based on feedback. For a well functioning team it’s vital that the feedback comes fast, because the cost of fixing a problem in code rises exponentially the further that problem goes undiscovered in the lifecycle of the software. It’s important that teams put in mechanisms to find the problems as early