I Am a Sample Size of One
"It doesn't work on me" is not analysis. It's projection. How I caught myself reasoning from a sample size of one.
Trials and tribulations of a 1x dev running a bootstrapped startup
"It doesn't work on me" is not analysis. It's projection. How I caught myself reasoning from a sample size of one.
The desk doesn't just mirror my mental state. It shapes it. Shape the environment first, and the work that happens inside it sharpens on its own.
Why I stopped pushing past 2 AM. Ted Mosby's mom was right — nothing good comes from it, and the next day always pays the bill.
Planning is the stage that matters. We spend five focused minutes reading the AI's plan before we run anything. Boring as hell. Only thing that works.
The disconnect didn't happen all at once. It happened in a thousand unanswered messages. A quiet goodbye to the circle I drifted out of.
Going dark on notifications was the scariest productivity move I made. Almost everyone can wait. I just didn't believe it until I tried.
I don't try anymore. I succeed. Small wins stack until the big prize unlocks. I forgive bad days and keep going. Eighty percent beats quitting.
We treat AI like a newborn carrying the world's intelligence. Tools are the windows it sees through. More windows, better software.
Separate repos made sense when humans were the bottleneck. With AI-assisted development, unified context beats independent deploys every time.
The 2-minute rule is the simplest habit I follow at work and home. If it takes 2 minutes, I don't defer it. I do it.
I stopped filling every quiet moment with podcasts and music. Going headphones-free is uncomfortable — and exactly what my thinking needed.
GitHub Projects felt organized but always died. We learned the best planning tool isn't the most structured one — it's the one you'll actually keep updating.
Fear of failure stops more people than failure itself. At YoPrint, we move forward, course correct, and keep going. You only fail when you stop.
We lost sight of the big picture by optimizing the wrong number. Here's how we're fixing that at YoPrint this year.
We choose excellence. After removing mediocre performers, work started flying. We finally had time to build infrastructure, not just survive.
AI lets us build the architecture we always wanted but couldn't afford.
Nothing kills team momentum faster than tolerating someone who can't deliver.
The carpenter doesn't blame the nail gun. We don't blame the AI. We hire thinkers who take full ownership of what they ship.
Pair programming used to mean two developers, one keyboard. Now it's two minds, one prompt. AI types, we think.
A table bump shouldn't close your dialog. We disabled click-away and kept Escape. Intentional actions only.
No deep dives. Just quick votes on what worked and what failed. Weigh them against your own.
We stopped shielding our team from deadlines. We ended up working around employees instead of on the product. Never again.
We're removing toast notifications from YoPrint. Actions show feedback where they happen. No random flickering. No covered content. No noise.
The ugliest bugs hide where data meets UI. DTOs are the firewall.
I wasted time lowering standards for new hires at YoPrint. Set the bar high from day one. Make them rise to your level. Never settle.
You can't please everyone. Ship what matters, not what makes everyone happy. Give it two weeks. Real feedback comes after the noise settles.
I shipped faster, stressed less: my incremental release story
I tried hiring superman employees. Failed twice. Here's how I learned to hire specialists and build systems instead.
Recovering from coding addiction. Now hiring, managing, and trying not to sneak in weekend projects. Send help.
Recap of 2024 achievements: launched V2, delegated tasks, managed more, wrote 15 articles, acted without over-reading, and hit 90% success
I let my engineers lead decisions, encouraging creative solutions and independence for truly effective problem-solving.
We ditched WordPress for a faster, cleaner site with Directus, Next.js, and Tailwind. After hard work and some fun struggles, it was 100% worth it!
Why does remote work matter? At YoPrint, we value flexibility, focus, and results over office distractions and rigid 'productivity' mandates. Here's why.
Innovation doesn’t happen in meetings—it happens when I act. Ideas are worthless without action. I turn thoughts into results by simply doing.
By delegating sales and support to my customer success manager at YoPrint, I freed up 90% of my time to focus on features. Discover how letting go boosted our productivity and won over customers.
By trusting my engineers and embracing mistakes, I fostered growth and boosted productivity. Letting go transformed our team's success. Here's how
By redefining bugs vs. enhancements, I boosted productivity and shipped meaningful features. Here’s how I classify and prioritize tasks for better balance.
Growing up questioning everything, I now make it a priority at YoPrint to explain the "why" behind our decisions, fostering understanding and better solutions.
At YoPrint, I explain why we say no to lucrative custom modules. They fragment code and harm service. We focus on features benefiting all customers.
Hey! I revamped the blog with a minimalist style—clean fonts and calming colors—for a distraction-free, zen reading experience. Check it out!
I left my 9-5 at Microsoft to build YoPrint from scratch. Follow my journey of growing a bootstrapped software business, overcoming challenges, and lessons learned.
I’ve stopped pluralizing variables in code. Here’s why, how language quirks play a role, and a simpler approach to naming collections in programming.
We encountered a major email abuse issue during our YoPrint trial. Here's how we fixed it, learned from it, and improved our system to prevent future incidents
Here are the techniques I use to write better 'if' statements, making code cleaner and easier to read. Hopefully, they'll be useful to you too!
After a long break, I’m back on YouTube! I’ll share insights on running a bootstrapped startup, UI/UX design, and coding tips. Join me on this video journey!
Happy New Year! This year, I’m focusing on doing less to achieve more: prioritizing impactful YoPrint features, delegating customer success, coding less, and sharing my journey.
After 7 years upgrading YoPrint from Angular 4 to 15, we faced many challenges. Here's our journey, how Nx helped, and why we’re now migrating to React.
We’re leaving Angular because of Zone.js—it's invasive, slow with third-party libraries, and hard to debug. Switching to React boosted our app's performance.
At YoPrint, we switched from Angular to React. Here's why, the benefits of MUI over Angular Material, and how Redux Toolkit simplified our state management.
I refactored our codebase to simplify handling Pricing Group drafts in YoPrint. Here’s how I improved clarity and decoupled logic to boost flexibility.