#074 - Adapting Flocode | An Update for Subscribers

Building a Better Way to Learn Python for Civil and Structural Engineering

Jul 15, 2025

Time for an update, an unfiltered look at where Flocode is going, what I’ve learned, and what’s next.

How It Started

In the summer of 2023, I set out to build a course for civil and structural engineers to learn Python. The goal was simple: give engineers the programming skills they need without forcing them to wade through generic, irrelevant tutorials. I wanted practical, no-fluff material calibrated for our industry. Something I should have had when I started with Python.

Along the way, I launched this newsletter. At first, it was a side project, a place to document thoughts, explore ideas, and engage with the growing Flocode community. But something unexpected happened: it became the most enjoyable part of the project.

The diversity of topics, the podcasts, the connections and the conversations with domain experts from around the world, these are what make it worthwhile. Far more, in fact, than the many hours I poured into curriculum development and video editing. This seems absurdly obvious in hindsight, but that’s life.

“As you start to walk on the way, the way appears” - Rumi

The Problem with Dense Courses

I built a rigorous curriculum. I recorded technical presentations. I wrote and re-wrote a lot of code. I covered a lot of ground. It was good, dense, but good.

Slowly, reality began to set in as I waded deeper into the weeds.

Engineers are busy. I'm busy. You’re busy.

Nobody has the time or patience to sit through hour-long walkthroughs of complex engineering calculations. What I had built was useful, but it demanded too much effort from the people it was meant to serve.

At the same time, AI tools continued to evolve. Large language models are becoming increasingly more capable, and the idea of building long, rigid courses feels outdated. Not obsolete, just… inefficient.

My Preferred Approach

Instead of detailed, extensive courses, I’m shifting towards something leaner, sharper, and more adaptable.

Bite-sized, focused learning – Less time-consuming lectures, more distilled, actionable knowledge.
Mental models and frameworks – Teaching how to think, not just what to do.
Practical, problem-solving skills – Once you know how to "ride the bike," you can take it wherever you want.
Examples and Templates - I build many different tools programmatically, both to support the workflows of technical staff and myself. I want to share what I can from these tools.

I’m still interested in structured learning, but not in the form of a sprawling online course platform.

Instead, I’m consolidating everything here on Substack—writing, resources, and (eventually) well-organized learning paths. One platform. One place to find everything.

No Community Management, No Social Media Circus

Another realization: I do not want to manage an online community. I set up a Zulip-based discussion space, and while it's a great platform, engagement has been sporadic and honestly, I’m relieved.

Moderating a community is a demanding role in itself. My time and focus is better spent developing content, building resources for engineers, not running a virtual meeting space.

As for social media? A necessary evil of our time. I don’t have a great solution. Every time I post anything, I feel like David Brent.

Unfortunately, it’s also the best way to reach people who are interested in Flocode.

Where This Leaves Flocode

This newsletter remains the core of Flocode—where I share insights, engineering applications, podcasts, research, and practical Python workflows that actually work. If you're reading this, you're in the loop moving forward.
If you can’t afford it, I’ll figure something out. If you can, your support keeps this going. There’s already a deep archive of practical content, Python workflows, GitHub resources, real-world applications etc., because I wanted to prove my commitment before asking for anything in return. But long-term sustainability matters. At some point, this needs to work for both of us.
No unnecessary complexity. No bloated course platforms. Just practical, no-nonsense knowledge in an efficient format.

Flocode’s Business Model

I want Flocode to be accessible. If paying for any of my work causes financial stress, just reach out, and we’ll sort it out—no questions asked. I have no interest in locking information behind a paywall that some people can’t afford.

At the same time, sustainability matters. I’ve been producing content for free since October 2023, not as a a marketing trick, but because I wanted to build something before asking for support.

If you find value in what I’m doing, your support allows me to keep going, refining, and expanding practical content for engineers interested in Python and open source tools.

I expect some will take this offer in good faith, and others will abuse it. That’s fine. If the net result is that people who genuinely need this material get access, then the system is working.

For those who support this project financially, you’re not just paying for content, you’re helping to keep this knowledge open and available for those who need it. That’s something I deeply appreciate.

This update might be light on Python, but these strategic adjustments are just as important for getting you where you need to go.

Thank you again for being a part of this.

See you in the next one!

James 🌊