Full stack developer and privacy advocate. I like to keep the mentality, if you can program one language well, then you can program in any language!

  • 0 posts
  • 19 comments
Joined 3 years ago
Cake day: June 15th, 2023
  • By not accepting your time estimate,
    requesting your reasoning why it takes that long, you explaining you calculated time in for refactoring, then rejecting your idea and granting you only time to implement the new thing, without granting time for refactoring.

    And dw, my project manager is a pretty chill friend and fellow senior developer, who is reasonable and helps me with calculating in time for refactoring whenever possible/nessecary.

    It’s only higher up, CEOs/management, who seek to cut corners, with rocks for brains, who don’t see that in the long run such practices are bad for business.

    Which sadly is the case for most IT businesses. But at least in my workplace the project manager is not a rat & on the side of the developers.

  • Just increase your time estimate,
    calculate in the time needed to refactor,
    but don’t tell them you’re gonna refactor.

    Works out most of the time.
    Only when they ask why the estimate is so long, then you explain your reasoning behind it, and then they might reply with your statement and block your refactoring idea.

    However, getting time to refactor most of the time, is aleady way better then never being allowed to do so.

  • WASM = WebAssembly,
    this has nothing to do with Java,
    but with JS (JavaScript).

    JS works with JIT (Just In Time) compilation, meaning every user that requests a web page, will request the JS and your browser will compile that JS on the fly as you request it.

    WASM on the other hand is pre-compiled once, by the developer, when he/she is making the code. So when a user requests a WASM binary, they don’t have to wait for JIT compilation, since it was already pre-compiled by the developer.

    They only have to wait for a tiny piece of JS,
    which is still JIT compiled,
    a tiny piece of JS to load in the WASM binary.

    This saves the user from waiting on JIT compilation and thus speeds up requesting web pages.

    WASM also increases security,
    since binaries are harder to reverse engineer then plain text JS.

    Due to those reasons,
    I believe WASM will be the future for Web development.

    No clue why people are hating on WASM,
    but I guess they just don’t grasp all of the above yet.

  • Not on my machine. Or at least, I do everything humanly possible to limit it.

    Either through:

    • Switching to FOSS alternatives
    • Custom patches applied to proprietary binaries.
    • Blocking network access for certain processes

    I don’t expect everyone to become a privacy expert though.

    However I do believe systematic privacy is important, and that we should aim for better privacy laws to keep the intellectual property of the average user safe.

  • Now they can also train their gray area trained model (trained upon our Github projects without consolidating with us if it was alright to do so) further!

    By spying on every command you type in your CLI, and phoning home to MS about it, to train it further.

    I guarantee you,
    If you use it, you’ll be their free training monkey.

    And once they used you for free,
    and the product improved enough,
    they’ll subscription charge you forever to make use of it.