• 1 Post
  • 56 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle



  • One of my most controversial gaming takes is that I like the first witcher game the most of the trilogy. There is a lot of jank and some cringeworthy parts but overall it feels like a much tighter experience than the later games, notwithstanding some clearly undercooked parts. It takes a lot more cues from older rpgs in how it’s structured and I suppose I might just have a weak spot for that.

    To be fair, I’ve never gotten that far in the third witcher so maybe I’d like more it if I played it enough to properly get in to it. I just got kinda bored after a dozen or so hours which is not a problem I had with the first witcher.










  • This article uses the term “parsing” in a non-standard way - it’s not just about transforming text into structured data, it’s about transforming more general data in to more specific data. For example, you could have a function that “parses” valid dates into valid shipping dates, which returns an error if the input date is in the past for instance and returns a valid_shipping_date type. This type would likely be identical to a normal date, but it would carry extra semantic meaning and would help you to leverage the type checker to make sure that this check actually gets performed.

    Doing this would arguably be a bit overzealous, maybe it makes more sense to just parse strings into valid dates and merely validate that they also make sense as shipping dates. Still, any validation can be transformed into a “parse” by simply adding extra type-level information to the validation.








  • Putting the message in git puts the information closer to the code, since the pr isn’t in git itself but instead the git forge. You can for example search the text of git messages from the git cli, or come across the explanation when doing git blame. I sometimes write verbose commit messages and then use them as the basis for the text in the pr, that way the reviewer can see it easily, but it’s also available to anyone who might come across it when doing git archeology