• 0 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: November 7th, 2023

help-circle

  • Side note: please don’t abuse the word “toxic” until it becomes absolutely meaningless. Let’s keep that to a more fitting context, having a

    I was expressing an obviously personal opinion about the language itself, which is objectively a dull, barren wasteland that sucks out your soul while you walk it. That is precisely the reason why it’s so widespread and loved by business entities and managers - there is no excitement, no surprises, just an everlasting monotony of keys clicking produced by a horde of clones wearing button-down shirts while sitting in absolute identical cubicles, creating yet another instance of FactoryProducer. It’s very easy to plan and schedule for, while at the same time being unnecessarily verbose and mildly unproductive (compared to other languages).

    Look, the JVM is fine, just pick another language. There is plenty of work doing Kotlin. But yes, if you’re doing this only for the money, go ahead. I’ve always been unable to separate my job fromy personal life and my other interests, I couldn’t imagine being cursed by Java again.

    If you can sit somewhere for 8 to 10 hours each day, doing something that isn’t fun and separate yourself from it, not going insane, all the power to you. I also get that not everyone has the luxury of picking their favorite toy and making it their job, but I firmly believe there are options that are not Java.

    Now, if you’re one of the rare types that actually enjoys Java, meet me in the closest Denny’s parking lot, I need your cranial measurements.

    Please note: this post contains hyperbole and humor. I don’t hate any of you, I just hate Java


  • My personal recommendation:

    • Pick up Python, it’s easy to learn and highly productive. If you also learn fastAPI, you can benefit from highly validated, declarative models to build REST APIs in the backend, well fast. It will yield quick results, you won’t become demotivated and you can pick up a paid project soon.

    • Pick up Rust. It’s “in” right now and I get requests from marketing people that know nothing about programming, asking if their project could be implemented in Rust

    • Go with memorizing the shell commands first, try to understand git later. Get productive, try to get where you were with e. g. svn or cvs. If you are comfortable, look at something in depth if you have a problem that you can’t solve with the knowledge you have.

    • Fuck Java, seriously.

    • You have commercial interests, so it is probably wise to look into becoming a fullstack dev to maximize the kind of projects you can do. Look into React, vue.js, svelte. React is probably still the most widely used framework, you’ll quickly do a project with vue.js and svelte is a super interesting look into things to come.




  • Surely not. But also many employees won’t even ask for it, and change will only happen if people care about it.

    So first, raise awareness, and naturally, implement those things at any companies you manage or own.

    I’m not saying quit your job and become homeless if your employer won’t corporate with you on the issue. Everyone should think about how this could potentially affect them and what they can do within the constraints they operate in, though.

    As someone else in this thread said, a separate (VLAN, guest) network for work devices, reasonable access rules etc. can go a long way. Eventually, I would like this to become unacceptable though.



  • I know it is somewhat of an accepted practice, and a lot of people lack the means or the knowledge to handle it any other way, but I’d still like to raise awareness that you’re basically inviting a foreign actor into your network.

    The days were people would trust corporations, including their employers, to be generally benevolent and to do the right thing are long over.


  • scrion@lemmy.worldtoMalicious Compliance@lemmy.worldWork from home
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    edit-2
    4 months ago

    This is absolutely correct. Heck, you’re free to deny that based on any reasoning, maybe the shoddy icon of the work app doesn’t match your phone wallpaper.

    The phone is your private property, if an employer requires an app to be installed to do your job, they can provide a phone.

    I would also never let corporate IT manage a device, e. g. a laptop connected to my private network at home.


  • Yes, absolutely. Not all hinges are adjustable, unfortunately. In fact, I’d argue that most are not. Just have a look at the hinges at your place (doors, cabinets, toilet seat etc.), most will be very simple mechanisms with no inbuilt adjustment.

    You can adjust the play mechanically, of course - that is, through application of a certain amount of force via deformation, which can be a destructive process if not done carefully.

    There are hinges that expose an axial screw that allows for precise adjustment of hinge friction, but I have not seen those used for laptop display lids (nor did I personally encounter those in the small dimensions you would find on a laptop) . You’ll find examples of those at Misumi or McMaster - Carr.

    If your goal is to increase the friction in your laptop’s display lid hinges, you might find that simply tightening all screws of and around the hinge often does the trick. Even though the main axial screw is not meant to be user accessible, it serves basically the same function and can tighten up the hinge. Tightening the screws used for mounting will ensure the lid doesn’t wobble. You will have to (partially) take your laptop apart for that, naturally.

    If your hinge doesn’t have an axial screw at all and uses, let’s say a pin, you might have to employ another method, but that would really depend on the actual mechanism being used.


  • Absolutely, if there is enough plastic left, melting is one of the best options. That also enables mending plastic by melting in metal pins or strips via a cheap plastic welder for 10 bucks (success can be great, but it’s highly dependent on the geometry and how things broke).

    Edit: no, as I said, that’s absolutely fine if there is a chunk of sturdy plastic to accept the insert. I just wanted to present another plastic repair technique for the sake of completeness, if somebody stumbles into this comment section.




  • lspci will read the vendor and device id via PCI and use that to determine what the device is. You might want to make the output a bit more digestable / useful via lspci -s 03:00.0 -k -nn, but I’d assume the ids that match an 2070 will show up.

    Could you please take the card out and provide us with a few pictures from different angles, maybe getting a good look at the actual chips?

    I’d like to rule that out before chasing rabbits here.

    Also, you could always run nvidia-settings, which will show information about an NVIDIA card using a different access method.

    I’d still like to see the pictures of the card though ;)



  • I am aware of what you are saying, however, I do not agree with your conclusions. Just for the sake of providing context for our discussion, I wrote plenty of code in statically typed languages, starting in a professional capacity some 33 years ago when switching from pure TASM to AT&T C++ 2, so there is no need to convince me of the benefits :)

    That being said, I think we’re talking about different use cases here. When I’m talking configuration, I’m talking runtime settings provided by a customer, or service tech in the field - that hardly maps to a compiler error as you mentioned. It’s also better (more flexible / higher abstraction) than simply checking a JSON schema, and I’m personally encountering multiple new, custom JSON documents every week where it has proven to be a real timesaver.

    I also do not believe that all data validation can be boiled down to simple type checking - libraries like pydantic handle complex validation cases with interdependencies between attributes, initialization order, and fields that need to be checked by a finite automaton, regex or even custom code. Sure, you can graft that on after the fact, but what the library does is provide a standardized way of handling these cases with (IMHO) minimal clutter. I know you basically made that point, but the example you gave is oversimplified - at least in what I do, I rarely encounter data that can be properly validated by simple type checking. If business logic and domain knowledge has to be part of the validation, I can save a ton of boilerplate code by writing my validations using pydantic.

    Type annotations are a completely orthogonal case and I’ll be the first to admit that Python’s type situation is not ideal.




  • scrion@lemmy.worldtoMildly Infuriating@lemmy.worldFor security reasons
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    6 months ago

    I’m aware of that, but let’s be honest here: social and political changes are not introduced, let alone solved, by technology.

    You said it perfectly: this is about business needs. I’d like to argue to make the barrier for entry even higher (tie it to a form of citizen identity) and mandate the petition must be reviewed / acted upon once it has become significant - frameworks like this do exist already in several countries.

    Everyone has multiple email addresses today, does that not fundamentally erode the validity of change.org as a platform for direct democracy then? I do believe this is the case, so I’d love if another website would at least stop violating already existing standards and force their erroneous interpretation of how email addresses work down our throats.


  • scrion@lemmy.worldtoMildly Infuriating@lemmy.worldFor security reasons
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    2
    ·
    6 months ago

    The local parts of email addresses are standardized, and there is an RFC handling subadressing as well, see RFC 5233 - it’s not like Gmail invented this behavior.

    Also, RFC 5321 clearly states (2.3.11) that the local part of an email must only be interpreted by the receiving server, so that part should not be parsed, modified or mangled in any form - the assumptions poor web forms or validation libraries make these days are incredibly annoying and simply not compliant.

    So no, non of your suggestions are good, let alone ideal. Ideally, people would simply implement the specs and stop making lazy and false assumptions. In the case you cited, it turns out email validation is simply not the proper tool to limit how often the form can be submitted. Similar websites use e. g. text messages.