A Vengeful Ex

07 Feb 2024

JSFiddle (pictured left). The person she told you not to worry about (pictured right)

When I first took this class about a year ago, I remembered absolutely LOATHING JSFiddle. Unfortunately, those underlying feelings haven’t changed. To me, JSFiddle feels like reconnecting with an old ex-partner. You think “hey, a lot of time has passed since we last talked, people can change”. Then you spend a little more time with them and their old flaws seep through the cracks, just like old times. The sidebar in JSFiddle takes up practically half the page, its console implementation (still somehow in beta) made testing code a hassle, and UI elements were still as buggy as ever. For a free IDE to quickly test code, it’s servicable at best, at least when it’s not trying to get in your way. When we eventually made the switch to IntelliJ, it felt like a colossal weight off my shoulders. In comparison, the UI can be customized extensively and the application is nowhere near as buggy. It may not be the best IDE on the market, but it’s reliable and intuitive. It doesn’t feel like a liability.

Don’t forget to dot your i’s and insert your newLines!

I may be in the minority, but having ESLint supplement IntelliJ makes my coding experience significantly more valuable and maybe even satisfying. I enjoy knowing exactly where and what my mistakes are because of how errors are handled. Most errors have a label, which corresponds with a web page to teach you about a specific coding standard. It can also fix errors in many cases, but I usually choose to hand fix them. Some may be annoyed by having to pay attention to the minute details, like ensuring your program ends in a new line, but I feel it’s necessary when learning concepts where the minute details matter. After a few hours, I quickly got a good feel for abiding by the ESLint standards. It’s gotten to a point where I can recognize what error I have seconds after I see redlines underneath my lines of code. Coding standards generally speaking can improve overall readability and collaboration with other developers, and I’d imagine this also benefits the TA’s having to grade these assignments if they’re all abiding by the same coding standards. And you know what.. I do enjoy that green check. I’ll live and die by the green check. Maybe it’s psychosis.

Hopes for the future

Overall, I’m in a much better position compared to last year. I’ve talked before about the importance of retaining concepts vs retaining answers and so far it’s been paying off. And if I still have blindspots in my coding knowledge, ESLint and IntelliJ helps pick me back up. When writing out a underscore function, for instance, you’re greeted with the function syntax and parameter definitions, which were especially helpful to me. I’m far from the best programmer, but I’m confidant that my current tool set will aid greatly in raising my own personal standards.