If you define a pattern as recognizing a good solution to a problem. Then an anti pattern could be described as not recognizing you are applying a bad solution to a problem – that is until someone points it out to you.
Every project you go on it is important to share lessons learnt.
Coaster requirement – also known as development by Osmosis, this is when the requirement is given to a developer on a beer matt.
CnP Programming - this is the tendency to avoid writing a program from scratch and try to copy from a tech spec, online help or google. This is usually followed by a resource vacuum, asking everyone else around why it doesnt work, going with the easiest to implement answer.
404 Consultant - the phenomen of having to rely on resources which cannot be found when needed
Programmer by association – also known as FTS (frustrated techie syndrome), been told by a functional person that the solution is to change line XX, before the problem has been defined
Dynamic Resume Syndrome (DRS) – common practice on big projects where for example a bad programmer is let go only to return months later as a functional team lead.
Wearing a box - releasing as little knowledge or responsibility as possible in an attempt to keep your job. aka covering your assets
Sour Milk - how the milk tastes just before the cow goes offshore
Digging your own grave - also known as knowledge transfer sessions
Vapor Lock in – aka the CIO’s new clothes, falling for Vendor hype because you dont want to appear like an idiot
feel free to share and i’ll add to the list
