r00t2/resume
1
0
Fork 0
Code Issues Pull Requests Projects Releases Activity

updating for new public render

Browse Source
This commit is contained in:
brent s
2020-11-25 16:55:46 -05:00
parent 759132a207
commit 235bf577f6
8 changed files with 55 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
includes/comm.involv.adoc
View File

@@ -1,8 +1,10 @@
=== Community Involvement
* Hosts and runs a Systems Operations podcast, https://sysadministrivia.com[Sysadministrivia^], for 6 years ongiong
* Hosts and runs a Systems Operations podcast, https://sysadministrivia.com[Sysadministrivia^], for 6 years ongoing
** Maintains accompanying community of other IT professionals
* Engineered, maintained NOC and designed firmware for a community/volunteer-driven city-wide WiFi project (Project.Phree) for 1 year (now defunct)
* Have volunteered for/participated in and raised funds for the https://www.extra-life.org/[Extra Life] children's health charity in 2013, 2015, 2016, 2017, and 2020.
* Have volunteed Systems Support for the https://tasgiving.org/[2020 TASGiving^] charity event (benefiting https://www.nami.org/Home[NAMI^])

5
includes/header.adoc
View File

@@ -1,6 +1,9 @@
[.center]
ifeval::["{filetype}" == "pdf"]
mailto:bts@square-r00t.net[bts@square-r00t.net,About your {ftypef}...] | +1 (504) 338-1513 | Lehigh Valley area, PA
endif::[]
ifeval::["{filetype}" != "pdf"]
mailto:bts@square-r00t.net[bts@square-r00t.net,About your {ftypef}...] | +1 (504) 338-1513 | Lehigh Valley area, PA
endif::[]
endif::[]

2
includes/hobbies.adoc
View File

@@ -1,7 +1,9 @@
=== Hobbies
////
[quote, Ralph Wiggum, The Simpsons (Season 4 Episode 15)]
So... Do you like... stuff?
////
ifeval::["{ftype}" == "cv"]
_A list of interests and hobbies (*outside* of technology) in no particular order, should it make sifting through {ftypef}s more amusing for you._

3
includes/skills.adoc
View File

@@ -32,3 +32,6 @@ to see technical specifics.
** Root cause determination
** Future mitigation design
* Incorporating best practices to ensure interoperability, safety/security, stability
** Implementing RFC recommendations (e.g. `MUST` and `MAY` directives)
** Seeking current advisement from upstream documentation and notices
** Applying new security discoveries as applicable to already deployed projects

41
includes/values.adoc
View File

@@ -1,17 +1,30 @@
== Values
In my professional environment, I value the following:
In my professional environment, I value and demonstrate the following:
* Security, safety, privacy (for both employees/coworkers and customers)
* Accurate and followed deadlines
* Quality first, quantity second, "quickness" third
** Reduce/avoid technical debt
*** Deploy correctly the first time
*** Extensive planning
*** Future-proofing
** Separate Dev, Test/Staging, Production environments
** Scalability
* Stability and availability over (individual) uptime
** Balancing
** Failover
* Clear communication with customers when affected
=== "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.