• 2 Posts
  • 94 Comments
Joined 11 months ago
cake
Cake day: August 11th, 2023

help-circle







  • Gotta remember it was a response to water fall. Docs didn’t mean the man page or the wiki, they ment the spec sheet, PowerPoint’s, graphs, white papers, diagrams, aggreements and contracts, etc. Where you might go MOUNTHS making paperwork before you ran a single line of logic.

    Docs SHOULD be the last resort of an engineer if your UX just can’t be intuitive in some way or some problem domain just can’t be simple. You should first strive to make it work well.

    For example Lemmy, it just would work if you needed to read the Lemmy user guide first to post on Lemmy. That would indicate bad UX, but that was how it was back in the day.





  • I mean the US healthcare market has huge amounts of regulatory and liceance capture that makes for free market healthcare impossible in the states. Its also, because of this subsidized a lot but practically forbidden to be efficient (because most of the industry is ran by for profit).

    Kind of worst case of government stepping in only to prevent meaningful markets but not to support people in need (not to say Medicare and medicaid don’t help some, they are the better example IMHO even if they pay out so bad most places practically refuse to take it).


  • I mean I made be a novice on this but multi-state service in general sounds like a bad time. Isn’t the accepted best practice for a micro service program stateless operations and one state at most per service?

    I mean its true for anything beyond a single threaded monolith right? Otherwise you just get apps that prentend to be asynchronous waiting on locks so they act totally synchronousaly.