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, architects, managers, testers, admins, technicians, business analysts, webmasters, data scientists, operators, integrators, technical leads, stakeholders, project managers, and agile coaches all beating down your door to promise you that they know how to get it done. What, me worry?
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 trigger? All the way? How do you know for certain? Who verifies that your systems are designed, developed, deployed, and running properly? And who watches the watchers? Such questions do not require a PhD in Information Systems Epistemology, rather, decisive action based upon code of the samurai is the surest path to understanding.
When you try to swing the C# fast, you deviate from the Way of the C#, and so it is hard to swing. The idea is to swing the C# calmly, so that it is easy to do.
To know the Way of the C# means that even when you are wielding your C# with two fingers, you know just how to do it and can swing it easily.
Pricing à la Carte
Service
Description
Retainer
Advanced Algorithms
Algorithms, calculations, computed approximations, analytics, etc. that require total complex case coverage, graceful degradation, formal verification, or mission-critical systems programming.
$50,000
Continuous Delivery
Development operations from source to build, configure, deploy, release, and rollback.
$50,000
Infrastructure Alignment
Platform assessment, resource planning, cost forecasting, system restructuring, provisioning, or installation of system runtime & program execution environment.
$75,000
Prototype Solutions
Proof-of-concept constraint/domain analyses encapsulated within a useful, working-code solution.
$100,000
Backend Services
Windows OS Services or any always-on, high availability background service or backend system.
$150,000
External Systems Integration
Third-party SaaS providers, APIs, client/server libraries, SDK implementations, etc. for interoperating with an external service or internal systems integration.
$150,000
Web Applications
Web Applications built from scratch to be efficient, maintainable, reliable, extensible, and scalable.
When you try to swing C# fast, the way you might when using a short sword or javascript you deviate from the Way of the C#, so it is hard to swing. That is called "short sword mincing" and is ineffective for killing a Ninja.
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, architects, managers, testers, admins, technicians, business analysts, webmasters, data scientists, operators, integrators, technical leads, stakeholders, project managers, and agile coaches all beating down your door to promise you that they know how to get it done. What, me worry?
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 trigger? All the way? How do you know for certain? Who verifies that your systems are designed, developed, deployed, and running properly? And who watches the watchers? Such questions do not require a PhD in Information Systems Epistemology, rather, decisive action based upon code of the samurai is the surest path to understanding.
