Everything I Shipped This Year (And What I'd Cut in Hindsight)
A year ago, I founded Sage Ideas LLC with a vague plan: build trading tools, offer consulting, and see what happens. Here's the honest retrospective.
What I Shipped
The Nexural Ecosystem — 7 interconnected systems:
- Trading Dashboard (185 tables, 69 APIs, Stripe billing)
- Discord AI Engine (30+ commands, GPT-4o, 12 phases)
- Research Engine (71+ metrics, strategy analysis)
- Alert System (.NET 8, NinjaTrader integration)
- Newsletter Studio (automated content pipeline)
- Strategy Tracker (performance analytics)
- Automation Suite (61 test suites)
AlphaStream — ML trading signals (200+ indicators, 5 models)
RiskRadar — Portfolio risk platform (Ledoit-Wolf, CVaR, optimization)
This Portfolio — The site you're reading. SLOs, incident drills, live dashboard, 27 artifacts, 50 blog posts.
The Book — 120,000 words on trading. 24 chapters. In editorial phase.
Active Trading — 8 symbols on NinjaTrader. ES, NQ, CL, GC, and more.
What Was Worth Every Hour
The Nexural Platform. It's the centerpiece of my portfolio. Every interview and client conversation starts with "you built a platform with 185 tables?" The depth of this project opens doors that a dozen smaller projects never would.
The Blog. 50 posts is a body of work that signals "this person thinks deeply." Every post is a shareable artifact. When I apply for a job, I include a link to a relevant post. It's more convincing than a bullet point on a resume.
The Platform Engineering Page. SLOs, incident drills, security receipts — this page alone has changed interview conversations from "can you code?" to "tell me about your operational experience." That shift is the difference between mid-level and senior offers.
What I'd Cut
Nexural Newsletter Studio. Built it, barely used it. The trading community wanted Discord alerts, not email newsletters. I should have validated demand before building.
Multiple API Testing Frameworks. I have 3 repos that do similar things: API-Test-Automation-Wireframe, API-Testing-Framework, and the API test suite in E-Commerce-Test-Suite. I should have built one excellent framework instead of three mediocre ones.
The visual regression testing suite. Percy integration is cool, but the repo has 1 commit and tests 1 page. If I'd spent those hours improving the E-Commerce-Test-Suite, my best QA repo would be even stronger.
What I Learned About Building
Ship the first version ugly. The Nexural dashboard's first deploy was embarrassing. No styling, broken mobile layout, placeholder data. But it was live, I got feedback, and version 2 was 10x better because of it.
Document as you build, not after. Every system I documented upfront was easier to maintain. Every system I said "I'll document later" became a mystery box within 3 months.
Your portfolio IS the job. I spent more time on sageideas.dev than on most client projects. The ROI has been enormous — inbound interest, interview conversations that start at a higher level, and proof of operational maturity that no resume bullet point can match.
What I'm Building Next
I have three things on my roadmap:
Improve existing projects. The 11 public repos on my portfolio need stronger READMEs, more commits, better CI, and real screenshots. Quality over quantity.
A Terraform module library. Reusable AWS modules for the patterns I've built multiple times. This fills the infrastructure gap in my portfolio.
Open-source contributions. Even small PRs to established projects add credibility. I want 5-10 meaningful contributions to projects I actually use (Next.js, Supabase, Playwright).
The Honest Numbers
| Metric | Value |
|---|---|
| Systems shipped | 7 |
| Database tables designed | 185 |
| API endpoints built | 69 |
| Blog posts written | 50 |
| Book words written | 120,000 |
| Certifications earned | 9 |
| Test suites running | 61 |
| GitHub commits | 500+ |
| Revenue generated | Private, but enough to fund the building |
| Hours worked | Too many to count |
The Bottom Line
Building in public for a year taught me that the work itself is the portfolio. Not a list of bullet points — the actual running systems, the honest blog posts, the documentation that outlasts you.
If you're starting your own engineering brand, my advice is simple: build real things, document obsessively, be honest about failures, and ship before you're ready.
The perfect portfolio doesn't exist. The shipped one does.