From powerdns, dnsdist, vector, and Prometheus - it’s been an interesting couple days of labbing. Now to identify the key metrics to fine the bottlenecks in this pipeline…
@theseanodell I do not and share your confusion and disbelief. There is so much that is supported that is not at all the way of Christ. It causes me to wonder how many Christians truly understand what Christ tried to teach us - in words and in his life. It makes me sad.
#TweetEveryDay 1) Values drive what you prioritize. What you prioritize reflects on your belief of what is important.
2) Accepting that something works without knowing _why_ it works, means someday you will discover why it does not work (anymore).
#TweetEveryDay
Thing 1) Metrics/data are powerful to those with understanding.
Thing 2) Whether physical, mental, emotional, or spiritual; most of the time we know what the healthy thing is to do. We simply choose the unhealthy thing. Goal for the year? Choose the healthy thing.
This echoes my painfully small experiences in using AI. The organization is still the bottleneck. Additionally, on the technical side, AI is still a power tool which in the hands of the unknowledgeable, simply shortens the mean time to chaos.
We’re seeing 2–3x productivity gains for developers using AI—but general-purpose copilots? Not so much.
Why? Developers work in structured, well-engineered systems. Copilots are thrown into chaotic, human-centric workflows that evolved without process rigor.
We keep trying to automate tasks that still require human oversight—because we don’t trust the AI.
So we get to decisions faster... but still wait on humans to approve them.
That’s not scale. That’s acceleration with a manual brake.
Until we invest in process engineering, copilots will underperform—no matter how good the model gets. cc @COentrepreneur
@CTOAdvisor Check the redirect on https://t.co/oDFFv0Eu5O - there is an ever so slight typo that results in an nxdomain. Although, I kinda like the idea of an everday... ;)
That said - good stuff and looking forward to more.
Our networks are like these homes—they are not houses so much as historical records of every new idea and vendor marketing drive. There is no architecture, there are many architectures strung together with a set of tightly wound and closely followed processes.
We need to support some new application or service? Throw a new overlay on top. There was a massive failure last night? Let’s spend hours closely examining our process and find some way to prevent the failure by adding a few new steps.
https://t.co/ae3BWKxO79
My 2nd grader is reading the after-visit summary from his urgent care visit. Like actually reading and understanding it. I’m wondering if that’s what he’s doing for fun when he’s sick now, just wait a few years when he’s healthy and gets his hands on a technical manual.
@standaloneSA There is no winning. There is no such thing as "secure". The only way anyone has a chance is to stop thinking of InfoSec as another "team" and instead as a "state of being". Security then becomes another function of your job. The "teams" job is to educate and answer questions.