i just made this right now, after trembling at my first professional correspondence with an old highschool friend.

  • a1studmuffin@aussie.zone
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Even when you finally think you understand how something works, it’s only temporary. Give it enough time and you’ll look back at mysterious code you wrote years ago and think “Wow, they sure knew what they were doing!”

  • Rhaedas@kbin.social
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    Realizing you may not know something isn’t a bad thing, it’s a step to understanding. The people who think they know it all regardless of the evidence presented are the problem ones.

  • sweeny@sh.itjust.works
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    1 year ago

    Both! You’re probably a lot better than you give yourself credit for but also haven’t made enough mistakes yet to see the error of your code

  • Uniquitous@lemmy.one
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    edit-2
    1 year ago

    We all are. Even the tech lead at the top of your program is only good at what he’s good at (yes he, you know how this industry be.) Nobody knows everything and most of us are just googling stackoverflow like you are.

    • sweeny@sh.itjust.works
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      edit-2
      1 year ago

      Rhetoric like this discourages women from becoming engineers, saying that a female tech lead isn’t even a possibility is pretty sexist. For the record, if you had just said “he” without the sassy parenthetical I wouldn’t have batted an eye.

      *Now that I think about it, pretty sexist is an understatement, it’s just plain sexist. Female tech leads exist, look it up, and stop perpetuating sexist ideas in tech

      • Uniquitous@lemmy.one
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I apologize. That was meant to be a humorous commiseration on the state of a profession that tends to be gender biased, but clearly I missed.

  • MasterBlaster@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    There are five levels of competence

    1. Incompetent and doesn’t know it.
    2. Incompetent and does know it.
    3. Competent and doesn’t know it.
    4. Competent, and knows it.
    5. Expert, but still often feels clueless.
    • Weirdfish@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I have 20 years experience, just cracked a project I’ve been working on for almost three years, and I still hesitate to consider myself an expert.

      Now, I’ll tell any lay person who will listen that I’m an expert, but man, some days I just feel clueless.

      I find the biggest issue I run into is lack of a peer group. I work in a large IS department, but other than one guy at my last company who works with a different language, I have no one to talk shop with.

      • MasterBlaster@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Once one gets to a high level of expertise, it seems there are fewer peers around - people who can teach something new, or give a perspective not already explored.

        It all depends on where you work, and whether there are any user groups frequented by veterans.