Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #14792
| From | Arved Sandstrom <asandstrom3minus1@eastlink.ca> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: multithreaded cache? |
| References | (3 earlier) <a1nu7sFnnpU1@mid.individual.net> <jp6iji$n6m$1@dont-email.me> <a1pb7oFpc0U1@mid.individual.net> <jp932s$r59$1@news.albasani.net> <a1vijnFv1jU1@mid.individual.net> |
| Message-ID | <fTIvr.34159$_l.17077@newsfe15.iad> (permalink) |
| Organization | Public Usenet Newsgroup Access |
| Date | 2012-05-25 07:09 -0300 |
On 12-05-21 04:15 PM, Robert Klemme wrote: > [ SNIP ]> > And it is true for a number of other techniques I would consider bread > and butter tools: > > - Ensuring requirements are gathered properly and understood before > starting to code (and design of course). I want to blame an improper understanding of agile and lean and iterative here, but I won't. On the other hand, I do think that a widespread kneejerk rejection of waterfall has also led, in many cases, to people rejecting formal requirements analysis and intensive BA work. Maybe they've read enough about agile to think that they'll find out everything they need to find out when it's time to build Slice 3, and it's OK to find out about Slice 3 requirements then, not upfront. My philosophy - perhaps old-school - is based on these observations over the years: 1) In the vast majority of projects of all sizes, the large majority of requirements were known and identifiable at the beginning; 2) Corollary to #1: the large majority of requirements do not change over the lifetime of a project, of any size. They may be identified late, or not at all (before release), but they were always knowable; 3) An impression of changing requirements is almost always due to imprecise stakeholder/BA/architect/designer interactions and conversations. If you get one answer in April and a different one in October, it's either down to who you are asking or what your questions are, or both. The actual final "real" requirement probably never changed. As I say, these are my observations. YMMV. In my case I do substantially more requirements analysis up front than maybe other folks do. It has served me well. I also do a lot of prototyping and wire-framing and proofs-of-concept/technology, all of which in some developer camps seem to have been relegated. > - Testing code _before_ shipping. > > - When writing unit tests, making sure to also include tests for > critical values (usually corner cases such as -1, 0, 1, limit, limit - > 1, limit + 1, null, "", etc.). Testing is a different art. There is a lot of truth to the saying that a good tester is a mediocre coder, and vice versa. At a minimum, if a single person does have the expertise to do both, they need to be schizophrenic. Although I've not read anything about it, I've occasionally thought that by generally accepted testing principles, that a person who writes unit tests (just like any other tests) cannot, and should not, be the developer. And yet it's the developer who invariably writes unit tests for his own code. Food for thought. > - Thinking about the person who must use what you produce, regardless > whether it's a document, a configuration file layout, a DSL, a class, a > library. It seems many people in software development are far more > concerned with the inner workings of what they create instead of > considering how it will be used. Maybe it's easier or it is because > making it work takes the largest part of coding - still the outcome > often is dissatisfying and a little more thought upfront goes a long way > at avoiding maintenance headaches and worse things. > > ... See my thoughts about prototypes, wireframes, Pocs/PoTs above. Using those methods I've saved a lot of time over the years. All of them show the end-user a good impression of *their* final interface. Which is what matters. > > This can't be so difficult, can it? > > Kind regards > > robert > > AHS -- Never interrupt your enemy when he is making a mistake. --Napoleon
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
multithreaded cache? bugbear <bugbear@trim_papermule.co.uk_trim> - 2012-05-15 10:14 +0100
Re: multithreaded cache? Silvio Bierman <silvio@moc.com> - 2012-05-15 11:41 +0200
Re: multithreaded cache? Roedy Green <see_website@mindprod.com.invalid> - 2012-05-15 15:57 -0700
Re: multithreaded cache? Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-05-15 16:13 -0700
Re: multithreaded cache? Silvio Bierman <silvio@moc.com> - 2012-05-16 01:22 +0200
Re: multithreaded cache? Silvio Bierman <silvio@moc.com> - 2012-05-16 01:19 +0200
Re: multithreaded cache? Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-05-15 20:26 -0400
Re: multithreaded cache? Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2012-05-15 21:41 -0300
Re: multithreaded cache? Silvio Bierman <silvio@moc.com> - 2012-05-16 09:26 +0200
Re: multithreaded cache? "Mike Schilling" <mscottschilling@hotmail.com> - 2012-05-26 14:54 -0700
Re: multithreaded cache? Roedy Green <see_website@mindprod.com.invalid> - 2012-05-16 22:03 -0700
Re: multithreaded cache? Silvio Bierman <silvio@moc.com> - 2012-05-21 15:25 +0200
Re: multithreaded cache? Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-05-15 08:22 -0400
Re: multithreaded cache? Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-05-15 09:56 -0700
Re: multithreaded cache? bugbear <bugbear@trim_papermule.co.uk_trim> - 2012-05-16 14:33 +0100
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-05-17 11:54 +0200
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-05-17 12:06 +0200
Re: multithreaded cache? Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-05-17 09:51 -0700
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-05-17 20:48 +0200
Re: multithreaded cache? Sebastian <sebastian@undisclosed.invalid> - 2012-05-20 01:35 +0200
Re: multithreaded cache? Sebastian <sebastian@undisclosed.invalid> - 2012-05-20 01:48 +0200
Re: multithreaded cache? Lew <noone@lewscanon.com> - 2012-05-19 18:11 -0700
Re: multithreaded cache? Silvio Bierman <silvio@moc.com> - 2012-05-18 20:42 +0200
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-05-18 23:45 +0200
Re: multithreaded cache? Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-05-18 18:31 -0400
Re: multithreaded cache? Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-05-18 22:15 -0700
Re: multithreaded cache? Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-05-19 07:09 -0400
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-05-19 12:33 +0200
Re: multithreaded cache? Lew <noone@lewscanon.com> - 2012-05-19 14:24 -0700
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-05-21 21:15 +0200
Re: multithreaded cache? Lew <noone@lewscanon.com> - 2012-05-23 23:11 -0700
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-05-24 23:05 +0200
Re: multithreaded cache? Gene Wirchenko <genew@ocis.net> - 2012-05-24 20:11 -0700
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-05-25 17:42 +0200
Re: multithreaded cache? Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2012-05-25 07:09 -0300
Re: multithreaded cache? Silvio Bierman <silvio@moc.com> - 2012-05-21 15:21 +0200
Re: multithreaded cache? Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2012-05-24 23:22 -0700
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-05-25 17:36 +0200
Re: multithreaded cache? Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2012-06-02 12:27 -0700
Re: multithreaded cache? Robert Klemme <shortcutter@googlemail.com> - 2012-06-02 21:54 +0200
csiph-web