"It is better to have a permanent income than to be fascinating."
- Oscar Wilde
More pages: 1 ... 11 ... 21 ... 31 ... 41 ... 51 ... 61 ... 71 ... 81 ... 91 ... 94 95 96 97 98 99 100 101 102 103 104 ... 111 ... 121 ... 131 ... 141 ... 151 ... 161 ... 171 ... 181 ... 191 ... 201 ... 211 ... 221 ... 231 ... 241 ... 251 ... 261 ... 271 ... 281 ... 291 ... 301 ... 311 ... 321 ... 331 ... 341 ... 351 ... 361 ... 371 ... 381 ... 391 ... 401 ... 411 ... 421 ... 431 ... 438
Query FailedLeSnip3R
Monday, February 13, 2012

I feel your pain; I have been through that same process myself.

However every time I re-write my framework I port part of the old oneS to the new one.
So essentially large parts of the new frmework comes from the previous ones; a bit like a genetic algorithm applied to coding

If something was working and well tested before, there's no point tossing it away; instead I import it and modify it to fit the new coding style/trend I'm going for.

What's important is that new framework shows an improvement over the old one.
Sparc
Tuesday, January 31, 2012

Very true!
I have experienced this enough very early in my career that my Engine still continues to evolve supporting Dx 8, 9 and 11 and GL 2, 3 Code-paths but I never reinvented the wheel, I just kept updating.
The secret is never version your Code-base. Versioning is only for external users and fixed stable builds
Tremor
Tuesday, January 17, 2012

Your child is beautiful, the best to you and yours.
Jerry
Saturday, January 14, 2012

Wait 10 years.

Overlord nailed it:
"In my experience rewriting parts of the code on a continuing basis and having a plan for doing so is the key to having all your stuff up to date"
default_ex
Tuesday, December 13, 2011

Why not just adopt a better cleanup regime. I've been using procrastitracker for awhile now, and at the end of every month I scrape it for any entries for the project's I've worked on. Then it's just going through the files one-by-one to clean up the ugly. Has turned out to be a worthwhile exercise, some of the best optimizations I've done so far have come from the clean up period when I came in with the mindset of just making it consistent with the rest of the codebase.
Vilem Otte
Tuesday, December 13, 2011

Rewriting whole code is definitely evil. The best way is - copy old project, change messy stuff to clean stuff, remove deprecated stuff and add new features.

Of course don't forget commenting a lot, as fixing some 8 year old bug when you've no comments in the code can stop your work for days, not even weeks.
Groovounet
Friday, December 9, 2011

I came across this reflection and thought that I am a stubborn programmer, well just a programmer, and I will also have the idea that I need to rewrite everything because it will be eventually better.

That is to say that I am programmer and hence stupid. So, I trick myself and decide that I should always work with small module (in a namespace) so that when a component is "ugly" I can freak out and just rewrite this component our maybe actually provide some useful feature.

Another advantage is the reduce the feeling of "giant mess" because it "contains" better the code.
David McKay
Friday, December 9, 2011

Truthfully, some of the most amazing technique demo's I have ever seen were those you put together in Framework 3.

To paraphrase some of the other refactoring advocates:

Framework 4 is dead.
Long live Framework 4.5!


You can do it Emil!
More pages: 1 ... 11 ... 21 ... 31 ... 41 ... 51 ... 61 ... 71 ... 81 ... 91 ... 94 95 96 97 98 99 100 101 102 103 104 ... 111 ... 121 ... 131 ... 141 ... 151 ... 161 ... 171 ... 181 ... 191 ... 201 ... 211 ... 221 ... 231 ... 241 ... 251 ... 261 ... 271 ... 281 ... 291 ... 301 ... 311 ... 321 ... 331 ... 341 ... 351 ... 361 ... 371 ... 381 ... 391 ... 401 ... 411 ... 421 ... 431 ... 438