Professional Web Applications Themes

Learning Curve Development Time Question - Ruby

I am curious what others have found with a learning and development curve with areas of code that are quite similar. In the design of a small scale project there will be 2 main systems. Inside of these systems will be a few more smaller subsystems. The systems will communicate to eachother via network socket interfaces. This is so we can have the systems to different machines. I was thinking for expandability purposes that perhaps we made the subsystems work the same way. So that if for any reason we found one area getting used a ton that we could ...

  1. #1

    Default Learning Curve Development Time Question

    I am curious what others have found with a learning and development curve
    with areas of code that are quite similar.

    In the design of a small scale project there will be 2 main systems. Inside
    of these systems will be a few more smaller subsystems. The systems will
    communicate to eachother via network socket interfaces. This is so we can
    have the systems to different machines. I was thinking for expandability
    purposes that perhaps we made the subsystems work the same way. So that if
    for any reason we found one area getting used a ton that we could move it to
    it's own machine with little effort. Since the 2 main systems would need
    socket interfaces to communicate with eachother I am curious if coding the
    subsystems would provide unneccessary development time. Or if since the same
    logic could be applied that was already coded and tested in the 2 main
    systems that the development time may not be unneccessary.

    In any of your experiences is this the case? Would the development time for
    the subsystems go way down since the main 2 systems have been tested and is
    good to go? Or since they are different "systems" would the
    learning/development curve still be just as steep?

    Thanks for any replies!

    Zach



    Zach Guest

  2. #2

    Default Re: Learning Curve Development Time Question

    Not sure if its inside the topic at all, nor if it will help, posting
    the testimony anyway.

    All of our internal software, most automation tasks, content management,
    in others, used to be coded in Java, few (very few) on Perl.

    Platform used to be Win32 and solaris on x86, more recently we have
    moved 90% of it to OpenBSD on x86.

    Id honestly say, the first reason to move away from Java was the lack of
    support on OpenBSD. Then came the Perl phase.

    Honestly saying, we are programming in 1/2 days with Ruby, what we used
    to take 1/2 weeks in Java.

    Specially the simplicity, and the builtin methods for web, ftp, email
    and regexp are the obvious reasons for that.

    Not sepcialist in Ruby yet, altho the learning curve for doing the same
    software has been considerably low, as we did java and perl before.

    One thing we notice is slightly harder to track programming errors, it
    took a while to get used to it. But overally, its been well worth it, if
    we were able to deploy the same code to the Java VM, that would seal it.

    Still portable tho, and runs pretty much in everything.

    Again not sure if any usefull on the case, but there it is.

    Good luck !

    Rove Monteux

    Zach Dennis wrote:
     

    --
    Rove Monteux
    Systems Administrator

    com




    Rove Guest

  3. #3

    Default Re: Learning Curve Development Time Question

    Zach Dennis wrote:
     
    Having two systems talk across a network is not to big a deal but at
    what level do they need to communicate. Could the whole socket thing be
    replaced by http requests? This would allow you to step back from socket
    programming and use things like Webrick.

    Just a thought.



    Peter Guest

  4. #4

    Default Re: Learning Curve Development Time Question


    Peter Hickman said: 

    Or even something like DRuby!

    --
    -- Jim Weirich org http://onestepback.org
    -----------------------------------------------------------------
    "Beware of bugs in the above code; I have only proved it correct,
    not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)



    Jim Guest

Similar Threads

  1. MS Vista learning curve
    By Carlos in forum Windows Vista
    Replies: 2
    Last Post: April 21st, 09:31 AM
  2. Learning Curve??? Urgent Question
    By grettamitch in forum Macromedia Director Basics
    Replies: 4
    Last Post: June 7th, 08:17 PM
  3. Flash to Director Learning Curve
    By CJV in forum Macromedia Director Basics
    Replies: 2
    Last Post: May 30th, 01:51 AM
  4. Flash MX learning curve
    By Robert Le Feve in forum Macromedia Flash
    Replies: 1
    Last Post: October 1st, 11:05 PM
  5. The Learning curve of taking great pictures.
    By J. A. Mc. in forum Photography
    Replies: 6
    Last Post: July 27th, 02:44 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139