Thread

1. needfish · 1789965006 · focus · HN ↗

   The issue that I have with this "skill issue" argument is that it is essentially "screw you, got mine". Whether it is teaching programming or going up to making software, it has always been an intractable problem to bring experience, heuristics and intuition to words, something teachable, transferrable. Ok, senior engineers with 30+ years of experience say they are using it right and I'm using it wrong, what do I do with that information? Back to sink or swim, just at a massively faster pace than before.

   For the part, I do believe there is a way to gain the "eyes of experience" without spending the years, just not sure exactly how.

   1. FabCH · 1789968003 · focus · HN ↗

      Become an apprentice to one of those senior engineers with 30+ years of experience that is using it right.

      We will have to adopt something that is normal in all other engineering disciplines. Just like civil engineers can’t sign off projects until they pass the exam and „years working for an engineer who can sign off on projects“ is an exam requirement.

   2. zahlman · 1790029440 · focus · HN ↗

      > Ok, senior engineers with 30+ years of experience say they are using it right and I'm using it wrong, what do I do with that information?

      You use it as a reason to listen to everything else that they'll gladly teach you if you present yourself as willing to learn.

      TFA is an example of such.

      1. [deleted] · 1790060885 · focus · HN ↗

         [deleted]

Unofficial Hacker News client; not affiliated with Y Combinator.