Jump to content
Ash

Fixing Bugs

Recommended Posts

So depending on what you are using to write your code, sometimes it may be a bit more difficult than usual to find the problem, figure out what's causing it and then fixing your code to ensure it doesn't happen again. Do you find the process of finding and fixing bugs easy? Does your code editor help identify what is causing the problem and give you easy to understand error messages & codes? Python is the programming language that I know quite well and luckily, the Python Editor is very user friendly and actually pinpoints exactly what is causing the error and what piece of code you have to change/edit. However, it's not always this straight forward. For example, when using Python & Flask to build a site, there are certain error messages that you will need to know what is causing it because they will not give any proper indication of what is wrong.

Link to post
Share on other sites

When i am coding, i usually have some idea on what could go wrong and usually have some preemptive measures behind my mind. This is usually very easy to contain using error handlers and going around with the codes. Although some statements are codes that comes from your thoughts and plans, there are some errors that are very hard to determined and solve. That's where the internet comes in... a quick research can solve the problem, with some backup books that are really handy in times of needs. Also a bottle of beer and a slice of pizza can make a difference:drool:.

Link to post
Share on other sites

Mastering the use of coding language is something that is not easy, it requires a lot of patience and dedication to study and do it effectively and efficiently. I have tried learning but it's not easy for but I'm trying my very best to get a hang of how to use it. I have had a little progress with the use of Python and I'm still making efforts to get more better at it. 

Link to post
Share on other sites

That hardest problem with fixing bugs is finding their source, which is quite difficult. Especially if you already created a big project and it has tons of bugs, then you'll end up spending double the initial time you consumed to write everything.

Link to post
Share on other sites

Most of the time when I do my coding, I already have specific scenarios that I am planning to test. Usually, it involved testing negative, positive, and exceptional scenarios to make sure that the code will not break once it is deployed into production. Keep in mind that the longer a bug is kept and not detected into the system, the higher the cost of fixing it once it's already in go-live.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...