• 0 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: May 1st, 2024

help-circle




  • Seems like it’s mostly error handling, which makes total sense to me. In a function with a lot of error conditions, where it also takes more than return <nonzero value> to report that error, the code would get very cluttered if you handle the errors inline. Using goto in that case makes the normal case shorter and more readable, and if proper labels are used, it also becomes clear what happens in each error case.

    Sure, you can do that with functions too, but it’s much nicer staying in the same scope where the error occurred when reporting on it. Putting things in a function means thinking about what to pass, and presents extra resistance when you want to report extra info, because you have to change the function signature, etc.










  • If I’d Only Known I Wouldn’t Have Wasted So Much Of My Potential Club.

    I’m in this club but very much trying to leave, because I’m starting to realize “wasted potential” in itself is a toxic idea that’s been ingrained by years of teachers telling me this (with my parents doing their best to counter). That’s not to say I’m not still trying to do my best, I am, but only because I want to and because it makes me happy.



  • I agree with the overall sentiment, but I’d like to add two points:

    1. Everyone starts off as a code editor, and through a combination of (self-)education and experience can become a software engineer.

    2. To the point of code editors having to worry about LLM’s taking their job, I agree, but I don’t think it will be as over the top as people literally being replaced by “AI agents”. Rather I think it will be a combination of code editors becoming more productive through use of LLMs, decreasing the demand for code editors, and lay people (i.e. almost no code skills) being able to do more through LLMs applied in the right places, like some website builders are doing now.