Comments by "" (@retagainez) on "ForrestKnight" channel.

  1. And that problem has existed for forever. I think it's a matter of the skill floor for seniority has significantly lowered. None of the "seniors" are senior enough to teach!
    7
  2. Yeah. Not entirely a unique issue when you look at it this way.
    2
  3.  @juancriolivares  Not gonna lie. This is a poor interviewing tactic, at best.
    1
  4. To be fair, relying on AI to test your code is probably a contributing factor to "not being able to code." There's a significant correlation to poorly-tested & poorly-designed code to production outages. In that sense, we will surely struggle and pay for the price of it no matter what skill level you are. You will have to fix old tech debt, read obscure code, and do it all in an untested codebase.
    1
  5. To be fair, I don't understand how spoon-feeding you a program language is any different. It doesn't teach you how to think. At best, it teaches syntax. So, from a very accessible perspective, teaching your students prompt engineering is very much the status quo of the same teachings University would've taught pre-GPT.
    1
  6.  @MrVanshajSaxena  I agree to a point. The struggle is important, if well-timed and deserved. Excessive struggle is more of a symptom of trying to do something unsupported or more bleeding edge than usual. That sort of thing has a six sense to it
    1
  7. Perhaps the most fundamental unchanging aspect of programming, even during the GPT era.
    1