See, for example,
https://youtube.com/playlist?list=PLrMvJfuADfNUx6s3PEFaraQP7...
679 karma · joined November 13, 2011
See, for example,
https://youtube.com/playlist?list=PLrMvJfuADfNUx6s3PEFaraQP7...
My point is that your claim is unsubstantiated.
Unoptimized code would easily take tens of minutes to render the Mandelbrot in 640x480x256 on a 486. FractInt (written by Ken Shirriff) was fast, but would still take tens of seconds, if not longer -- my memory is a little hazy on this count.
Good luck, again!
This, instead of actually thinking yourself, and examining your own biases - or those of the people who wrote what you read
Right. Good luck!
Hell, maybe making today's tech workplace more about getting work done instead of the series of ritualistic performances that the average tech workday has degenerated to might help too.
Ergo, your conclusion doesn't follow from your initial statements, because interviews and workplaces are both far more broken than most people, even people in the tech industry, would think.
Question 2: Do you think this will ever become valuable?
Perhaps not when the code is getting written (by yourself or by an AI).
When you're dealing with a memory leak in production (yes, they can and do happen), or worse -- if you're dealing with a drop in performance -- good luck with the vibe debugging.
Maybe there will be a time not too far off in the future when the stochastic cockatoos become sentient enough to do all of this by themselves, it's sure as hell not happening tomorrow.
Oh, and logarithmic tables were still a useful thing as late as forty odd years ago :)
Either way, I loved the joke. Thank you!
More and faster, yes. Almost never better.
(Not trying to be sarcastic, this is genuinely the best reason I can think of)
Edit: made a change for completeness.
You're right, each of us have differing motivations. That doesn't give anyone license to promote their own point of view and tar everyone else with the same brush.