3 ms·
The funny thing is that I remember doing exactly this with PHP in the early 2000’s on a small team. We didn’t even have version control on the project and just
by brightball 6y ago
The funny thing is that I remember doing exactly this with PHP in the early 2000’s on a small team. We didn’t even have version control on the project and just did all of the development in vim, relying on its lock files to ensure we didn’t edit the same files at the same time. Deployed changes with rsync.
That project ran in an enterprise environment, customer facing for 10 years with almost no maintenance.
- damagednoob 6y ago> for 10 years with almost no maintenance. 10 years is a long time in security. Presumably that's what the maintenance was for?
- mrmonkeyman 6y ago"What a nice house! Big rooms, nice view. Very little maintenance." "Nah, the lock is 10 years old. Any thief worth his salt can break it nowadays. The entire house is worthless I say, worthless. Burn it! Burn it now! It is a danger to society if you let it stand." This is totally reasonable and normal.
- brightball 6y agoYep. It was also a project where we rolled our own...everything. This was an AJAX project before Prototype, jQuery or even JSON was popular so we had a lot of explicitly mapped paths and code that only didn’t exactly what was needed and verified every argument.