Read this blog post for a similar perspective on that problem:
Hardware is Cheap, Programmers are Expensive

BTW, please use English because we have International readers.

On the other hand, you are correct, the example is exaggerated. But you get the point.

Still, point still stands. You can’t EXPECT every programmer to understand your code on first look. IF efficiency is NOT NEEDED, why sacrifice readability?

naasar nga ako dun sa teacher ko ng subj na comsci d2 sa canada…… sabi nya ang haba ng daw ng code ko.. di daw efficient sa memory…. ang sabi ko naman sa sarili ko “sa bilis ng computer ngayon, halata pa ba yung difference? at bat pa kailangang mag tipid ng memory eh ilang kb lang naman yung program, at simple lang. imposibleng magjaroon ng memory leak.”

so yun, hahahaha, kasi mas madali para sa akin i-modify yung code dun sa way na ginagawa ko, at flexible sya in case I would want to use it for a future project…… so yun….. kapilitan, kailangan kong paiklian yung code to the point na, pag kailangang i-update or modify yung process, eh kailangang mag write ng new set of code for a new program…… haaaaaay……

so yeah, that’s my share……

Your sorting example is way exaggerated too. Even a hardcore programmer would not attempt to do multithreading stuffs just to sort 50 items.

For more info about bit patterns, see HRESULT.

This is the best blog post so far…