Our new web dev at work showed me this:
http://theoatmeal.com/comics/design_hell
He had some pretty uncomplimentary things to say about his predecessors, too.
On the other hand, he has a job for life, sorting out their shit.
Our new web dev at work showed me this:
http://theoatmeal.com/comics/design_hell
He had some pretty uncomplimentary things to say about his predecessors, too.
On the other hand, he has a job for life, sorting out their shit.
it's not a bad thing till you throw a KLR into the mix.
those cheap ass bitches can do anything with ductape.
(PostalDave on ADVrider)
Break your code up in to small manageable chunks. Don't write a 350-line subroutine that basically does the same thing to 10 elements... normalise it, write a function to do the thing, call it 10 times. Much, much better. Whitespace does cost, in that instance, as it cannot be collapsed and must be scrolled through. Gets extremely tedious and time-consuming to work with.
Of course the smaller chunks can be tested, proven, library-ised and forgotten about.
Comments should describe what is being done (eg "add GST"), not how it's being done ("multiply by 1.15").
The most common style advice is to be consistent - and everyone sharing code on the project should use the same style. Conventions don't matter so much, as long as you follow whichever one you've chosen.
I _hate_ working with crappy, lazy, ignorant coders.
Cheers,
Colin
Originally Posted by Steve McQueen
All old and / or large systems eventually turn into a big ball of mud as described here:
http://www.laputan.org/mud/
Well worth a (geek) read.
Originally Posted by FlangMaster
The worst system I worked on was a life insurance capture application (client / server) that had 1,500 classes - each UI element was subclassed!
Do web developers these days use OO practices? I know various frameworks exist, but wonder whether OO theory is still widespread?
Originally Posted by FlangMaster
Crappy code = Code that does not deliver the solution to your customers expectations.
Good code = Any code that delivers the customers expected result.
How far into the future does that extend? Only to the moment they see it, or to the moment they discover Web Dev #2 is going to take 5 hours to do something that should have taken 1 because of Web Dev #1's practises?
Trying to decide whether you're the crappy coder we're talking about.
Yup, don't over engineer, there's no money in it.
No no no. There are plenty of point n click tools that will tell you exactly how a particular element got it's rules applied. Work smarter, not harder.
That's nothing. One guy I know looks after a webhosting companies technical odds and sodds... 8 servers, (2 Apache/MySQL, 5 IIS, 1 MSSQL), 8 different CMS systems (mixture of PHP/ASP/ASP.NET ones)... he looks after the servers, the code, the databases, everything... over 500 sites, and he's knows nothing about operational tasks, has never done a lot of PHP, or PASP, or other even weirder shit... and still gets $150 an hour for the privlege. Sickening ain't it![]()
Sure, but that still doesn't make the CSS any easier to edit (with whatever tool) or to add a new rule to or ...
Bad messy CSS is bad messy CSS, regardless of what tool you use to see what it's doing.
(Bad analogy time) It's like how a Doctor might have a new fangled high resolution MRI scan of your guts, to see what that bullet did, but it's still going to be hard for him or her to fix you up.
That reminds me of a large VB6.0 app I had to support, many many years ago. Absolutely full of stuff like (my memory-fu is weak):
sub EnableButton(Button theButton, Bool enabledOrNot)
theButton.Enabled = enabledOrNot
end sub
Tons and tons of absolutley normal stuff was farmed out into subs and funcs and stuff. Way pointless and meant you had to dig through twice as much code as you should, to trace through what was going on.
Measure once, cut twice. Practice makes perfect.
Meh - you guys complain to much.
Trust me it gets a hell of a lot more worse when you have to have code interface to stuff in the real world.
Embedded loops, broken cases or even a bad pointer means that someone (usually sitting in a comfy office somewhere) pushes a button on a web page and then a train on a site somewhere goes into "runaway" mode.
Consultants are the bane of my life, and could not design an exit out of a cardboard box.
Reactor Online. Sensors Online. Weapons Online. All Systems Nominal.
Crap code and system design is killing me right now. Supporting/maintaining multiple legacy apps and systems where 3rd party controlled PC-connected embedded cryptographic devices have to work across all manner of unreliable networks and that at least 20 previous "rockstar" programmers have all mangled horribly before landing in my lap is causing me to seriously rethink my vocation! I really enjoy programming, but other people's horrid code just serves to make me realise how good my own code is![]()
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks