Today I came to the conclusion that LLMs are mostly for smart people. They usually made me lose time try to solve the wrong problem and in the end I just debug by printing
=> More informations about this toot | More toots from RosaCtrl@mastodon.social
@RosaCtrl If you have access to an in-editor debugger (with breakpoints and value inspection and such), try getting used to that. It was the biggest productivity boost I’ve had since learning FP, alongside using LLMs.
=> More informations about this toot | More toots from Profpatsch@mastodon.xyz
@RosaCtrl Stuff like logpoints and attaching to running processes (at least for node) makes debuggers a strict superset of printf-debugging
=> More informations about this toot | More toots from Profpatsch@mastodon.xyz
@RosaCtrl Funnily enough, embracing classes/objects for local state (not inheritance!!) was the other big improvement to my code after unlearning it with FP.
=> More informations about this toot | More toots from Profpatsch@mastodon.xyz
@Profpatsch 💯 For the last two years I’ve been removing all the inheritance that “expert on iOS consultant” brought to the table 🙄
=> More informations about this toot | More toots from RosaCtrl@mastodon.social
@RosaCtrl this is the way
=> More informations about this toot | More toots from Profpatsch@mastodon.xyz
@Profpatsch I like the Xcode debugger a lot, the reason why I print stuff though is that sometimes it changes the order of execution. Most of my bugs are concurrency related now. Even if I only use the “when you hit this line print something and continue”.
This bug wasn’t concurrency related, but after wasting enough time with ChatGPT I preferred to be safe
=> More informations about this toot | More toots from RosaCtrl@mastodon.social
@RosaCtrl oh no concurrency evil
=> More informations about this toot | More toots from Profpatsch@mastodon.xyz This content has been proxied by September (ba2dc).Proxy Information
text/gemini