It was a bizarre disconnect having someone be both highly educated and yet crippled by not doing.
It was a bizarre disconnect having someone be both highly educated and yet crippled by not doing.
The students had memorized everything, but understood nothing. Add in access to generative AI, and you have the situation that you had with your interview.
It's a good reminder that what we really do, as programmers or software engineers or what you wanna call it, is understanding how computers and computations work.
> The first principle is that you must not fool yourself and you are the easiest person to fool.
I have no doubt he'd be repeating it loudly now, given we live in a time where we developed machines that are optimized to fool ourselves.It's probably also worth reading Feynman's Cargo Cult Science: https://sites.cs.ucsb.edu/~ravenben/cargocult.html
Star Trek or Idiocracy.
Makes me wonder if C programmers look at JS programmers and shrug, “they don’t understand what their programs are actually doing.”
I’m not trying to be disingenuous, but I also don’t see a fundamental difference here. AI lets programmers express intent at a higher level of abstraction than ever before. So high, apparently, that it becomes debatable whether it is programming at all, out whether it takes any skill, out requires education or engineering knowledge any longer.
Just checking I have that right... is that what you meant?
I think that's what you were implying but it's just want to check I have that right? if so
... that ... is .... wow ...
Knowing the complexity of bubble sort is one skill, being able to write code that performs bubble sort is a second, and being able to look at a function with the signature `void do_thing(int[] items)`and determine that it's bubble sort and the time complexity of it in terms of the input array is a third. It sounds like they had the first skill, used an AI to fake the second, but had no way of doing the third.