Skip to content
Usman Zubair
Go back

What I learned running local LLMs

What I learned running local LLMs

I have been running local LLMs every day for the past few weeks, and one thing became clear.

The improvement came from using the right model for the right job. I was looking for one model that could handle code generation, Terraform, Kubernetes, AWS, CI/CD, documentation, and architecture discussions.

Every model has its strengths and weaknesses

Some are great at writing code Some are better at reasoning through complex problems Some are better at understanding larger systems and infrastructure

I have started to treat them like specialists on a team.

The three models I use

Qwen 3.5 9B

This is my default model. I use it for Terraform, Kubernetes, AWS, GCP, architecture discussions, and anything that needs a broader understanding of a system.

DeepSeek R1 8B

This is the model I use when I need reasoning. Gitlab CI/CD, Github Actions, CI pipeline debugging, workflow design, or anything that needs multiple steps before getting to the answer.

Qwen 2.5 Coder 7B

This one handles most of my coding.

It is fast and has become my go to local model for day to day development.

Benchmarks

I spent too much time comparing benchmarks

In reality, none of this mattered as much as having the right workflow.

My setup

After all the experimenting, my configuration ended up being boring.

That is it.

Will it replace cloud models?

Simple answer. No.

And I do not think it needs to.

For most of my daily development work, local models are more than good enough.

They are fast They are private They work offline

When I run into something that needs deeper reasoning or a second opinion, I still use Claude or GPT.

Conclusion

The biggest lesson was not which models to run. It was using the right model for the right job.



Next Post
Making AI Coding Agents Smarter About Context