Seocheckout

What's the hardest part in programming?



Write the reason you're deleting this FAQ

What's the hardest part in programming?

Personally for me, the most difficult part in programming is finding bugs in your software, before publishing it in public. Even when software is running perfectly in your machine , debugging is an important process and quite inevitable sometimes.

If you have coding experience, what's the hardest part for you? Please share your thoughts!

Comments

Please login or sign up to leave a comment

Join
anwebservices
I guess for all programmers, hardest part is finding bugs and mistakes. Sometime i do PHP programming and by just swapping ; with : nothing works. Well easy to fix, but sometimes very hard to find where the mistake is. There was times when i had to look over and over again for few hours where the bug is. To be worst, there were many times that i looked and i was sure there is no bug, but at the end you have to find it, one way or other, or all your work is absolute zero What



Are you sure you want to delete this post?

robertman11
Bugs are definitely the worst part of coding. Especially those bugs that turn up months later caused by user input, user devices or otherwise that you didn't test for and couldn't anticipate.



Are you sure you want to delete this post?

EliteWriter
Being a programmer is certainly not easy. I agree that debugging is one of the most problematic tasks of all for a programmer. Sometimes it seems impossible to find what is wrong, and it takes ages to manage to find the bug and then realize how to fix it. However apart from debugging there are other challenges that a programmer needs to face.

For instance, managing to design a solution which will manage to meet a client's needs is not always straightforward. Another challenge is to write up unit tests, and see that each one functions properly. Although this is a good practice overall, it tends to be really tedious in my opinion.

One thing that is simply a nuisance is trying to work with a code that someone else has written. It is often difficult to realize what another programmer had in mind, especially if the code was poorly written and documented.

Another task that most programmers just cannot stand is that of trying to estimate how long it is going to take them to finalize a job, which is unfortunately something that many clients demand to know in advance. Often they fail to realize that a programming problem may take longer than expected. Predicting task length or duration is often a bit impossible.



Are you sure you want to delete this post?

overcast
I think hardest part is in finding regular projects and testing your skill. If that is not done properly things may not work out. I think some of the time lack of project makes you wander. And you lose the touch with the projects and language. That's how I lost touch with the language. I think lot of effort goes on while making the best use of the language in such case.



Are you sure you want to delete this post?

Corzhens
This reminds me of my first employment. Our section was situated beside the programming section that gave me the reason to know some of the programmers. There was one programmer that they always ask to debug the program. The other programmers admitted that it is easy to to the flowchart and coding but when something goes wrong that it the hardest part.



Are you sure you want to delete this post?