fordodone (@ForDoDone) profile picture

Systems Architect, Nix/network/storage/db guru, BASH masochist, CM enthusiast, automation addict, cloud operator, mixologist #DevOps #FOSS #dockerize #puppetize

Joined April 2013
Photo by fordodone (@ForDoDone)Photo by fordodone (@ForDoDone)Photo by fordodone (@ForDoDone)Photo by fordodone (@ForDoDone)Photo by fordodone (@ForDoDone)Photo by fordodone (@ForDoDone)Photo by fordodone (@ForDoDone)Photo by fordodone (@ForDoDone)Photo by fordodone (@ForDoDone)Photo by fordodone (@ForDoDone)
The most effective leaders know that what they say matters 5% and what they do matters 95%.
The irony of leadership is that the people who most need to grow and change are those that are the least likely to be open to it.
Career Achievement Unlocked: Referencing by number an obscure 20+ year-old RFC off the top of your head and it having the answer to the question!
Replying to @John_Papa
I always always type "mysql" when I'm trying to type "myself" (<-- literally just mistyped it here and had to fix)
I would definitely participate in this Rackspace Feedback Session if the incentive was a $100 in AWS credits.
New post: gracefully stop php laravel sqs worker in Docker on ECS Fargate fordodone.com/2019/02/08/gra…
New post: awslogs agent running inside Fargate container fordodone.com/2019/01/29/aws…
1
This is so toxic because they end up sabotaging themselves at the same time, failing to realize that your team/organization getting better, making more informed decisions means that you get better. "A rising tide floats all the boats"
Replying to @CatSwetel
Information hoarding also helps people individually move on projects or position themselves in a good light because they were artificially able to perceive the future. Once everyone else gets the information, they hoarder has an apparent step up.
2
Replying to @CatSwetel
I find that in low trust organizations people hoard information because they want to be involved in decisions. Making the information hard to get guarantees they will have a seat at the table during decision time.
1
oh they left the company? proceed with gusto.
Pro Tip: maybe do a git annotate (blame) before you decide to talk shit about the code someone in your slack channel wrote.
1
use a wide ranging spectrum to describe vendor lock-in, and treat it like it can be measured and estimated
1
1
much like leveraging technical debt, vendor lock-in can be exploited or used as a tool, consider the trade-offs
1
1
not all vendor lock-in is created equal
1
1
1
Replying to @krisnova
1) Introhm (Agent 23) 2) You make it rough (Chromeo) 3) Street Scene (St. Germain) 4) Feel like a stranger (the dead)
1
OH: We have an MVP, but M stands for Maximum. not #agile not #lean
Implementing successful CI/CD is so fulfilling. Taking a change from my laptop to production in less than 30 minutes is still amazing to me. I giggle every time.
Replying to @yanaga
@yanaga highlighting the classic #devops problem: the Wall of Confusion #CNADPHX
1