Here's a random idea I was thinking about this morning. Playbara - a Capybara driver that uses Playwright under the hood instead of Selenium or Cuprite. Same Capybara DSL, but modern, fast, headless by default.

Most teams can cut their CI test time by 40% with better parallelization. Built a quick analyzer to show the potential savings. What's your biggest CI pain point?

Still no SaaS success after years of building... but I’m not quitting. Here’s what I’ve learned (and my latest idea for optimizing CI test speed for Rails devs): 👉 [dev.to/damonclark/ive…]

Honest question: How many dev teams are actually using test parallelization in their CI? And of those that are - how many have optimized it beyond just splitting files evenly? Feels like there's a huge gap between "best practice" and reality 🤷‍♂️

🚀 Tests slowing down your CI? Try: Parallelization Test retries for flakies Isolate slow E2E tests Small changes here can cut runtime by 30–50%.

Automated tests aren’t about 100% coverage. They’re about confidence. Confidence to refactor, deploy, and sleep at night.

Hot take: most teams don’t need 1000s of end-to-end tests - they need better contracts between services.

Automated tests & CI/CD can either be blockers or superpowers. Done poorly, they slow teams down. Done right, they catch bugs early & keep deployments smooth.

Hacked together a proof of concept 🚀 It tackles optimizing CI testing pipelines by identifying bottlenecks and giving an opitimization strategy. Would love any honest feedback 👇 wonderful-souffle-fcd787.netlify.app

I'm thinking maybe I should just build a small micro app that solves a simple problem once a week or month. Until something sticks 🤷‍♂️

My favorite weekend mornings: wake up early, run before the sunrise, then read/learn for a couple of hours. Body + mind fueled before most people are even awake - it sets the whole day on the right foot.

The biggest question I have to myself everyday lately. Continue studying for the CISSP so I can pass the exam. That should be a big career boost. Or should I keep following my main passion and try building and scaling a SaaS again.

I spent some time building with cursor AI today. What would have taken me several months or even longer, literally took me a few hours today with AI. It's amazing how fast you can build now.

Are system tests a waste of time and effort for small teams? Or do you still see value in them?

Started tinkering with Cursor AI and hacked together CapyDash a live dashboard for your Capybara tests. Capybara doesn’t ship with a UI, so now you can watch your system tests run in real time from the browser. It only took a few hours. Not sure if it’s sustainable or useful for

I feel confident I can develop a quality software product. I just need to figure out how to get in front of people. I feel like I'm unknown and I am wasting my skills - that I have spent so much time learning. I regret building and developing in the dark for so long but I'm

Early in my career I worked in customer support at a SaaS CRM company. I dreamed of building my own SaaS one day. I had failed many many times and then I gave up for a while. But with new AI tools + Jumpstart Pro, I’ve tried again, and now I actually have an app I feel

After years of developing in the dark. This past week I made big steps in the right direction with my SaaS insightque.com. I spent 80% of my time doing outreach and discovery, 20% on development. I had promising calls/texts with several prospects who I think I can help.

I built a very simple lightweight CRM tool nothing fancy with AI yet but it works well and is very capable. I could see it adding value for small digital agencies amongs others. Would be great for tracking sales, contacts and deals. Its currently in early access and free during

Building insightque.com a simple CRM for small teams to track contacts, deals and more. Nothing fancy but it works. Big thanks to Jumpstart Pro SaaS template so nice and easy to work with.