• 0 Posts
  • 201 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle

  • Which means the app was crap. Rather the rules it used to validate a valid name are garbage.

    Usually because someone tried to be too strict. E.g. names are space delimited A-Za-z strings, rather than just accepting any old Unicode string and safely processing it (e.g. with an SQL prepared statement).

    I’ve had websites reject email addresses with one of the newish TLD’s because someone decided they new how to validate an email address (it’s more a more flexible spec than you might think).


  • That’s conforming (to what ever criteria). Send me a UTF-16 string of at most 100 code points. Send me a 7-bit ASCII string of only A-Z0-9. Reject anything that doesn’t comform.

    sanitizing is trying to clean an input. That’s “lemme just double escape some special characters” or stripping/replacing/encoding characters or truncating strings, coercing types. Don’t do this, your sanitization code will have bugs or edge cases.







  • 100%

    Excel is the one actual critical application because it deals with data (and formulae), data which is only useful when you maintain its integrity (hopefully you’re not storing dates).

    Word is just a shitty application for text. Needs that can usually be adequately addressed by a plain text file (or plain text email). It thinks it’s a desktop publishing application (goodbye MS Publisher). Any tool that can do rudimentary text processing will suffice for the vast majority of use cases. One might have footnotes and some meta data that might be important, other apps do that well. Even markdown can do that.

    PowerPoint, likewise, is a shitty slide show application. Any equivalent will suffice.

    There’s quite a few other apps, I forget those.











  • deadbeef79000@lemmy.nztoProgrammer Humor@programming.dev: (
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    17 days ago

    Use a CHAR(1) you can then use it as an enumeration.

    Don’t use T/F for true/false use it for the actual sematic meaning for the thing that the Boolean is toggling. E g. S for subscribed, U for unsubscribed, or whatever.

    It also means when you inevitably grow to needing a tri-state it makes sense.

    Unless SQLite actually supports enumerations, then just use them