This article is not about error screens or user experience. It is about how development-level decisions can protect our customers from impossible scenarios and give the developer more confidence while writing code.
View More
For software development teams, the moment we stop learning is the moment our technical stack starts becoming obsolete. It’s not about how many languages or tools we know. It’s about how quickly we adapt when they evolve, get replaced, or transform…
View More
"Done": A Dangerous Word? In Software Engineering, the word “done” might seem simple, almost obvious. In reality, it can be deceptively slippery. What’s “done” for a developer implementing a feature may not be the same as what’s “done” for QA,…
View More
In our latest blog article, we explored the practice of dogfooding and how company-wide, in-house testing helps us sharpen product quality and ensure the best possible experience for our clients. But testing is only one side of the equation. If…
View More
In the fast-paced world of software development, it’s tempting to push features out the door and rely solely on QA teams or early adopters to find the cracks. But we, at Blip, swear by a different approach: dogfooding. Eating our own dog food means…
View More
On Growing Something Coherent in a Wild, Thorny Landscape Hugging a cactus is a good analogy to describe the first assignment of the newly created Design Systems team at Blip. It’s not that we dislike cactus, on the contrary. Some of our team…
View More