Writing
Practical writing on Java, system integration, databases and financial technology, drawn from systems we actually run.
Most performance advice is written for fast phones on cheap data. Here is what changes when your users are on mid-range Android handsets paying per megabyte, and why we removed the framework from this site.
What actually changes when you write financial software for Zambia: statutory deductions that are not what most payroll engines assume, mobile money as a first-class payment rail, and decimal arithmetic you cannot afford to get wrong.
Connecting two systems is easy on the happy path. What costs time is duplicate deliveries, partial failures, and the hour the other end is down. Here is how to design for those from the start.
Why we build back ends on Java and Spring Boot, why this site has no framework at all, and how to tell which of those two situations you are in.
Why expense claims break down at around thirty people, what an automated system actually has to do to fix it, and the failure modes that make replacements stall.
Not an OWASP recitation. The handful of weaknesses that account for most real compromises of small business systems here, and what fixing each one involves.
Tell us what you are trying to fix and we will reply with an honest view of whether we are the right people for it.
eLucive Software · Lusaka, Zambia