robertandrewp

3 ms·

1. 1.▲
   by robertandrewp 7mo ago

   The .xlsx experience is even messier in a business context. I work daily across Windows and Mac, and my two worst offenders are Excel and QuickBooks. Excel on Mac has been closing the gap, but VBA macros from Windows colleagues still break
2. 2.▲
   by robertandrewp 7mo ago

   The "one of the greatest inventions in computing" framing holds up when you look at what it actually did to financial math accessibility. I've been implementing the functions Lotus 1-2-3 made mainstream as a REST API — amorti
3. 3.▲
   by robertandrewp 7mo ago

   One approach that sidesteps the whole problem: design for fully synchronous, stateless requests from the start so there's nothing to queue. I did this for a financial calculator API — every request is pure computation, inputs in, resul
4. 4.▲
   by robertandrewp 7mo ago

   AstroBen's framing matches my experience — "well-specified + verification harness" really is the sweet spot. Financial math is about as well-specified as a domain gets: the amortization formula is unambiguous, expected output
5. 5.▲
   by robertandrewp 7mo ago

   Working as an accountant in a services industry, inventory has been the thorn in my side. The ERP package that I manage and work on daily has some limitations on inventory control, possibly a signal to change packages, but other than the in