← Back to Insights An Old Dog's New Tricks — Part 4

How I Connected AI to Everything I Touch at Work

Ken Whiteside July 2026 5 min read

A few months ago, AI was a chatbot I asked questions to.

Today, it's connected to every system I work with. Snowflake. SQL Server. Jira. GitLab. Zephyr. PagerDuty. All of it.

That didn't happen in one day. It happened one connection at a time.

It started personally. I have brokerage accounts with market data access, and I asked AI: "What data is available from these accounts?" It not only found out what was accessible — it showed me how to connect. Then it suggested free data sources that could fill gaps and how to hook into those too.

The pattern was always the same: most applications have some kind of interface that allows connectivity — a key, a token, a connection string. You don't need to understand the technical details. Just ask AI: "Can I connect to this tool?" and it will find the way in and set it up.

Once I saw how simple each connection was, I started wondering about the tools I use at work. Could I connect to those the same way?

Sure enough — Snowflake had one. Jira had one. GitLab, Zephyr, PagerDuty, even the reporting tools. Each one had a way to connect waiting to be used.

One connection at a time, I was enabling myself to work smarter and faster than ever before.

Here's what most people don't realize: pre-built connectors are a starting point, but they often lack full capability.

Going direct — setting up the connection yourself with AI's help — gives you full access to the capabilities you're already approved to use. Then AI can DO things for you, not just TALK about things.

The difference between "AI answers my questions" and "AI executes my work" is just connectivity. Once AI can reach your systems, it goes from advisor to assistant.

Today, my workflow looks like this:

  • Jira ticket comes in
  • AI reads it, drafts the implementation
  • I review and adjust (the 20% that needs human judgment)
  • AI generates the code, the test cases, the CR documentation
  • AI formats it for our CI/CD pipeline
  • I validate and approve

What used to take days takes hours — not because I'm faster, but because the mechanical parts are gone.

And here's the thing — connecting each system wasn't hard. The barrier isn't technical. It's the same mindset barrier I talked about last post: realizing you should even TRY.

Two things I want to be clear about:

First — this isn't bypassing anything. AI operates under YOUR existing access and security. The same permissions and guardrails that apply to you apply to AI working on your behalf. You're not unlocking anything new — you're letting AI use the access you already have.

Second — be explicit about your environment. If you work with Dev, UAT, and Prod, tell AI which one you mean. Say "write to DEV" not just "write to Snowflake." Be specific about where you're pointing.

Every system you touch probably has an interface you can connect through. Start with one tool you're familiar with and ask AI: "How do I connect to this?" I didn't even know Personal Access Tokens existed until AI guided me to them.