• 2 Posts
  • 294 Comments
Joined 1 year ago
cake
Cake day: December 31st, 2023

help-circle









  • The technology behind the registry is fine (which is what I think @VinesNFluff meant)

    But it’s execution in Windows was ass

    In theory, a configuration manager with DB-like abilities (to maintain relationships, schematic integrity, and to abstract the file storage details), isn’t a bad idea

    But the registry as it is today is pure pain




  • Lightfire228toComic Strips@lemmy.worldisitdownrightnow dot com
    link
    fedilink
    arrow-up
    33
    arrow-down
    2
    ·
    1 month ago

    Software dev here,

    It doesn’t stop you from typing code, but it does drastically hinder the process. You often need to pull up technical documentation (for the language, framework, platform, etc), or search the internet for things, like “C# HttpClient how to serialize JSON with a different naming policy”

    Not to mention, if any of your dev resources are online, no Internet prevents you from running your code. Like, if you need to connect to an S3 bucket, AWS instance, or Azure Database





  • Lightfire228toProgrammer Humor@lemmy.mlCommit
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    2 months ago

    I mean, you just need to look at the conflicting files, fix up the code, then stage those changes and pop a new commit

    There’s no “special” merge conflict resolution commit “type”


    As for fixing the code itself, I usually look at what changed between both versions, and then re-author the code such that both changes make “sense”