Replies

Boy, if you and Miss Spelling Bee would consult the posting rules for this forum, you would find that criticism for spelling in not considered good manners. It is not prudent to be overzealous in proofing these posts.

You haven't seen my work, nor worked with me. You are simply in no position to judge my work. I keep good records related to software changes, even when management doesn't require this. I also keep time records on each task, and feed that back to my own original estimates. Management has never required that. That feedback loop allows me to estimate my work to within 5% unless the requirements are a moving target. I do write excellent software and documentation. Don't jump to conclusions related to postings.

BTW, you match my stereotype for QA personnel. If you could code, you would be employed writing software. I'm still employed. Our entire QA department is out looking for work. Your job is very useful in ensuring delivery of a quality product, but it does not produce the product.

BWAHAHAHA. Still dodging. Can't take even the slightest criticism.

I'm in an excellent position to judge your work. I've seen that you can't spell and any criticism gets your back up and puts you in a defensive mode where you immediately try to blame everyone but yourself. Those are the personality traits of a bad engineer. You could have walked away from all of this yesterday by simply aknowledging the mistake and moving on, but you're incapable of doing that you must FIGHT FIGHT FIGHT. Blaming the people who noticed you can't spell instead of simply taking the hit. I'm not jumping to any conclussions, I've had similar conversations with many developers in my career, and in each case that developer was a drag on the company and his work blew chunks.

I can code, I just never liked it. Your work might produce a product but given how poor you are at self checking the product would get somebody killed out in the field if nobody was there to make you do it right. the fact that you think it's a good thing that your company got rid of QA shows what a stereotypical bad developer you are, employing engineers with your attitude and getting rid of the safety net that keeps you from releasing garbage in the field proves your company is run by idiots and doomed to failure. Better spellcheck your resume because you're destined to be on the street soon.

Walk away from it. Every time you comeback to whine about being mistreated and boost your own ego with pointless red herrings I'm not dumb enough to believe you simply prove me right. You're a bad speller, a bad engineer, and not a very impressive person. That's the badge you more firmly affix to yourself with every reply in this thread.