Instructor, author, developer. Creator of Beej’s Guides.

openpgp4fpr:CD99029AAD50ED6AD2023932A165F24CF846C3C8

  • 0 Posts
  • 15 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle







  • A shell script can be more concise if you’re doing a lot of shell things. Keeps you from having os.system() all over the place.

    Things like “diff the output of two programs” are just more complex in other languages.

    I love rust, but replacing my shell scripts with rust is not something I would consider doing any more than I’d consider replacing rust with my shell scripts.







  • I see new workers there struggle a lot because they don’t try to understand what’s wrong and just want a fed copy paste solution to make the problem go away.

    I see that in my students a lot, as well. I’ve been hammering away that the goal (in school, but frankly in general) is not actually to solve the problem. It’s to learn to solve the problem. And that every experience you have, success or failure, is learning to solve problems. The 10 ways you failed to solve this problem all are solutions to other problems that you now know.

    “The expert has failed more times than the beginner has even tried.”

    I fear, however, the pervasive Pride in the Craft that existed 30 years ago is now something observed only by a minority.


  • Programming pays well because it’s hard. Just keep in mind that if AI is making it easy for you, it’s making it easy for a lot of people who could easily replace you.

    Use it as a tool, but know what it’s doing, and be able to do it yourself after you learn from it.

    Personally, I generally struggle through on my own first and then ask it to critique. Great teachers don’t just give you the code to copy.

    By analogy, you need to be able to hand fly this plane when the autopilot dies; those are the pilots who get the jobs.