• varsock@programming.dev
      link
      fedilink
      arrow-up
      12
      arrow-down
      4
      ·
      10 months ago

      to add to this, id like standardization of qualification and competencies - kind of like a license so I don’t have to “demonstrate” myself during interviews.

      I hate being in a candidate pool that all have a degree and experience, we all go through a grueling interview process on college basics, and the “best one gets picked.” Company says “our interview process works great, look at the great candidates we hire.” like, duh, your candidate pool was already full of qualified engineers with degrees/experience, what did you expect to happen?

      • v_krishna@lemmy.ml
        link
        fedilink
        English
        arrow-up
        13
        arrow-down
        2
        ·
        10 months ago

        I’m betting you aren’t involved in hiring? The number of engineers I’ve interviewed with graduate degrees from top universities who are fundamentally unable to actually write production quality code is mind-boggling. I would NEVER hire somebody without doing some panel with coding, architecture/systems design, and behavioral/social interviews.

        • RonSijm@programming.dev
          link
          fedilink
          arrow-up
          7
          ·
          10 months ago

          This. I’ve had someone in my team that was completely self-taught with no relevant education that was a great dev.

          I’ve also interviewed someone that supposedly had a master degree and a couple of certificates and couldn’t remember how to create a loop during the interview.

          I don’t know how you could properly implement “standardization of qualification and competencies” without just min-maxing it in a way that favors academics

          • varsock@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            10 months ago

            good question. Software and computer practices are changing much faster than other fields but with time, pillars are being better and better defined. Production quality code, CI/CD, DevOps, etc…

            Civil engieers have a successful licensure process established. See my comment regarding that.

            But an approach where a candidate would spend time under a “licensed professional software eng” would favor practical work experience over academic.

        • thelastknowngod@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          10 months ago

          As a counter balance to that though, interviewers need to understand what they are hiring for and tailor the questions asked to those requirements.

          For example, there is genuinely very little coding required of an SRE these days but EVERY job interview wants you to do some leetcode style algorithm design… Since containers took over, the times I have used anything beyond relatively unremarkable bash scripts is exceptionally small. It’s extremely unlikely that I will be responsible for a task that is so dependent on performance that I need to design a perfect O(1) algorithm. On terraform though, I’m a fucking surgeon.

          SRE specifically should HEAVILY focus on system design and almost all other things should have much much less priority… I’ve failed plenty of skill assessments just because of the code though.

        • nilloc@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          0
          ·
          10 months ago

          Programming should be more like other trades, apprentice for a year or two before getting journeymen status, then work up to master status. Pay and job changing becomes more fair, and we get some reasonable fucking hours and rules to keep us from making overworked mistakes.

          Companies know what they’re getting asked on the programmer’s level (specific experience will still matter, but baseline will be much more standard).

          And workers get experience and learn from the gray beards instead of chatgpting their way into a job they don’t understand.

          • varsock@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            10 months ago

            the trades is a great example of having to work under a professional. Other engineering disciplines also have successful licensure processes. See my comment regarding that.

            There are parallels to be drawn between licensed professionals (like doctors, CPAs, lawyers, civil engineers) that they all have time under a professional and the professional then signs off and bears some responsibility vouching for a trainee.

  • aport@programming.dev
    link
    fedilink
    arrow-up
    28
    arrow-down
    2
    ·
    10 months ago

    Attention and awareness of the ways in which modern technology is harming ourselves.

    We’re providing people with the electronic equivalent of heroin, from a young age, completely rewiring our brains and detaching us from nature and each other.

    • onlinepersona@programming.devOP
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      1
      ·
      10 months ago

      The statistic that ~90% of American teens own an iPhone was shocking to me. It makes me think that from a young age, children are taught not to question but just accept their cage. If closed source is all they grow up with, opensource will be foreign to them. And that in a way that’s worse than when you grow up with windows which doesn’t completely lock you in.

    • fuck_u_spez_in_particular@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      10 months ago

      This! I feel it myself, my ADHD was much better when I stayed in a relatively natural setting with only little technology. for a few weeks (I did some programming there though, and boy was I focused in complex problems without medication etc. had one of my best coding sessions there I think). I’m pretty sure that a lot of ADHD but also other psychiatric issues like autism or social anxiety etc. that is diagnosed these days is because of all this unhealthy environment we have created. Or in other words, our modern technology promotes psychiatric issues such as ADHD, autism, social anxiety etc.

  • Gabadabs@kbin.social
    link
    fedilink
    arrow-up
    23
    arrow-down
    1
    ·
    10 months ago

    More focus on the ability to maintain, repair, and perhaps even upgrade existing tech. So often people are pushed to upgrade constantly, and devices aren’t really built to last anymore. For example, those yearly trade in upgrade plans that cell phone providers do. It sucks knowing that, once the battery in my cell phone finally dies, the whole phone is essentially garbage and has to be replaced. I miss my older smartphones that still had replaceable batteries, because at least then it’s just the battery that’s garbage.
    We’re throwing so much of our very limited amount of resources right into landfills because of planned obsolescence.

    • onlinepersona@programming.devOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      10 months ago

      I think the solution to this will come by itself: the supply chain will break down and people will have to learn to make do with what they have. It was like that in the Soviet Union, is like that in some parts of the world right now, and can easily return if we don’t get climate change in check.

  • RonSijm@programming.dev
    link
    fedilink
    arrow-up
    23
    arrow-down
    3
    ·
    10 months ago

    Probably less elitism. “Oh you build it in x language? Well that’s a shit language. You should use y language instead. We should be converting everything to y language because y language is the most superior language!”

    (If this feels like a personal attack, Rust programmers, yes. But other languages as well)

      • RonSijm@programming.dev
        link
        fedilink
        arrow-up
        3
        ·
        10 months ago

        Well sure, it depends on the context. If it’s a shitpost on /c/programmer_humor, whatever, meaningless banter.

        If it’s a serious question, (maybe for a beginner) asking how to do something in their language, and the response is “It would be a lot easier in y language” - I don’t think it’s particularly helpful

    • huntrss@feddit.de
      link
      fedilink
      arrow-up
      3
      ·
      10 months ago

      C’mon, a little bit of flexing is so nice.

      But, I get what you’re saying. I usually filter out this bullshit (because I’m a Rustacean myself 😜) but this doesn’t mean that it is as easy for someone else as it is for me.

    • SorteKanin@feddit.dk
      link
      fedilink
      arrow-up
      2
      ·
      10 months ago

      As someone who’s quite vocal about my support for Rust, I can definitely see how it can go overboard.

      But on the other end of the spectrum, saying that all languages are just as good or capable and it doesn’t matter which one you use is definitely wrong. There are meaningful differences. It all comes down to what your needs are (and what you/your team knows already, unless you’re willing to learn new stuff).

      • RonSijm@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        Yea, I kept my original comment language-agnostic (Just referring to it as y language) - but added the extra wink to Rust because generally they seem to be the highest offenders.

        I have years of experience in loads of languages: PHP, Ruby, Java, Python, C#, C++, Rust - And that’s probably how I’d order the level of elitism. PHP Devs know everything they’re doing is shit - Python should probably be next in ranking of how shit they are, but they’re not self-aware enough - (Sarcastic elitism aside here - )

        Anyways, besides that - at the end of the elitism-spectrum there seems to be Rust. Someone like me says something about Rust in a general unrelated-to-Rust thread like this - and a Rust enthusiast sees it, and it would just devolve into a dumbass back-end-forth about how good Rust is

  • profoundlynerdy@programming.dev
    link
    fedilink
    arrow-up
    20
    arrow-down
    1
    ·
    10 months ago

    A pivot way from cargo cult programming and excessive containerization towards simplicity and the fewest dependencies possible for a given task.

    Too many projects look like a jinga tower gone horribly wrong. This has significant maintainability and security implications.

  • Falst@lemmy.world
    link
    fedilink
    arrow-up
    18
    ·
    10 months ago

    More privacy and less profit 🫣

    I realize most people could rather not pay for a service they currently have for free (which is partly due to the lack of transparency regarding our data usage).

    • onlinepersona@programming.devOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 months ago

      It’s possible that a donation based-society might work. However, I’m not sure how that can be achieved in parallel to a profit-based society (the on we majorly have to take part in).

      IMO one way is to force the issue by making certain methods of profit impossible or not worth it in the long run. Something like “don’t use it? you lose it” in terms of patents or proprietary solutions. For example if a company stops producing and supporting something, then it has to release the designs, code, and intellectual property to the public.

      • Spazsquatch@lemmy.studio
        link
        fedilink
        arrow-up
        2
        arrow-down
        5
        ·
        10 months ago

        It’s inefficient, there are many alternate layouts that are “better”. I feel like AI is going to give us auto-fill that makes the keyboard efficiency less important though.

        • onlinepersona@programming.devOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          10 months ago

          How is it “inefficient”? There are many keyboard layouts out there for different languages. DVORAK also exists, which supposedly is better.

          I’d argue that the mode of entry of inefficient, not the layout. There’s a lot of movement for a finger to reach a key. Much of that movement could be reduced. An example thereof is the CharaChorder

          • Spazsquatch@lemmy.studio
            link
            fedilink
            arrow-up
            1
            ·
            10 months ago

            I read OP’s comment as indicating they wanted tech to move to alternative layouts from QWERTY, and the argument is always improved wpm.

            I type slow as hell, I don’t have a dog in the fight.

  • j4k3@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    10 months ago

    Data is a part of a person’s individual self. Storing such data on another person is owning a part of their person. It is slavery for exploitation, manipulation, and it is wrong.

    This distinction is the difference between a new age of feudalism with all of the same abuses that happened in the last one, or a future with citizens and democracy.

    Never trust anyone with a part of yourself. Trust, no matter how well initially intentioned, always leads to abuse of power.

    • sbv@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      ·
      10 months ago

      I agree with the sentiment that personal data is owned by whoever it is about. And that other organizations shouldn’t be able to exploit it.

  • porgamrer@programming.dev
    link
    fedilink
    arrow-up
    13
    ·
    10 months ago

    Three things off the top of my head:

    • Unionisation
    • Way more stuff publicly funded with no profit motive
    • Severe sanctions on US tech giants all around the world, with countries building up their own workforce and tech infrastructure. No more east india company bullshit.
  • PM_ME_VINTAGE_30S [he/him]@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    11
    ·
    10 months ago

    Boot out corporate shitware, boot out adverts, and stop collecting data unless it is absolutely necessary, or alternatively just cancel the fucking product and don’t do it.

  • librecat@lemmy.basedcount.com
    link
    fedilink
    arrow-up
    8
    ·
    10 months ago

    Accessibility and internationalization first. A lot of projects start without it and tack it on later. It’s so much better to have good roots and promote diversity and inclusivity from the start.

    • RonSijm@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      10 months ago

      Could you elaborate in what context and to what extend? I can agree that bigger companies with large user-bases should have a focus on accessibility and internationalization -

      But generally a lot of projects start with just one dev solving a problem they have themselves and make their solution Open-Source. Anecdotally, I’m dumping my solutions on Github that are already barely accessible to anyone somewhat tech-illiterate. No one is paying me anything for it. Why would I care whether it’s accessible or internationalized for non-English speakers?

      • librecat@lemmy.basedcount.com
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        As a solo developer, some things are out of scope like writing translations or ensuring full compliance with accessibility standards. What’s important is to have some knowledge of what things block progress in these areas. For example, not treating all strings like ASCII, or preferring native widgets/html elements as those better support accessiblity tools.

  • UFO@programming.dev
    link
    fedilink
    arrow-up
    8
    ·
    10 months ago

    ISO-8601 only

    UTF-8 only

    UTC only

    Oh and more self hosting. Clouds are expensive and unnecessary for some stuff.

  • Jack3G@sh.itjust.works
    link
    fedilink
    arrow-up
    6
    ·
    10 months ago

    Honestly, just less waste. Wasted time, wasted hardware, etc. We spend so much time building devices that are meant to break, and be unfixable, and making software that fights the user instead of helping. All in the name of profits or something.

    We could be making so many cool things, but instead we’re going back and forth not making any progress.