🧾 I'm Generating Invoices (and a Little Chaos)

Excerpt:
I’m not billing anyone yet, but in an effort to manage myself and my projects better, I seem to have stumbled into building a pretty decent billing/invoicing microservice.

⏱️ Tracking the Work

It started with a simple idea:

“What if I could just track my time per task?”

Well, I did that… and then I added:

• Session tracking – start/stop timers for work sessions.
• Per-task billable rates – because not all work is created equal.
• Invoice generation – yes, it even spits out a PDF.

The result? I can now select time entries, generate an invoice, and (at least in theory) hand it to someone and say, “Pay me, please.”

💡 The Next Steps

Of course, there’s still plenty I need to figure out:

• Multiple invoices & proper numbering
• Terms and due dates
• Payment tracking
• Probably a bunch of edge cases that will only appear when I finally get a real client

But still—this feels like a good start.

🏗️ Building Until I Get Noticed

If someone commissioned me tomorrow, I could put together coherent billing that tells a story, and that feels like a win.

I know I’m not done learning (far from it). I look forward to the headaches I haven’t met yet, but for now, I just have to keep building until someone notices.

📝 Final Thoughts

This is exactly why I build in public. Seeing a problem, solving it, and implementing a solution is where I want to live.

Even if no one else ever uses this system, it’s already helping me manage my projects better—and that’s enough reason to keep going.

This article was generated with 25% rambling from Proper and 75% refinement by ChatGPT — because building in public sometimes means letting an AI turn your brain dump into a readable blog post. 😅