In my professional environment, I value and demonstrate the following:
=== "SSP" ===
*Security*, *safety*, and *privacy*.
These concepts are paramount for both employees/coworkers/clients and customers. By holding these concepts in mind during all stages of a project or product's lifecycle, I believe that other areas (flexibility, economic growth, etc.) become much more achievable.
=== Timing ===
*Deadlines* should be _accurate_ and _followed_. This allows for a smoother development, deployment, and consumer satisfaction level.
When determining deadlines and when developing or deploying *quality* comes first, *quantity* second, and *"quickness"* third. Efficiency is not efficient if it creates more work down the road at the cost of speed.
=== Do it Right, Do it Once ===
By following a procedure and policy that allow for *testing* during development and deployment and by implementing *automation* into that cycle, it allows for *reducing/avoiding technical debt* by paving the road for:
* Deploying correctly the first time
* Extensive planning
* Future-proofing
This is accomplished by a strong focus on:
* *Separate* _Dev_, _Test/Staging_, and _Production_ environments
** *Scalability*
=== Stability ===
In the modern technological world of failover and redundancy, *stability* and *availability* of a service hold priority over individual machines' uptime.
Because of this, I value *balancing* load/resources, deploying *strong failover procedures*, clear *priority levels/SLA* and *clear communication with consumers* when affected.
