The manifesto introduced 12 guiding principles around teamwork, leadership and customer satisfaction. But in 2001, a group of programmers came together to create the Manifesto for Agile Software Development, changing the way that applications were built. “Because there was often no test environment, developers relied on peer reviews before shipping the code and hoped that it worked as intended. Kerr says that this all meant that programmers (and their supporting operations staff in roles such as Database Administrator - DBA and systems administrator - sysadmin) needed to take down the servers overnight and copy the source code from one directory to another… all while crossing their fingers and hoping that the entire system wouldn’t be taken down, while also hoping they had a reliable copy of the code to roll back to stored safely on a floppy disk. Software would be released every six months and then go to production. ![]() If a company didn't provide access to Microsoft Visual SourceSafe, version control meant having a folder on a hard drive that was passed around between engineers,” said Kerr.įor other engineers at the time, going to production was painful and nerve-wracking because there was a lot of copy/paste involved. “This was a period when software was meant to run on a single machine - there was no such thing as a web application. This all meant that when code was deployed to production, there often wasn’t a ‘live production’ environment (as we know it now with the immediacy and continuous continuity of the cloud) because ‘deploying’ to production meant physically mailing a CD and/or floppy disk to customers so they could update the software on their machine. ![]() If there was a security issue, engineers often wouldn't know about it until it was published in a dedicated magazine or they heard their peers speak about it in a meeting,” clarified Kerr. “Because on-premises datacenters were widely used and personal data did not live on the cloud or across the Internet at the time, there was more focus on physical security - ensuring that data warehouses were only accessed by authorized individuals. ![]() Because of the waterfall effect, it would sometimes take one to two years to deploy projects to production and when it was, security wasn't front of mind.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |