Discussion Locked

Are techs lazy?

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

All too often I see postings here that are replete with 'txt' style spelling. Is this an example of techs being lazy or is it simply a fad?

Do the techs that use 'txt' speak write documentation that way or have their CV's written in such a style? If not, why is it OK to write that way in forums like these?

8 replies

by jaqui

we are lazy, our job goal is to have everything running so smoothly that we can get payed to play games all day. :)

as far as the spelling and grammar, or lack thereof in posts, lots of threads on it.
the general consensus is this seems to be more conversation than technical writing, and we all use slang, contractions and techspeek in conversations, so why not here?

I often toss grammar rules out the window, but I do try to use correct spelling. ( proper english, not that bastardized version taught in us schools ;) )

by jdmercha

Most techs are spoiled be auto-spell-checkers. They are not used to taking the time to have to spell correctly.

by noyoki

For me, I don't have the bloody time to read over my posts atm. Soooo much to do, I'm trying to say want I wanna say (and I generally aim to have it readable too), and get stuff done. If that includes a typo or 5 (and an abbreviation or 3), so be it. :P

Oh, and I fell in love with parentheticals.... parenthesii... parenthisises... hmm...

by garydw

Time.

Everything is done in a rush and therefore things get missed out, left out, tripped over or hacked into place normally with the intention of fixing it later but that later fix never appears because people are too busy fire-fighting.

by noyoki

It's also job security! Lol. If you had the time to fix everything perfect and pristine, they'd just fire you for lack of things to do.

by tony hopkinson

It's a conversational forum. Not even ms's vb compiler could gloss over the number of typos I make on this site.
In my experience in IT things go wrong not because we are making silly mistakes and having to rework, but because we are running around like mad bastuds trying to do the work we said would take six months in the six weeks allowed by the budget.
Hence bodged insecure undocumented cheap ass unrefactored unreadable garbage, that costs more and more to maintain and simply exacerbates the problem.

If I make a spelling mistake in the GUI, QA spot it. If I make a spelling mistake in the code, the compiler/interpreter spots it. If I do an unholy bodge (bodge on top of a bodge on top of a flaw) to make an impractical deadline the next developer to work on the code will curse my name for eternity.

If I make a spelling miskate in my post, anal retentives spot it.
LOL

This discussion is closed to new replies.