Salut, eu sunt Alecs. Sunt un programator web stabilit in Hamburg.

Rapiditate

Prioritatea mea: incarcare rapida si optimizare a website-urilor.

Responsiv

Layout-urile mele vor functiona pe orice dispozitiv, mare sau mic.

Dinamic

Website-urile nu trebuie sa fie statice, imi place ca paginile sa prinda viata.

Cine sunt eu ?!

Programator web hamburg ghinea alecs

Ma numesc Alecs, sunt un programator web din Bucuresti, stabilit in Hamburg, cu o experienta de peste 8 ani in programare web.

Sunt un programator talentat si versatil, specializat in realizarea de website-uri si aplicatii personalizate.

 Hai sa facem lucruri interesante impreuna!

Cronologie

2019

August

  • Whow Games GmbH · Programator web

2017

March

  • Legal Tech Systems · Programator web

2016

April

  • Mylittlejob · Programator web

2015

November

  • About You · Programator web

2013

April

  • Wolters Kluwer Transport Services · Programator web

2011

November

  • End Soft Design · Programator web

Technologii

Sunt specializat in programarea web cu PHP7, Laravel / Lumen, MySql / MariaDB si JavaScript, mai ales cu REST JSON API standard. Cu toate acestea, am experienta si cu Vue.js, ReactJS, Responsive Design cu Bootstrap sau Flexbox, JQuery. Am creat mai multe aplicatii front-end (SPA) si am cunostinte de Zend Framework, Symfony / Silex Framework, Python, HTML5, CSS3, SASS, LESS si Wordpress.

  • PHP7
  • Laravel
  • Yii
  • Wordpress
  • Zend framework
  • Symfony framework
  • Python
  • MySql
  • MariaDB
  • PostgreSql
  • ArangoDB
  • Vus.js
  • React JS
  • Amazon Web Services
  • Nginx
  • Apache
  • HTML 5
  • Git
  • Redis
  • Sphinx

Clienti

B+R

Kehrwasser

Tillome

PerScience

Euro
metropola

Mustrategy

B-Ceed

Job Cops

Ultimele proiecte

PerScience

Una dintre cele mai importante companii de management si consultanta pentru cabinetele medicale si dentare din Germania.

Tillome

Utilizati social media intr-un mod mai inteligent! In calitate de creator de continut, va puteti arata prezenta on-line cu un singur profil. Ca utilizator privat puteti descoperi profiluri interesante, puteti cauta figuri publice, marci, companii locale sau influeceri. Cu o singura cautare, veti gasi toate canalele lor sociale, informatii de contact sau link-uri web. Mai simplu, va puteti consuma retelele sociale intr-un singur loc.

MyRight

Este un serviciu juridic care ajuta cumparatorii europeni in scandalul emisiilor masinilor diesel pentru a obtine o compensatie. Startup in zona LegalTech si primul initiator al unui proces colectiv in Europa.

Proiecte mai vechi

Testimoniale

I've worked with Mr.Ghinea in developing a website for the company I represent and he and his team proved to be great professionals, creative, focused on solution and extremely patient and comprehensive with clients that don't know the IT field very well. I truly recommend Mr Ghinea for developing a great website.

Raluca Pascu

Business Development Manager Romania
Marie Stopes International
I highly recommend Alecs as he is a very professional guy, with high commitment to work. A real pleasure to work with him, he understand very good business needs and make everything to meet business goals.

Ovidiu Sutac

Studio Director
I-Play

Blog

PSR-2 or how to be a better developer

15-04-2021 · in development

PSR-2 or how to be a better developer

In the PHP world the entire community was not so compact in the early days when it comes to the coding standards. The idea of having a coding standard is so hard to adopt to some of us and it is causing more trouble in the thinking process.
This is so evident when doing code reviews for example and can cause different useless talks inside the development team.

Advantages

PHP Standard Requirements (PSR) is the the go to point for any kind of PHP developer. From my experience I can say that adopting a code standard like PSR-2 comes with multiple benefits. I will try to list them here:

- software maintenance; this is the main point and the most important one. If you do a search you can find that from the cost perspective between 40 and 80 percent of the lifetime cost of a software goes into maintenance and also the fact the hardly any software is maintained its whole life by the author.

- code quality; software development work involves reading a lot of code. Either writing code or code review involves reading the code and this should not be perceived as something difficult to do or more beautifully said, as something annoying.

- keep it simple; the complexity of a code structure is fighting against security in most cases. If you try to minimize the amount of code written during the project development you will also write less (hidden) bugs

- refactoring; when renaming a variable, renaming a method or breaking code in smaller parts it is called refactoring. When the code looks clean and ordered then the refactoring process goes easy and well.

- code language; every developer should know English. All the documentations regarding parts of some software are in English. The guy coding after you knows also English so for all of the reasons above the code language is connected with the software maintenance process and is bringing a plus to the readability of the code.

PSR-2 conventions

The PSR-2 conventions make a lot of sense for me at least in overall code improvement.

Indenting

I read a lot of articles with talks about what is better, tab or spaces. For PSR-2 things are simple in my perspective: “Code MUST use an indent of 4 spaces, and MUST NOT use tabs for indenting.”.

Properties

Developers know that naming variables is the hardest thing to do so thinks like “Property names SHOULD NOT be prefixed with a single underscore to indicate protected or private visibility.” or like “Visibility MUST be declared on all properties.” are here to help.

Closures

“Closures MUST be declared with a space after the function keyword, and a space before and after the use keyword.” To check out all the conventions for the PSR-2 standard please visit this link

Tools

A great tool to have some automation in checking the code standards is PHP CodeSniffer. To install it you can do something like

	apt install php-codesniffer

or if you have PEAR installed

	pear install PHP_CodeSniffer

After installation you can use it from the console for example like this

	phpcs --standard=PSR2 src/

Or you can set up your IDE to automatically check the coding standard using the phpcs.

Go ahead and be a better PHP developer

A good developer should follow a code standard. I am standing up for PSR-2 here but what code standard you should use it is up to you. The important thing is to have one and follow it strictly.

If you are a business owner or project owner talk with your developers about coding standards.
If you are a developer adopt a coding standard.

source1 source2 source3

Older posts