3 ms·

(blog author) Well I thought refactoring went all the way back to Forth. I'm sure that with some language xyz it worked out very well for some project abc and

(blog author) Well I thought refactoring went all the way back to Forth. I'm sure that with some language xyz it worked out very well for some project abc and that obviously disproves my whole point and you can move on... I found writing large projects in Python - a language I was very familiar with, expert even - to become very difficult to extend aka maintain after a long time. My post should be seen in the bigger picture of the post I was following up about "Scaling My Server", and others I have written.

mhd 13y ago
Isn't "some language xyz worked out very well..." and "I found writing large projects in Python..." basically the same (anecdotal) argument?
- willvarfar 13y ago
  Yes, but its a subjective post. If someone wants to say or blog "I use xyz and I can successfully maintain and extend large projects and it hasn't collapsed under a cognitive burden and too-specific unit testing" that'd be a cool counter data point.
  - mhd 13y ago
    Advocacy is cool now? Statistically you could come up with almost any methodology, sane or not, and find one project using it, unless you're going for outright cruel jokes like Befunge, INTERCAL or ITIL...
protomyth 13y ago
> Well I thought refactoring went all the way back to Forth. The original refactoring browser was in Smalltalk. Forth programmers don't go about that type of thing the same way as other language since the goal is really to write good "words" that express your program. It is more building a better language than traditional refactoring.
PaulHoule 13y ago
I think you're thinking of the very good book "Thinking FORTH", which presented an incremental style of development coupled with a Lispy DSL architecture.