Currently between olives

  • 1 Post
  • 49 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle

  • Well sure that’s fundamentally true, but really doesn’t give any sort of accurate picture of how estimates are done any more than “humans are just collections of cells” does, and anybody who does estimates without using some sort of data as the basis and is purely guessing is doing it wrong as fuck.

    It’s not like we have no idea how long certain tasks have taken in the past, or what affects how long something will take.


  • XML has a bad rap because people went a bit (ok a lot) overboard with it in the early years, pretty much like what happens with a lot of other technologies, but as far as structured and human-readable data formats with good schema and tooling support go, it’s pretty much unbeatable. Now that JSON is the New Good Tech and XML is the Old Bad Tech, too many developers use JSON where XML would absolutely make more sense, and then we end up with unholy abominations like Portable Text, which is JSON pretending to be XML, and is so incredibly verbose and monumentally stupid that it feels like some sort of joke esolang data format rather than something being used in a production system. But no, here we are, god is dead and JSON is XML.

    XML is terrific for building eg. structured markup languages with more complex markup than what something like Markdown can provide, and have the resulting files be comparatively readable, at least in comparison to the JSON-based alternatives – compare HTML to Portable Text, for example. XML has such a bad reputation – partially deservedly – that people just automatically assume it’s not a valid tool for anything modern, even when the modern “NoSQL”, “structured and typed data is for nerds, suck it” JSON solution is a giant pile of shit compared to the XML alternative
















  • git gets easier once you get the basic idea that branches are homeomorphic endofunctors mapping submanifolds of a Hilbert space.

    (source)

    Edit: but to actually have content in this comment, I’m not sure the mental model is the problem. It’s not that alien that a good explanation wouldn’t help, but it took a long time for git to start paying any sort of attention to “human readability.” It was and still is in a way “aggressively technical” and often felt like it purposefully wanted to keep anybody but the most UNIX-bearded kernel hackers from using it. The man pages were rarely helpful unless you already understood git, the options were very unintuitively named, etc etc. And considering Linus’ personality, I’m not exactly surprised.

    With a little bit of more thought on how to make it more usable right from the start, I’m not sure it’d have such a reputation as it has now. The reason why I think this endofunctor joke is so funny is that that sort of explanation to “simplify” git wouldn’t have been at all out of place – followed by the UNIX beards scoffing at the poor lusers who didn’t understand their obviously clear description of what git branches are.