“Efficiency is doing better what is already being done.” (Peter F. Drucker)

În cadrul oricărei ramuri de management este întâlnită ideea de decizie eficace.

Pentru a fi un bun manager şi pentru a fi sigur că îţi conduci echipa în cele mai bune condiţii trebuie să nu mergi pe principiul că marile calitati de manager sunt înnăscute. Nu este suficient să fii inteligent, să fii informat şi să munceşti din greu pentru a avea un nivel de eficacitate. Eficacitatea se poate învăţa. Şi chiar aceasta este cheia dobândirii eficacităţii.

Pentru ca un lider/manager să fie eficace, trebuie doar să pună  în practică câteva “reguli” nescrise.

Just one simple "Google" search for the title of my article gives you the possibility to pick from thousands of opinions of hundreds of people. What does that mean? Well, for starters it means that people care an awful lot about better code writing technically speaking and also from the comprehensible point of view.

It means that people care a lot about the technical aspect of the code but they are also very interested in respecting certain standards that will ensure the code is comprehensible.

The main reason for making code look "pretty" is trying to understand it later in case you need to debug it, or more important, in case someone else needs to debug it, or, even more important (in my opinion) - you want to reuse the code.

But enough about that! Let's just see what could make our code look friendlier!

Innovations occur as a response to necessities. The need for security and certitude that what you’re doing is correct is also very important. That is why rules, norms and laws were invented and have to be followed in order to be sure of success. A sort of “legislation” is needed even in the creation department. When you need to be sure everything is understood well and problems caused by simple misunderstandings won’t occur, a methodology is required.

Over time there have been several attempts or versions of a methodology that works for any project, but the greatest issue of these methodologies is that they are not completely applicable for every project. In fact, this is not surprising, so all we had to do was to study very well the existing “laws”. What we discovered was Prince2. So after a good reading we grabbed all the available material and we molded it for our own needs.

Now the technical side of the project! This application had to answer to some important requirements: extended accessibility for anyone who needs to use it – therefore it had to be online, simple and efficient document management along the projects evolution, easy and safe document generating and, last but not least, creating pdf’s in order to further approval.

This project was a real challenge for us, “the parents of Methorator”, because we had skills in programming and in working with databases but our skills were lacking concerning PHP and Java Script – the programming languages that we needed for creating an online application. But after creating only a few web pages, the further development of the portal became natural and easy. Surely, we encountered a few problems during the weeks we spent in developing the portal. We would follow a certain path and later on we would discover that the solution was not perfect. Then we would rewind the situation and give it a wide discussion debating all points of view and then we found the way out of the problem. Several times I had the impression that we had to go through a maze in order to get the solution to a glorious end, but sometimes we chose the wrong path. What always worked in solving our problems was gathering the whole team for a debate and a brainstorm.

With a high level of usability in generating and managing a project’s specifications, managing a project’s human resources that can have access to creating, editing or approving these docs, Methorator helps out the project manager in monitoring his project and taking the right decisions. He defines the project on the portal, attaches the companies that are involved in it – the customer and the supplier, and then invites the participants – the human resources. Methodology intervenes from the very step of creating the project: the project’s default stages are added, they contain the default documents with the default titles. These default assets are mandatory for a good development of the project.

I send my thanks to all my colleagues for an excellent cooperation!

We invite you to follow our updates for further updates about the platform’s launch date.