From Code Cowboy to Cubicle Architect

SHARE

Non-Fluffy Edition

Picture this: a pregnant wife, a looming due date, and a bustling software business with a team of three devs. I was the captain of this entrepreneurial ship, navigating the exhilarating highs and gut-wrenching lows of client work. Don't get me wrong, I loved my clients (most of them), but the constant feast-or-famine cashflow felt like a haunted house – thrilling, exhausting, and guaranteed to leave you questioning the choices that got you there.

Enter my wife, the voice of reason (and frequent eyebrow-raiser extraordinaire). She started saying things like "stable paycheck", "job", and "maybe you should fight that client". Well, maybe not that last part, but with the baby news and her not-so-subtle hints, I started reconsidering.

Fast forward: I'm five months into my corporate gig, a reformed code cowboy turned corporate architect, and oh boy, do I love this office life! The team's awesome, the projects are challenging, and my (wife's) paycheck arrives like clockwork – a beautiful symphony of financial stability.

Now, with 40 hours neatly tucked away, the rest of my time explodes in a glorious technicolor of family, side projects, and self-improvement. I'm still slinging code, but this time for me and with the peace of mind that comes from knowing my fridge won't stop running (else, I'd better go catch it).

It's surreal, it's like I just completed scaling Mount Startup only to discover the peak was actually a comfy ergonomic chair with a decent view. Don't get me wrong, the entrepreneurial fire still flickers. Nights are for my own code babies, nurtured by the day's architectural expertise. I'm a code chameleon, blending corporate camouflage with independent stripes.

This journey, fueled by sleep deprivation, questionable career choices, and the occasional baby poop explosion, is one I'm excited to share. I'll be here, dissecting code, exploring tech, and hopefully, adding a healthy dose of humor. Come along, ask questions, share your own adventures. Let's build a community where learning is as fun as a sugar rush, but without the inevitable crash.

I'm in the lab as I write this with plenty of content in the pipeline. I'll be posting regularly, so stay tuned for the next installment in the ongoing saga! If you have thoughts or questions, don't hesitate to connect in Discord or on X, @RickDotNet.

Until next time,

Rick (the reformed, but never tamed, code cowboy)

P.S. I'm still working on finding my "style" for these articles. The jury's still out – fluffy or casual? Let me know what you think!