By Matias Herranz
While collaborating with several projects, I noticed issues when generating and setting up the public keys as well as configuring the access to GIT repositories. These usually gives people a bit of a harsh time.
By Miguel Balparda, Magento Developer at Santex
Today I will be developing some concepts and ideas regarding the architecture of Magento and its components.
On occasion everyone takes the skill of producing and delivering superior code for granted. With that said, after many internal discussions we at Santex have come up with a quick list of items to support in everyone’s success in the matter.
- Ask questions (not doubts) and never make assumptions!
- There is no substitute for long term hands on (real world) experience because school only works as a good introduction.
- The more you care about your work and the result of it, the better results you will get from your work.
- Always Google (in English on the .com site) for a solution because you are not alone in the world and someone else has come across a similar issue before.
- Think about the entire picture/project and not just your assigned tasks. Having blinders on will cause your tasks to not integrate as well with everything else and perhaps cause extra work to be done later.
- Test your own work a couple times in more browsers than you think the client will use before you say it is done and working.
- Read the requirements before you start your work, read them during development and read them at the end of your tasks to confirm it is correct.
- Use source control and make backups as often as possible.
- Use only one testing instance. More than this wastes space on drives, time figuring out which is correct, time creating/editing/deleting all of them and it creates a nightmare when some have only parts of the system implemented.
- Write your code in English, include comments in English throughout your code, declare every variable and reuse code throughout a project to make things more slim and clean.
- Never write code or do work that you know will need to be eliminated later. Do it right this time as it saves headache and heartache for everyone involved.
- Make sure your and the testing environment are setup to work as close as they can be to the live environment. (in US English and the same versions of Apache, IIS, MySQL, PHP, OpenOffice, ImageMagik, PEAR, SWFTools and so on…)
- Never hack the core or modules from a CMS or Framework for any reason.
If you have any feedback feel free to post it in the comments section below.