blogtopus

Shared auth state for test runs, custom variables and environments for separate deployments: 8 features you requested, one hairy step in the agent progress and new treats for more advanced web development set-ups.

An Octomind tutorial for developers who want start end-to-end testing. Let me show you what getting up to speed with Octomind looks like so you can see if it’s something you’d want to try out for your own websites or apps.

A backlog is a collection of tasks that aren’t important enough to do. If they were, we wouldn't be stashing them away. After years in software development I’ve come to see backlogs as more of a hindrance than a help.

When abstractions do more harm than good - lessons learned using LangChain in production and what we should’ve done instead.

Flaky e2e tests are frustrating for QA and development teams, causing constant disruptions and eroding trust in test outcomes. A fail-safe checklist for how you can tell the difference.

We've raised $4.8 m to reinvent testing with AI. Led by Cherry Ventures, the round supports the developer tool’s ambitions to create a bug-free future for AI-assisted software development and testing.

When done right, end-to-end tests are invaluable tools for comprehensively testing a backend. Working e2e tests is in everyone’s interest, whether you are on frontend, backend, engineering or QA.  

To build a better way of testing we needed a testing framework to complement our AI agents. Our ideal end-to-end testing tool would help build high quality apps fast.

How do we get quality back on track while keeping the productivity benefits of tools like Copilot? After all, degrading quality undermines delivery speed and neutralizes some of the gains, if not most.

A case study of creating personalized AI generated gifts for your team, friends and family 🎄🎁  I created this blog to share with Octomind friends, users and fans. This is our special, genAI way of saying: thank you.

Post mortem on a weekend of missed opportunity. What we've learned on moving fast and making sure we don't break things thanks to an unexpectedly viral blog posted to a subreddit on a Friday afternoon.

Software testing is littered with strong opinions and i'm no different. What, when, who, how and if to test at all is the subject of heated discussions. About the one dogma I'm guilty of - testing what you've built.

Deploying on Fridays is a legend of programming memes - a practice only fools engage in. Being completely averse to Friday releases can come across as dogmatic. My take #3 on popular developer dogmas.

An attempt for reconciliation between TypeScript lovers and haters. I’m firmly in the TypeScript camp. However, using typescript is also not an absolute.

Opinions in software engineering have gotten more extreme lately. I'll use some notorious examples to show that nuance is an essential engineering principle.

The unpredictable and non-deterministic nature of LLM output makes ensuring type safety hard. Lessons I learned about parsing and error handling of LangChain.

Change is ubiquitous in software development. New languages, tools and frameworks are everywhere. Yet the one thing unwilling to move is the Testing Pyramid.