CaleLettus wrote:
Hello,
I’ll try to keep this short BUT, I’ve got little/no experience with
programming. In fact, my only background is using Cold Fusion (since
1996 and VERY little of that for the past 5 years as I’ve been playing
as a Manager-type at my jobs so I haven’t had to do any hands-on stuff
for a while).
My question: Would Ruby on Rails be a good platform to get back into
the swing of things and is it something I can pick up on my own with a
book? Thanks so much!
ROR is awesome. So is easy to learn. It also eliminates a lot of the
hassle of crazy database designs some DBA’s make, that are hard as heck
to code to and impossible to maintain. I used Aptana (eclipse knock
off) but it corrupted my files on a java update. I got rid of it. I use
jEdit now for editing.
You will need CSS for web design, and there are many free template
sites.
You might want to learn database refactoring.
And then there is agile and extreme programming technigue’s.
In my opinion, stay away from the UML unless you are dying
to get into ton’s of time documenting things that will change.
You can just do a simple data flow diagram, in most cases,
or a class/attributes diagram. But in my world, the documents NEVER
get updated and you have to check the code, anyway.
I am not sure where this is from, but it is true: (it might be from the
envy guys)
Ruby Sucks Because
* Ruby does not any major corporate sponsorship or backing
* At RubyConf everybody wants to talk about Rails
* At RailsConf half the audience is writing books from lectures
given by the other half
* Ruby is a DSL for Rails
* Most people think that DHH wrote Ruby or never have heard of Matz
* There is no language specification for Ruby
* Ruby will fragment to different wannabe successors
* JRuby will ultimately go where Ruby can’t, the enterprise
* Closures are by no means unique to Ruby, get over it
* Ruby and Rubyist seem to have an inferiority complex when it comes
to Java, get counseling
* Rails is too tightly mind controlled, managed, copyrighted, owned
by DHH and 37signals
Java Sucks Because
* Java has way to many freaking frameworks
* There is sooo much to learn in developing an application
* Java has far too many APIs and libraries that are designed by
committee
* People still think Java is slow
* Java still suffers from the fiasco that was Applets
* Java still suffers from the fiasco that was EJB 2.x
* There too many flavors of the JRE (Java 5, Java 1.4, J2SE, JEE,
J2ME, JWTF)
* The JRE has a lot of junk in the trunk
* Methods gets deprecated, nothing gets removed, the API gets
bloated
* Java does not always run everywhere, sometimes you need to go
native
* Java is still primitive
* Java developers are a dime a dozen
* Java puts you in XML hell
Python Sucks Because
* Python cares about whitespace, I don’t care for that
* Python programmers are morons
* I like David Chappelle better than Monty Python
* Guido van Rossum doesn’t work at 37signals
* Python has no personality like JavaScript or personalities like
Dave T.
* Python will never go mainstream, not even with Google’s backing