• nilloc@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year 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
      3
      ·
      edit-2
      1 year 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.

      • lysdexic@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        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.

        We need to keep in mind that the main value proposition of these licenses is to bar people from practicing. There is no other purpose.

        In some activities this gatekeeping mechanismo is well justified: a doctor who kills people out of incompetence should be prevented from practicing, and so do accountants who embezzle and civil engineers who get people killed by designing and building subpar things.

        Your average software developers doesn't handle stuff that gets people killed. Society gains nothing by preventing a software developer from implementing a button in a social network webapp.

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

          society gains nothing by preventing a software developer from implementing …

          I see the point you are trying to make but I respectfully disagree. Technology is at the core of seemingly every field and at the core of technology is software. Will it result in direct bodily harm? Rarely. But indirectly the impact is certainly more substantial.

          Take internet as an example. The significance of internet and information sharing cannot be disputed. Disturptions to information sharing can send ripples through services that provide essential services. Networking these days is accomplished Vida software defined networking techniques. And we are becoming more dependant on technology and automation.

          I can see why the indirect risk is not as scary as direct risk, but you have to admit, as automation is growing and decisions are being made for us, regulation of those that build these systems should not be overlooked. Professional engineers have a code of ethics they have to adhere to and if you read through it you can see the value it would bring.

          As a counter example to your "doctors are licensed to not kill people" - orthodontists, who move teeth around, pose no fatal risk to their patients. Should they be exempt from being licensed?

          EDIT:

          Just yesterday news was published by Reuters that Musk and managers at Tesla knew about defects of autopilot but marketed otherwise. If those working on it had been licensed, then negligence and decietfulness could line them up to lose their license and prevent them from working in this line again. It would bring accountability