Search for a command to run...
Every competition deserves a dramatic submission just before the deadline 😉
Few interesting things about me:
If you’re new to machine learning, reinforcement learning, especially, then it’s completely okay to have a hard time understanding these fancy jargons in front of you. Here’s my attempt to simplify these while we work on a little robo-car :) About AW...
Dynamo DB is AWS's NoSQL offering in the vast set of managed databases as a service that they provide. Like most other services, it's fully serverless, flexible and easy to scale. The Data Model As we're working on NoSQL here, there's no real restric...
I was recently a part of a hackathon and was found searching for good Jupyter environments on the cloud to be able to work on my ML Project. Soon enough, I found myself here. However, it took me a while to figure out how powerful it truly can be. F...
I spend 5 days out of a week coding for work, so I'm definitely not motivated to code a lot on weekends. This means that I do not have any software development tools installed on my personal machine. Not even IDEs. However, being the curious little g...
Almost a week to this and not a lot of drama on Indian Twitter, so I thought I could write about it. TLDR: Malicious code with a backdoor was added to one of the core packages of Linux affecting almost all Debian and Redhat distros; was later discove...
Software development is inevitably accompanied by errors. Perfection is unattainable in coding. However, the way we handle errors is crucial to our growth as developers. This article presents a concise guide with practical steps for debugging errors in various programming languages and frameworks. Join me as we explore!
Hi, my name is Sreekesh and I'm a Software Developer and a Content Writer. I've been learning and working with full-stack web development for almost 3 years. I'm a final year undergrad student from the University of Mumbai, India.
In this article, I'll try to change your mindset of approaching errors and problems in your code and working your way towards solutions in a hassle-free manner. I've participated in numerous hackathons and I've explored different ways to debug errors especially when it's a race against time.
We're gonna follow a series of simple steps to find a solution to the error we're facing.
One of the silliest mistakes people make is blindly copying the error and putting it on the browser or ChatGPT. The key here is to first understand which part of your code is producing the error, what your code was intended to do and which end of the workflow is causing the issue.
When it isn't clear which part of the workflow is causing the issue, you can walk through the code in reverse, i.e. from the final line all the way through to the start. Feel free to make use of console.log or other print statements in your language to log outputs at different stages of your program. This will provide you clarity about the exact lines that are giving you trouble.
Utilize try-catch statements to gain a comprehensive grasp of your program's workflow and guarantee a crystal-clear understanding of potential code-breaking points. By implementing this strategy, you increase code readability and facilitate comprehension for others.
Famously known as Google-ing, the idea is to be efficient at finding things out of Google Search. All you have to do is put your error out on google search and take a look at the results. The chances are, you'll find yourself in a StackOverflow thread, an old GitHub Repository Issue Discussion or literally on the documentation website.
Google-ing doesn't make you any less of a developer. The best developers I know are the ones that use Google the most. Much like any other tools like StackOverflow or ChatGPT, which is where we are heading.
You'll find most solutions related to syntax errors, typos in function names, etc. in the documentation. Sometimes, you miss out on an argument, or there's a typo in the function name and sometimes functions and objects are deprecated by libraries and replaced by other utilities. When you grow as a developer, you'll find yourself interacting more with the documentation and less hobbling around search results.
StackOverflow is still the holy place where most of your errors will be solved. The knowledge base of that website purely out of support from community members is insanely huge. However, we now have friends from OpenAI that make use of websites like StackOverflow and bring results to us even quicker.
Given how fast ChatGPT is in finding things out, it is a handy tool for debugging. In fact, in a lot of cases, ChatGPT alone could fix your problems. However, I wouldn't recommend this for now, because it doesn't seem to manage versions (it sometimes shares dated/deprecated code) as well as one would expect.
Discord has to be my favourite community platform. Most frameworks and tools that I use (like Next.js, Supabase, Flutter and more) have already set up their Discord servers where people talk about the software, and its issues, there are spaces where people can share their errors and more. This is why I feel that you should explore different communities on Discord because they can certainly help you in the debugging process.
Here's Supabase's Discord server for instance. There's a forum channel set up for doubts and issues. You'll have a similar experience with your frameworks as well, the open-source community is very friendly and amazing when it comes to supporting at this level.
Errors are, in a way, your friends. Because every new error teaches you something, even though you might find them annoying. While you are on the warpath to solve that annoying error, I want you to steer clear of these things that can potentially destroy your learning process.
The difference between a Junior and a Senior Developer is the number of errors they've come across.
Enjoy getting new errors. As I mentioned, they are a part of the process and inevitable. Going through this process of debugging is very rewarding and gives you a sense of achievement at the end of the day.
I hope I was able to provide practical and effective steps for debugging errors in various programming languages and frameworks. I hope that this guide will help developers approach errors with a positive outlook and that they will find the solutions they need to create effective and efficient code. Embrace the process, keep learning, and keep growing!
