This is where we think out loud. Essays, deep-dives, and post-mortems from the team that builds software for a living — written for the people who do the same.
We don't publish "Top 10 AI Tools You Need in 2026" listicles. Our posts come from real projects, real bugs, and real decisions we've had to defend to a client. Every article falls into one of five buckets:
Engineering Deep-Dives
Architecture decisions, database design, performance tuning, and the trade-offs behind them.
Product Craft
How we scope, plan, and ship features. Notes on product thinking from inside a small studio.
Post-Mortems
Bugs that taught us something. Outages we caused. Lessons we now bake into every project.
Tooling & Workflow
The editors, CI pipelines, and testing setups we actually use day to day — not what we'd endorse in theory.
Industry Perspective
Opinionated takes on trends that affect our clients — with data, not vibes.
Client Case Notes
Anonymised write-ups of real projects — what worked, what we'd do differently next time.
From Sample to Insight – The Story of Helix LIMS Laboratories are the backbone of diagnostics, research, and quality control. Yet, many labs still struggle with fragmented workflows: pa...
Read More →
Behind the Scenes: Drassine's POS Software Every retail business – whether a small boutique or a sprawling supermarket – faces the same challenge: how to manage sales, inventory, and ...
Read More →
Why We Built Our Own Document Conversion Engine Every modern software company eventually faces the same dilemma: we need to handle documents – merge, split, compress, convert – but ex...
Read More →
Artificial Intelligence is not just a trend — it's a paradigm shift. Over the past decade, AI has moved from academic research to production-grade tooling. At Drassine, we integrate AI-...
Read More →
Great UX is not just about aesthetics it's about productivity. In enterprise environments, poor user interfaces lead to costly errors and low adoption rates. At Drassine, we treat UI/UX...
Read More →
We turn your vision into reality, step by step. Our 8?stage Digital Product Lifecycle SOP is the blueprint for every project we undertake. It ensures clarity, alignment, and quality at ev...
Read More →Every article on this blog is written by someone who has actually built the thing they're writing about. No ghostwriters. No AI-generated filler. No "content strategist" recycling what they read on Twitter.
Posts are drafted, reviewed, and edited by at least two members of our engineering team before publishing. If a claim can be measured, we measure it — you'll see real numbers, real screenshots, and real trade-offs, not just confident assertions.
Where we're uncertain, we say so. Where we made a mistake, we correct it publicly and note the edit at the bottom of the post. We don't quietly delete things when we're wrong.
Our target length is 1,500–2,500 words — long enough to be useful, short enough to respect your time. If a topic needs more, we split it into a series. If it needs less, we publish it as a short note and save you the scroll.
We write for four kinds of readers. If you're one of them, you'll feel at home.
Developers, SREs, and tech leads who want technical depth — not another "5 coding hacks" post. Expect architecture diagrams, code snippets, and honest trade-off discussions.
People building companies who need to make informed calls on stack choices, hiring, and outsourcing without wasting a quarter learning the hard way.
PMs who work closely with engineering teams and want to understand the constraints we deal with — from dependency hell to migration fatigue.
Business owners who've hired us (or are considering it) and want to see how we think before they commit. No sales spin — just the work itself.
Roughly twice a month. We'd rather publish one thoughtful piece every two weeks than five rushed ones every week. Some months we publish more — especially when a project gives us something worth documenting.
Yes to both. Topic suggestions go to our editorial list — if enough readers ask, we write. Guest posts are considered case-by-case and must be original, technical, and non-promotional. Reach out through our contact page with the subject line "Blog Pitch."
No. We don't accept sponsored posts, paid link insertions, or affiliate placements. If we recommend a tool, it's because we actually use it — not because we were paid. This is non-negotiable.
With attribution and a link back to the original post, absolutely. Reach out first so we can approve the format. We ask that you don't modify the content or republish it commercially without written permission.
No. Every post is written by a human engineer. We sometimes use AI tools for grammar checks and code samples, but the thinking, structure, and voice are ours. We believe that's why our readers keep coming back.
One email per post. No tracking pixels, no marketing funnels, no upsells. Unsubscribe with one click at any time.
We never share your email with anyone.