• 30 Posts
  • 16 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle


















  • I cannot stand Python. I don’t like it. I don’t want to learn it. That’s not a fault or a deficiency, it’s a choice.

    I’m with you 100%. However, the logical next step is then to code the thing in a language you know and/or like – I’m sure there are plenty of those. It is NOT to utilize a fucking AI to code it for you in Python just because you can’t be arsed to learn Python.

    What is a problem is Linus’ decision to go ahead and “code” something on Python even though he had no intention on learning it, then using AI to code something for him that he could not troubleshoot because he doesn’t have the knowledge. That’s reckless.

    That is exactly the argument the article is making (albeit rather roundabout and colored with personal opinion, which is…fine, it’s his article, he can phrase it however he wants to). Linus would rather vibe-code the thing in Python than just bang out a couple lines of code in a language he’s familiar with.





  • Also note that the python visualizer tool has been basically written by vibe-coding. I know more about analog filters – and that’s not saying much – than I do about python. It started out as my typical “google and do the monkey-see-monkey-do” kind of programming, but then I cut out the middle-man – me – and just used Google Antigravity to do the audio sample visualizer.

    From the GitHub repo of said vibe-coded project. It appears Linus did not in fact know enough Python to code this properly and couldn’t be bothered to learn, so the writing you’re questioning is accurate.