I am going to assume that most of your post is surplufious hypeboles of 
inqualifiable and unverifiable claims, and you assume anybody else does the 
same 
as yours.

Since mine are five as you say, you appear to assume that I do five of what you 
do.

As that is all I can figure out from this post--without you citing examples.

I know you will not however.
~Katrina

On Monday, July 26, 2010 06:28:16 pm Tony "omega" Sergi wrote:
> I try to avoid these types of things but- I just can't at the moment.
> 
> The whole thing can be summed up in three sentences:
> It takes you 5 paragraphs to get your points across.
> You go off-topic about a million different things while trying to make one
> point, and most of the time is irrelevant.
> This is the reason that those who have spoken are complaining, nothing more.
> 
> -Tony
> 
> 
> On Tue, Jul 27, 2010 at 8:53 AM, Katrina Payne <[email protected]
> > wrote:
> 
> > Well, this style that you do see, that I am working to adjust out of, was
> > mostly only created by these accusations of wall of text.
> >
> > I am now at the point that I do not even really type:
> > * Redundant remarks
> > * Irrelevant statements (in my mind at least)
> > * Keeping each "paragraph" along a single logical step in thought (if at
> > all
> > possible)
> >
> > The thing is, I have included a few other elements that cause issues.
> >
> > As I have found some people complaining about wall-of-texting tend to miss
> > sentences if they are not at the start of a paragraph. To point this out, 
I
> > tend to make these sentences their own paragraph.
> >
> > Personally, I blame that in the past, accusers have generally been fairly
> > terrible about qualifying what made my wall of text, a wall of text.
> > Forcing
> > me mostly to guess, and adjust.
> >
> > It is also these other previous issues with this, that have just generally
> > lead me to regard Wall-of-texts as not a real accusation.
> >
> > Generally I do read my stuff prior to posting it. I do miss a few things
> > due to
> > being in a rush, yes.
> >
> > Though--I just noticed that in your reply to shorten my response, I appear
> > to
> > have a few newlines in odd places. I am fairly certain my client forces a
> > newline on my messages at column 79... though it has just occurred to me 
it
> > might not--or that may somehow have an issue propagated elsewhere.
> >
> > I will note, that in threads about coding issues, I agree that text should
> > be
> > short. The code and comments in code should do most of the talking in
> > those.
> >
> > However, this, and other threads that I have gone over board with the
> > others
> > in, there has been very little code applied. So what would normally be
> > present
> > in code and comments in the code, appears to be done in a more verbose
> > manner.
> >
> > Thank you
> > ~Katrina
> >
> > On Monday, July 26, 2010 05:34:35 pm Jonathan Murphy wrote:
> > > Sorry, I typed it in a hurry and yes, you would probably write something
> > > completely different to what I did, it was only an example of the short
> > form
> > > communication that people prefer to read in a discussion list.
> > >
> > > I suppose it also isn't a blanket rule, sometimes (rarely) a wall of 
text
> > > may be required, particularly when someone is starting a new thread and
> > > trying to explain the problem they are dealing with and also when people
> > are
> > > posting pieces of code. Just try to be as short as possible while
> > > maintaining your point.
> > >
> > > I have the habit of reading everything I post and if I realise I'm not
> > > adding anything to the conversation, I cut chunks of my post out as a
> > > courtesy to the other members.
> > >
> >
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives, 
please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlcoders
> 
> 

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders

Reply via email to