C#SAMURAI
C#SAMURAI
C#SAMURAI
C#SAMURAI
C#SAMURAI
Even if one's source-control were to be suddenly cut off, he should be able to do one more deployment with certainty.
The art of software engineering has plenty of tradition, best-practice, standards, architecture, automation, software lifecycles, deployment processes, methodologies for adapting to change or growth, and all of that good stuff... In reality, there are infinite ways for writing code and organizing the design, development, deployment, future growth and maintenance of a planned or ad-hoc system. Not surprisingly a professional army beckons your command: an entire industry teeming with specialists, designers, a
Who wrote the code? What was the R&D process? Were all of the options presented also well-researched, practical, and right-sized solutions? How did design happen? Did experimentation actually prove the concept? QED? Who made the daily micro-decisions? Is the working code documented? Any idea if the original design was sound? Were all of the critical changes merged into the current release? What is the process for deploying a patch? Which deployment process requires a server reboot? Did last night's batch tr
C#SAMURAI
C#SAMURAI
C#SAMURAI
C#SAMURAI
C#SAMURAI