• 2 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle


  • Zangoose@lemmy.worldOPtoProgrammer Humor@programming.devGood luck web devs
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    6 months ago

    VS code is a good app in spite of using electron, not because of it. There’s no reason a simple plaintext editor needs to allocate 300MB of ram even without extensions just to launch, and there is definitely no reason a plaintext editor should require compiling chromium to build from source.

    Slack is fine, but only when you exclusively use slack. Throw in an actual browser, discord, VS Code, Whatsapp, teams (?), etc. each with their own chromium instance and now your 16GB of ram are being eaten up at idle.






  • Zangoose@lemmy.worldtomemes@lemmy.worldLies, deception!
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    7 months ago

    Tell me you’re not a software developer without telling me you’re not a software developer.

    If you’re working on the code the only thing that might change is not having access to the release/staging environments (production databases, cloud server, etc.) but you would need access to the code itself (and development database/services), so it wouldn’t be too difficult to check if the code is keeping voice recordings

    (italicized is edited in for clarity)

    Additionally, the higher up you are, the less code you usually write. With software development being higher up usually means more meetings, team management, planning, and higher level infrastructure talk.

    (Obligatory disclaimer that I’m pretty new in software development, this is the experience in the company I work at and seems to be pretty standard among other companies as well)




  • Exactly this. I’d rather use TypeScript than regular JS, but I enjoy using almost any other statically-typed language more (except maybe C++) because TS has the potential to be just as bad as JS for codebases where it isn’t being used correctly (this is true for other languages as well but it’s usually a lot more obvious).

    Not that it isn’t possible to have good typescript code, but rather that code becomes a lot harder to maintain because of problems that could’ve been prevented at a language level (truthy/falsey logic, ‘any’ type being allowed by default rather than ‘unknown,’ etc)


  • Zangoose@lemmy.worldOPtoProgrammer Humor@programming.devthe myth of type safety
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    3
    ·
    8 months ago

    In theory I’m a fan of the inferred but static typing systems that most modern languages use (kotlin, rust, TS, etc.) where most local variable types can be inferred and only return types/object fields/parameters need explicit types.

    I just despise typescript because it feels more like someone put a bandaid over JavaScript and all of its oddities instead of making a properly fleshed out language, and allowing the option for an ‘any’ type to be used freely by default emphasizes that.