2 ms·
Yeah. Maybe what I’m calling “annoying” is what makes it “difficult”. The features and ideas billing usually needs aren’t “difficult” to write, but if you have
by wredue 3y ago
Yeah. Maybe what I’m calling “annoying” is what makes it “difficult”.
The features and ideas billing usually needs aren’t “difficult” to write, but if you have someone inexperienced designing the system, your project is inevitably going to run face first in to these “annoyances” and this may present as somewhere between difficult and impossible where if you had an experienced person at the helm from the get go, you won’t be running in to the same issues.
Yeah. I guess the iceburg will present as difficulty in some ways.
- doctor_eval 3y agoYeah, I don't disagree. There are a small number of "actually difficult" problems but the vast majority are run-of-the-mill. For example when presenting an invoice, you end up needing to be able to access just about any part of the system. In telco you need the invoice, line items, past payments, CDRs, entitlement, pre-paid, ... Without a global data model this becomes really complicated. It's not hard (we settled on GraphQL), but it ends up being big. And it needs to be pretty fast, too.