|
|
Darren New wrote:
>> It seems to be that, regardless of which programming language you use,
>> figuring out the best way to divide the problem into abstractions is
>> absolutely *critical* to writing clean, efficient, maintainable code.
>> And it's often not very obvious which way *is* the best until you try
>> to actually "do it".
>
> Yep. That's where the experience comes in. And the natural ability to
> recognise the abstractions in things.
Experience.
It's like Chess or Go - the rules is simple, but the tactics and
strategy to play well come only with practice and experience.
>> This seems like it's only common sense.
>
> You would be surprised. I've had people do things like pass the number
> of columns wide that the printer report should be in index zero of a
> floating point array indexed by customer age, just so they wouldn't have
> to spend 20 minutes to recompile other parts of the program when they
> changed what variables are shared between programs.
GAAAAAH! >_< IT BURNS! IT BURNS ME!! MAKE IT STOP!!!! GAH, I WANT TO
CLAW OUT MY OWN EYEBALLS!!1!!eleven
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|