Conversation

Notices

1. Embed this notice
   alcinnz (alcinnz@floss.social)'s status on Monday, 09-Dec-2024 03:17:33 JST alcinnz

   Programming protip: We all make typos that causes our programs to fail, & which takes us forever to locate.

   You doing it doesn't mean you're a bad programmer. It means you're just like the rest of us!

   • Embed this notice
     (webdev Tory) :emacs: (worldsendless@qoto.org)'s status on Monday, 09-Dec-2024 12:01:41 JST (webdev Tory) :emacs:

     in reply to

     @alcinnz I had this happen last night, with latex and a mysterious "b"

   • Embed this notice
     alcinnz (alcinnz@floss.social)'s status on Monday, 09-Dec-2024 13:55:08 JST alcinnz

     in reply to

     • Olivier Forget

     @teleclimber I use a variety of languages, though Haskell tends to be my preference.

     But my point here: Yeah, sure. Use a compiler that points you directly to your mispelled variable names or missing semi-colons, that's useful! But what if, say, you get your logical conditions backwards & requires a "!" to be added or removed?

     Single-character typos don't just yield syntax errors, they can yield logic errors!

   • Embed this notice
     Olivier Forget (teleclimber@social.tchncs.de)'s status on Monday, 09-Dec-2024 13:55:09 JST Olivier Forget

     in reply to

     @alcinnz what are you programming in? I find that with strong types and good practices (like using enums instead of string values) and of course an ide hooked up to a good language model it's actually hard to make a typo.

     In fact it's hard to make a typo when you don't type! With auto complete based on symbols that fit the type, I rarely write more than the first few chars of a var or function name.

     (In my case Go + vscode achieve the above)