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

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

Re: Calling deprecated methods

Show all headers | View raw

On Tuesday, December 12, 2017 at 4:04:55 PM UTC-5, Kiwi User wrote:
> >      Bear in mind that Java 9 was originally scheduled for 2016,
> > then postponed to 2017 Spring, then 2017 Summer, and finally to 2017
> > Autumn, more than a year later than planned.[*]
> >
> Then they had plenty of time to get it right, didn't they.
>
> > Resistance to the Project Jigsaw changes can be blamed for only part of
> > the delay;
> >
> Sure, but I wasn't really taking aim at Oracle: I have little doubt that
> they'll have reasonable regression test coverage and will maintain that
> regression test suite.
>
> In the past I've seen far too many sets of local library support
> functions that had no documentation, test harnesses or regression test
> data and was suggesting that devs in general should not go there.
>
> This was common in the past when we didn't know any better, but now we
> do. However, it wouldn't surprise me that many PHBs (who are probably
> MBAs) still consider test harnesses and regression testing to be a waste
> of time.
>
> > [*] A colleague once explained his method for making sense of
> > software project time estimates.  An estimate always consists of two
> > parts: A quantity and a time unit, like "two weeks" or "six months."  My
> > colleague would start by doubling the quantity, then continue by bumping
> > the time unit up by one step.  Thus, the examples above would be
> > understood as "four months" and "twelve years."  ;)
> >
> ... good to see there are no cynics round here.
>

Development time = number of developers * skill of developers * scope of
project?

How many bugs are there to be fixed?  How many enhancement requests?  How many
requests must be handled by a single developer or development team?

Is there a framework and standard for testing?  Is each developer or
development team responsible for their own testing?  Is anyone outside the
company using the API?  Does the company place importance on stability,
maintainability, versatility?

I suspect a lot of developers write code that is not well tested, not well
documented and/or hard to maintain if the company doesn't enforce standards for
 it.  Hard to maintain means job security.  Not well tested means showing
results faster, assuming it's not going to crash and hurt your career.  Not
well documented means getting results faster, assuming you're not worried about
 wasting your own time by having to modify what you've done previously after
you've forgotten how it works.

I suspect most businesses never look at their developers' code and give
performance reviews based on how much of their work has gone live, no pat on
the back for pretty and detailed comment blocks.  Sometimes that does require
peer review, as I'm not writing comment blocks for a section of code that seems
 obvious, though to another developer it may not be so obvious.

I currently work for a small business, so not a lot of time to waste writing
tests that can guarantee every enhancement won't break any existing code much
less comment blocks, when we have a dozen big enhancement requests and 2
developers.

Delays in the release schedule mean the code should be cleaner, only if the
initial release schedule wasn't overly ambitious to begin with, and if the
project wasn't inundated with change requests along the way.

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

Thread

Re: Calling deprecated methods Kiwi User <martin@mydomain.invalid> (Kiwi User) - 2017-12-12 16:31 +1200
  Re: Calling deprecated methods Eric Douglas <e.d.programmer@gmail.com> (Eric Douglas) - 2017-12-12 10:24 +1200
    Re: Calling deprecated methods Kiwi User <martin@mydomain.invalid> (Kiwi User) - 2017-12-12 20:05 +1200
      Re: Calling deprecated methods Eric Sosman <esosman@comcast-dot-net.invalid> (Eric Sosman) - 2017-12-12 15:41 +1200
        Re: Calling deprecated methods Kiwi User <martin@mydomain.invalid> (Kiwi User) - 2017-12-12 21:04 +1200
          Re: Calling deprecated methods Eric Douglas <e.d.programmer@gmail.com> (Eric Douglas) - 2017-12-12 13:33 +1200
            Re: Calling deprecated methods Kiwi User <martin@mydomain.invalid> (Kiwi User) - 2017-12-12 22:41 +1200
              Re: Calling deprecated methods Eric Sosman <esosman@comcast-dot-net.invalid> (Eric Sosman) - 2017-12-12 17:57 +1200
                Re: Calling deprecated methods Eric Douglas <e.d.programmer@gmail.com> (Eric Douglas) - 2017-12-13 04:51 +1200
                Re: Calling deprecated methods Eric Sosman <esosman@comcast-dot-net.invalid> (Eric Sosman) - 2017-12-13 08:21 +1200
                Re: Calling deprecated methods Eric Douglas <e.d.programmer@gmail.com> (Eric Douglas) - 2017-12-13 05:40 +1200
                Re: Calling deprecated methods Kiwi User <martin@mydomain.invalid> (Kiwi User) - 2017-12-13 15:19 +1200
                Re: Calling deprecated methods Eric Douglas <e.d.programmer@gmail.com> (Eric Douglas) - 2017-12-13 07:57 +1200
                Re: Calling deprecated methods Kiwi User <martin@mydomain.invalid> (Kiwi User) - 2017-12-13 17:30 +1200
                Re: Calling deprecated methods Richard Damon <Richard@Damon-Family.org> - 2017-12-15 22:31 -0500
                Re: Calling deprecated methods Kiwi User <martin@mydomain.invalid> - 2017-12-16 09:08 +0000

csiph-web