(no subject)

[hyuri]

the only way I can think of to fix LJ.NET is to switch to asynchronous server calls, which would require a fair overhaul of a lot of code. certain actions would have to be broken out into seperate functions which could then be run in a seperate thread. some functions would need to be merged, split, twisted...

it’s not really robust code. and I have to take a lot of blame for that, since I’ve been adding to the problem instead of doing it the Right Way.

and then, of course, I need to deal with the headache of thread‑safety. >_<

this is gonna huuuuurt... but at least the next person to maintain it should have better code to maintain. although I’m beginning to question why that’s so important to me.

Comments

[science-vixen.livejournal.com]

although I'm beginning to question why that's so important to me.

Two answers:
1) Because you might be the next person maintaining the code.
2) Because you are paying forward.

The second answer is important here.
I don't know whether you heard the story.
basically when you are in trouble someone lends you a hand, or gives you money. But instead of asking you to pay it back they ask you to pay it forward. Extend the same type of help to someone else who needs it, with the same clause attached to it.

As a result the world gets a little better for everyone.

The same works for code. When no-one documents or writes maintainable code, everybody else thinks they don't need to bother either.

I started with writing well spaced, documented code as a professional courtesy to my fellow programmers who are going to be stuck with maintaining my code long after someone else accidentally deleted the manual.