Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@steaksauce @Nawap Thank you for your respective views. Yes I know less lines != Efficient code. I was worried if my efforts in writing error handling didn't go wasted...
-
Real software is complex and involves dozens of components integrated with one another, passing data, and working in tandem.
Not handling errors properly in one place can set ogf a cascade of bugs that hides the actual problem and adds HOURS to debugging time.
~20 lines is nothing compared to the time proper error handling will save in the long run!
No questions asked
As a Python user and the fucking unicode mess, this is sooooo mean!
I just started working on a little project to browse devrant from terminal. It converts images to ascii art!
So our class had this assignment in python where we had to code up a simple web scraper that extracts data of the best seller books on Amazon. My code was ~100 lines long( for a complete newbie in python guess the amount of sweat it took) and was able to handle most error scenarios like random HTML 503 errors and different methods to extract the same piece of data from different id's of divs. The code was decently fast.
All wss fine until I came to know the average number of lines it took for the rest of the class was ~60 lines. None of the others have implemented things that I have implemented like error handling and extracting from different places in the DOM. Now I'm confused if I have complicated my code or have I made it kind of "fail proof".
Thoughts?
rant
python
web scraping
complicated code