Community12 min read
Staying Motivated, Week 2: The Grind — Setbacks, Funding, and the Team That Showed Up
The middle of any long project is where most people quit. This is the story of the grind — the setbacks that tested us, the funding challenges that kept us up at night, and the people who showed up when it mattered most.
Week 1 of this series covered the early days — the spark, the first lines of code, the moment we realized TCTF was bigger than a side project. This week, we talk about what happened next. The middle. The middle is where most projects die. Not because the idea was bad. Not because the technology failed. But because the grind wore people down. The excitement of the beginning fades. The finish line is not yet visible. And every day feels like pushing a boulder uphill with no guarantee it will stay at the top. This is the story of our middle. The setbacks. The funding challenges. And the people who showed up when it mattered most.
01The Setbacks Nobody Talks About
Every project has a highlight reel — the launches, the milestones, the metrics. But behind every highlight reel is a blooper reel that nobody sees.
We had services that worked perfectly in development and broke spectacularly in production. We had architecture decisions that seemed brilliant at the time and cost us weeks to undo. We had the December 2025 rewrite — an entire month spent tearing apart a working monolith and rebuilding it as 34 independent services, with no guarantee it would be better.
We had days where nothing worked. Days where the CI pipeline was red for hours. Days where a single misconfigured IAM policy brought down an entire service. Days where we questioned whether we were building the right thing, in the right way, at the right time.
These setbacks are not failures. They are the cost of building something real. The difference between a project that ships and a project that dies in the middle is not the absence of setbacks — it is the willingness to get back up after each one.
💪Setbacks are not failures. They are the cost of building something real. The difference is not the absence of setbacks — it is the willingness to get back up after each one.
02The Funding Question
Building a platform with 34 microservices, 4 frontend applications, and a growing community is not free. Cloud costs, domain registrations, design tools, third-party services — they add up. And when you are building something that is not yet generating revenue, every expense is a bet on the future.
The funding question kept us up at night more than any technical challenge. Not because we did not have resources, but because the resources were finite and the ambition was not. Every dollar spent on infrastructure was a dollar not spent on community programs. Every hour spent on code was an hour not spent on fundraising.
We learned to be ruthlessly efficient. Serverless architecture was not just a technical choice — it was a financial one. Pay-per-use pricing meant we only paid for what we used. DynamoDB on-demand meant no provisioned capacity sitting idle. Lambda meant no servers running when no one was making requests. The technology choices were driven as much by budget as by architecture.
The funding challenge is not solved. It is ongoing. But we learned that constraints breed creativity. When you cannot throw money at a problem, you throw ingenuity at it instead. And the solutions you find are often better than the ones money would have bought.
💰Constraints breed creativity. When you cannot throw money at a problem, you throw ingenuity at it instead. Serverless was not just a technical choice — it was a financial one.
03The People Who Showed Up
The technology is important. The architecture matters. The funding is necessary. But none of it matters without the people.
Building TCTF is not a solo effort. It never was. The people who showed up — who contributed code, who reviewed pull requests, who wrote documentation, who tested features, who gave feedback, who believed in the vision when it was still rough around the edges — they are the reason TCTF exists.
Some showed up for a week and moved on. Some showed up and stayed. Some showed up at exactly the right moment with exactly the right skill. Every contribution, no matter how small, moved the project forward. And every person who believed in what we were building gave us the energy to keep going.
If you are building something and you feel alone — you are not. The people who are supposed to find your project will find it. The contributors who are supposed to join will join. The community that is supposed to form will form. Your job is to keep building. The people will come.
🤝Your job is to keep building. The people will come. Every contribution, no matter how small, moves the project forward. The community that is supposed to form will form.
The middle is hard. It is supposed to be hard. If it were easy, everyone would do it. But the middle is also where the real work happens — the work that separates ideas from products, dreams from reality, side projects from platforms. Next week, in the final part of this series, we will talk about where we are now and what keeps us going. Stay tuned.
Editor's Note: This is Week 2 of the 'Staying Motivated' series — a personal story about building TCTF. Read Week 1 for the beginning and Week 3 for where we are now.
CommunityOpen Source
Never miss a post
Subscribe to get the latest TCTF articles delivered to your inbox.
