AI coding assistants in the editor, CLI, and version control

I started using the GitHub CoPilot at work this week to connect my local files on my machine to an agentic code tool like Claude Code. @GitHubCopilot is really nice. If you are working in a corporate environment and you're a @Microsoft shop, this is a great tool with access to all the main LLM models.

I know you can use the various LLM models through VS code as well, but I'm not a developer and just want the natural language interface for developing specific solutions for myself. An example is I created an API connection with JIRA for project management, and it worked seamlessly. That solution is also much easier than PowerBI because I can ask questions of the data better and adjust the solution on the fly.

Worth checking out especially if your company doesn't allow access to Claude Code or Codex.

There was a time when looking at a code you could have an idea who in your team wrote the code. The variable naming convention, the coding style and even the comments were enough to give that hint.
I have been doing some serious coding using copilot as well as reviewing others code for some time now and I could see the changed times.

No personality in the code.

Can we tell our copilot to use our style of coding for code suggestions or is it already there and I didn't know.

AI vs Developer

I'm looking back from February 2026, and honestly? The headlines screaming"AI is killing developer jobs" feel overblown. I've lived the transition firsthand, and my career is stronger than ever.

I started as a developer in 2022, right before the AI boom. Landed in a fast-moving startup, working with Java (not exactly beginner-friendly). No senior dev shadowing me, no endless Slack help, my boss was slammed, so I couldn't ping him with every little question. That meant grinding through problems solo: debugging, reading docs, trial-and-error. Brutal at times, but it built unbreakable fundamentals. No crutches, just deep understanding.

Then ChatGPT landed in late 2022early 2023. Game-changer. Suddenly, 20% of my daily work  writing functions, handling tricky logic, boilerplate -- was AI-assisted. I was on free tiers of ChatGPT and Claude (premium felt like a luxury in startup life), but even that sped things up massively. In an environment where ship fast was the mantra, AI let me deliver quicker without sacrificing quality.

Back then, I used AI mostly for greenfield code. No GitHub Copilot access yet, so I didn't lean on it to explain or refactor existing team code. That kept me honest -- I still read and understood everything manually.

Fast-forward: I joined a multinational company. Boom  GitHub Copilot in the IDE, AI agents in the CLI, the full modern toolkit. My workflow evolved overnight.

Now it's simple (and powerful):

I drop the user story into an AI agent: Here's the requirement -- give me a thoughtful implementation plan.

It returns architecture, steps, edge cases.

I review, tweak for our system's realities.

Quick check with seniors: Does this align?

If yes-- I hit enter.

Features that took days? Scaffolded, coded, and ready to polish in minutes. Its not magic  its acceleration.

So, is my job gone in 2026?

If I blindly accepted AI output, merged without review, and called it done -- yeah, I'd be at risk. That path leads to garbage: misunderstood context, hidden bugs, exploding tech debt. We've all seen it.

But any developer with real system knowledge (even 50%+) wont do that. I dont. I treat AI like a turbo-charged junior: it drafts fast, suggests boldly. Then I bring my fundamentals -- architecture judgment, domain insight, trade-offs, security, scalability  to validate and refine. AI proposes; I own the decision. AI generates; I ensure it fits.

In 2026, thats the winning combo. Developers who master this partnership? Were not fading  were thriving. AI handles the repetitive 80%; we own the high-value 20%: critical thinking, system design, creativity.

My gut says were safe for at least the next 5 years. Beyond that? Tech always disrupts, and we adapt like we did with cloud, mobile, every wave before. New tools create new roles.

If youre-reading this as a developer: double down on fundamentals. Use AI aggressively as your co-pilot, never as a replacement. The ones who do will come out way ahead.

Views are my own and dont represent any past or current employer.

What's your 2026 reality? Has AI flipped your workflow like this? Juniors starting now vs. pre-AI vets -- what's different for you?

Drop thoughts/questions below
I'd love to chat.

I’ve been using the Copilot CLI on a daily basis for coding, review, planning, design, and for debugging production systems. It’s awesome! Glad to see it reach GA. 👏

I use Claude code a lot these days , but only let it touch personal code that is under GitHub version control, to avoid this kind of situation….

I use copilot at work with the most recent models (Opus 4.5, Codex 5.2, etc.,) and the limits are more than generous, context window is amazing, and I am hearing that it's better than native Claude Code.

You should start with Copilot and then if that's not enough, try CC.

I’m a cautious skeptic of AI/LLMs, but I’m trying to use them where it makes sense in my software work. As I use chat/agent tools to help implement and debug code, I make a point of clearly documenting which commits (and sometimes lines) include LLM-derived code—often using Git commit trailers like `Co-authored-by` with the model name/provider—to improve traceability for reviewers and to reduce future legal/compliance risk.