Wingravity
Most people who commission software have no direct way to check what they actually received. You can open the app, click through the screens, and see that it does roughly what it was supposed to do. What you cannot see is how it was put together underneath, whether anyone other than the original team could work on it, or what happens the first time it comes under real load. The people best placed to answer those questions are usually the same people who built it, which becomes awkward the moment…
The sentence that stayed with me I asked a client once why he chose us over an agency twice our size. He told me something I still think about today: "You answered in four hours. The other agency needed four meetings just to answer anything at all." That sentence stuck with me the way a good story sticks with you, the kind you replay in your head weeks later because it captures something true about how the world actually works. The customer service line we all know too well Think ab…
The symptom A content platform, a directory-style site with thousands of dynamically filtered listing pages, was showing serious performance problems in a routine site audit. A full crawl of roughly 6,000 pages, combined with PageSpeed Insights (PSI) API data, turned up two things that looked unrelated at first glance: - Server response times were bad, and occasionally catastrophic. Median time-to-first-byte (TTFB) sat around 0.7 seconds, with over 1,500 pages taking longer than a s…
Inside Showslide’s new Faculty Partner Program There is a precise moment that every university lecturer knows by heart, you are mid-slide, mid-thought and mid-sentence when you glance up at the room. Some students are locked in, while many others are somewhere else entirely. Their phones are face-up on their desks, or their laptops are open to a browser tab that has absolutely nothing to do with your course material. This is happening because the traditional, one-way lecture format gives th…
The title arrives faster than the clarity. One day you are an engineer who happens to be trusted, and the next you are a CTO with a business card that implies you know exactly what you are doing. You don't, not yet, and that is fine. Nobody does in the first few months. The most common mistake I see in first-time CTOs is acting out a role they have only watched from a distance. They picture the CTO of a five-hundred-person company, with the architecture review boards and the quarterly planning …
There is a particular kind of friction that accumulates slowly in remote work, the kind that never quite makes it onto a retrospective board because it feels too small to name. You don't lose a deal over it. No incident report gets filed. But it shows up, meeting after meeting, in the tiny hesitations, the apologetic messages, the "can you just share your screen instead?" workarounds that everyone accepts as normal without ever questioning whether they should. For us, it showed up in three spec…
Think about the last person at work who genuinely impressed you. Not the one who knew the most, or had the longest resume, but the one you'd go to when something was broken and no one knew how to fix it. The one who could walk into an awkward meeting and somehow make everyone relax. The one who, when you described a vague problem, came back with three approaches you hadn't considered. What was it, exactly, that made them that way? We reach for words like _smart_, or _experienced_, or _a good co…
Building internal tools often starts with frustration. For our team, it began with two recurring problems: the opaque permissions of our project management system and the sluggish interface that made even small tasks feel like a chore. We needed a tool that could combine project management and operational reporting. Something that allowed us to track work, understand priorities, and maintain context without fighting the tool itself. At first, I tried to bend existing platforms to our will. Ji…
Most business logic ends up hardcoded deep in your app, and it’s slowly killing your codebase. What starts as a clean service grows into a bloated mess of if-else statements, feature flags, and ad-hoc patches no one dares touch. Before long, your services are "absolute units", ORM models do way more than map data, and you’re moving data back and forth like an unpaid intern, not a software engineer. How did we get here? The real problem: Business logic is treated like an afterthought When …
