4 ms·
Is this strictly an issue with self-taught programmers? I mean, there has been a ton of articles on the front page here about why coding tests at interviews are
by dizzystar 13y ago
Is this strictly an issue with self-taught programmers? I mean, there has been a ton of articles on the front page here about why coding tests at interviews are a bad thing, and it seems that most of it revolves around not ever using it, and this attitude appears prevalent among web-coders.
As a self-taught programmer, I take speed and big-O considerations very seriously, but I've gotten the impression that my opinions on this topic are too extreme. I hate nothing more than a slow program and website, and I especially hate it when the site runs so slow it causes my fan to whir. It is nice to see that there is at least one other person that probably wouldn't think I am insane.
- rimantas 13y agoWell, I am not sure how often big-O applies to websites. Sure, you can tune your backend to handle processing in .1 s instead of .2, but then user can still wait 10-12 seconds till all the assets are downloaded and rendered.
- tommorris 13y agoThe key to web performance is finding JavaScript code and ruthlessly pressing delete.
- dizzystar 13y agoSpeed considerations, though not precisely big-O, certainly applies to the database design and how you call it. And it must apply in many other areas. How many sites have you visited that takes more than 10 seconds to load lately? How many "cloud-based" programs have you used that takes far longer than it should to do basic operations? I know I can name quite a few.