But of course our company has a coding standard:

• Write it any old how.
• Keep the warnings off.
• Don't ever touch old code!
• Tests? Forget them!
• Documentation? Why?
• Shared code? Nonsense! We've got copy&paste.
• Efficiency? Why bother? Memory footprint? Who cares? Safety? Never mind!
• Ad-hoc SQL with variables interpolated into the queries all over the place.

I'm leaving by the end of this month.

Update: And I'm looking forward to it!
Yeah the salary's quite OK, I would not have to work too hard, but OH MY GOD THIS IS DRIVING ME CRAZY!!!

Adding an overcomplicated formal process on top of a years old "slap it all together" project is ... a sure way to petrify the spaghetti bowl. It's just as messy, but much harder to maintain and much more fragile. I feel like Adrian Monk tied down in a messy room. With an old, noisy, smelly, friendly dog loosing fur.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.