At least refactoring the code can make the bug easier to find. What I hate is when I spend hours looking for a bug because I missed a single line in some documentation and misunderstood how something in the project worked, that always hurts.
Honestly, this is a good rule for programming in general. With user input, make sure it’s in its own area where it can’t interact with anything else and make sure to read and process in such a way that it can’t fuck with the operation of the program.
Javascript might be the most widely-used scripting language in use today, due to its browser dominance. Most popular would imply that it’s not completely despised by everyone that has to use it, which is misleading. Even TypeScript tutorials are about 50% ‘you have to understand what Javascript does wrong here’.
I did that many times with my game engine, and every time I have had to postpone a release by at least two weeks: one week of implementing the feature, one week of debugging it. (Where can I find people who want to work on an open source game engine?)
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.