Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #6225

Re: I've been lazy

From Robert Klemme <shortcutter@googlemail.com>
Newsgroups comp.lang.java.programmer
Subject Re: I've been lazy
Date 2011-07-16 14:48 +0200
Message-ID <98dflsF4c6U1@mid.individual.net> (permalink)
References <c08ee4fe-df1e-4a2a-8c26-17137d64c60a@gc3g2000vbb.googlegroups.com> <32f10b50-2cae-4e57-8ee3-d7c54b827877@hd10g2000vbb.googlegroups.com> <88780480-0311-4b42-b33b-30249a3f8fb8@p14g2000yqj.googlegroups.com>

Show all headers | View raw


On 15.07.2011 18:38, Ross wrote:
> Fundamentally the program I'm writing is an experimental program,
> rather than a commercial product. Hence, my primary aim is to get a
> working version of it that I can release to people, and see if they
> like using it. If it's a hit, then it's reasonable to start rewriting
> bits of it to make them more elegant under the hood. Otherwise, if the
> end user can't see it, it's not a high priority. It took me part of a
> day to write the client/server code, so almost any amount of learning
> curve for things I haven't used in a while (e.g. RMI) would have meant
> that it took longer to get that functionality working.
>
> I'm reminded of the old programming maxim "Make it work first, then
> make it work fast". At the moment, I'll make it work at all, then make
> it more elegant under the hood. Fundamentally, I *need* people using
> it.

It is not too unlikely that the architecture of an experimental program 
does not fit real usage needs - especially if you provide it as a public 
service which can be hit by arbitrary many clients.  In those cases it's 
not enough to "start rewriting bits of it" but you need to rearchitect 
it which often means a major effort.

Experience shows that code that exists has a certain - err ductility? - 
which keeps it hanging around longer than you may want.

If you are afraid of the learning curve you could at least replace your 
custom format (which we do not know) with something like JSON which is 
pretty short yet allows for arbitrary structured data much like the 
verbose XML.  That will give you flexibility and avoid having to fiddle 
with the details of parsing.

Kind regards

	robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/

Back to comp.lang.java.programmer | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

I've been lazy Ross <rossclement@gmail.com> - 2011-07-15 00:59 -0700
  Re: I've been lazy lewbloch <lewbloch@gmail.com> - 2011-07-15 08:04 -0700
    Re: I've been lazy Robert Klemme <shortcutter@googlemail.com> - 2011-07-15 08:30 -0700
  Re: I've been lazy Paul Cager <paul.cager@googlemail.com> - 2011-07-15 08:35 -0700
    Re: I've been lazy Ross <rossclement@gmail.com> - 2011-07-15 09:38 -0700
      Re: I've been lazy Robert Klemme <shortcutter@googlemail.com> - 2011-07-16 14:48 +0200
        Re: I've been lazy Ross <rossclement@gmail.com> - 2011-07-16 08:48 -0700
          Re: I've been lazy lewbloch <lewbloch@gmail.com> - 2011-07-16 10:21 -0700
    Re: I've been lazy Ross <rossclement@gmail.com> - 2011-07-15 09:39 -0700

csiph-web