CTO at goLance • Making software simple • Startup Mentor

80% of companies quit on AI before it helps.

Why? 
• One doubtful engineer
• Scary tool costs
• Or no clear plan

I make those problems disappear.

Who I Am
• 20+ years in code and leadership – from hands-on developer to CTO.
• Scaled SaaS platforms used by millions of customers.
• Trained global teams of 10 – 200 engineers to work faster and smarter.
• Guided “boring-industry” firms like healthcare and banks through tough tech shifts.

What I Bring
• Plain-language coaching – Your leaders and engineers get the “why” and the “how” without buzzwords.
• Tool fit & cost control – Pick the right AI tools, keep data safe, and stop surprise credit charges.
• Team habits that stick – I show devs how to fold AI into daily tasks—code reviews, tests, docs—until it feels natural.
• Measurable gains – Expect quicker releases, fewer bugs, and happier engineers in weeks, not years.
• Outcome pricing – You pay for real results, not for my hours on a clock.

The Bottom Line
If you lead a steady, no-flash company and keep hearing, “AI sounds cool, but…,” let’s talk. I turn that “but” into better software, lower costs, and a team that loves its work.

Brian Childress

Full Stack Software Engineer | .NET Specialist | Master's Student at City, University of London

I’m a tech founder who transforms ambitious ideas into scalable, real-world technology solutions that solve meaningful problems. Over the years, I’ve founded and led tech ventures, built high-impact products across finance, education, healthcare, and enterprise systems, and thrived in fast-moving startup environments.

My expertise sits at the intersection of Software Engineering, AI/ML, and Data Science, where I design and deliver resilient SaaS platforms, distributed systems, and adaptive infrastructures that evolve with business needs. I combine systems thinking, deep product intuition, and strategic leadership to align technology, design, and business goals.

Beyond building tech ventures, I educate and mentor the next generation of engineers and founders, helping them innovate, grow, and lead with purpose.


————————

Subscribe to The Modern Engineer Newsletter: elliotone.com

————————

I am relentlessly focused on delivering:
➜ Value
➜ Impact
➜ Long-term growth

Cutting-edge Solutions → xantco.com


📩 For business inquiries, collaborations, or partnership opportunities, reach out at business@elliotone.com


Let’s Connect:
[1] Instagram: https://www.instagram.com/elliot1one
[2] X (Twitter): https://x.com/elliot1one
[3] Substack: https://substack.com/@elliotone
[4] GitHub: https://github.com/ElliotOne
[5] TikTok: https://www.tiktok.com/@elliot1one
[6] YouTube: https://www.youtube.com/@elliotone
[7] Support my work: buymeacoffee.com/elliotone

Elliot One

Leaking resources is a silent performance killer.

Managing unmanaged resources is not optional if you care about performance, stability, and reliability.

Any time the code touches files, databases, networks, or external systems, it allocates resources that the GC does not manage for you. 

If you fail to release them explicitly, you slowly accumulate problems that only show up under load.

.NET gives us two clear tools for this job:
1. IDisposable for synchronous cleanup via Dispose()
2. IAsyncDisposable for asynchronous cleanup via DisposeAsync()

Using them correctly gives you:
• Fewer memory and handle leaks
• Lower pressure on system resources
• More predictable application behavior
• Better performance at scale

The key is ownership. 

If your class owns a resource, it must also own its cleanup. That means implementing the appropriate interface and exposing a clear lifecycle.

Modern C# makes this easier than ever. 

The using and await using statements ensure cleanup happens deterministically, even when exceptions occur, without cluttering your code with manual try/finally blocks.


A simple rule of thumb:
• Use IDisposable when cleanup is fast and synchronous
• Use IAsyncDisposable when cleanup is asynchronous or resource-heavy


P.S. Clean resource management is not just about correctness. It is about writing code that behaves well under stress and remains maintainable as systems grow.


♻️ Share if you care about clean, reliable resource management

➕ Follow Elliot One for practical Modern Engineering insights

IAsyncDisposable & IDisposable Resource Cleanup in .NET by Elliot One

taplio

The Battle

Brian Childress

Elliot One

Followers

Posts

Engagements

Likes

Performance ScoreElliot One's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Brian Childress

Elliot One

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Elliot One's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreElliot One's LinkedIn Performance