I have absolutely no idea how this sort of opinion piece is supposed to be of value to another person on this planet.
Sure - everybody has to learn their own lessons and sometimes it can be helpful to read about another persons journey. In this case, however, the author is still too much in the middle of it and would do good giving it some more time, then digest it, then look back and reflect and maybe THEN write about it. Reports from halfway through an experiment do make for good blog fodder (and a post about going BACK to Coldfusion sure gets attention), but most of them, as this one, leave me very unsatisfied.
So sure - go write stuff like that into your blog, but I think only the blog post at the end of the series is what should be submitted here.
As someone else mentioned - learn more than one language. That's fine, and good. The main takeaway is often a broader understanding of how to solve problems from new perspectives, but at some point you need to implement things in a particular tool.
If investigating other platforms gives you a new appreciation for modern techniques which you can apply to your previous platform - that's great. If you decide to take the plunge and hone your skills on a new platform - that's great too. Seems like in either case, the net result should be getting better at development overall.
To the extent the OP didn't initially - found himself making the same mistakes in new platforms as he'd made in old platforms - it was great that he had the insight to realize the meta of the situation and reexamine what the real problem was. I (less often now) run in to people who jump to new platforms every few years, and never really get good at development, just good (enough) at shiny-new-tech-X.
I ditched ColdFusion for Ruby as my go to language years ago. Rather than reiterate the overwhelming negative aspects of ColdFusion, I suggest you spend a bit more time with Ruby, Python, and other languages; don't be constrained by one.
[+] [-] skore|14 years ago|reply
Sure - everybody has to learn their own lessons and sometimes it can be helpful to read about another persons journey. In this case, however, the author is still too much in the middle of it and would do good giving it some more time, then digest it, then look back and reflect and maybe THEN write about it. Reports from halfway through an experiment do make for good blog fodder (and a post about going BACK to Coldfusion sure gets attention), but most of them, as this one, leave me very unsatisfied.
So sure - go write stuff like that into your blog, but I think only the blog post at the end of the series is what should be submitted here.
[+] [-] j45|14 years ago|reply
[+] [-] zapman449|14 years ago|reply
http://webcache.googleusercontent.com/search?q=cache:UGF6HCq...
[+] [-] myliverhatesme|14 years ago|reply
[+] [-] Veejay|14 years ago|reply
[+] [-] mgkimsal|14 years ago|reply
If investigating other platforms gives you a new appreciation for modern techniques which you can apply to your previous platform - that's great. If you decide to take the plunge and hone your skills on a new platform - that's great too. Seems like in either case, the net result should be getting better at development overall.
To the extent the OP didn't initially - found himself making the same mistakes in new platforms as he'd made in old platforms - it was great that he had the insight to realize the meta of the situation and reexamine what the real problem was. I (less often now) run in to people who jump to new platforms every few years, and never really get good at development, just good (enough) at shiny-new-tech-X.
[+] [-] adacosta|14 years ago|reply
[+] [-] myliverhatesme|14 years ago|reply