Contribution

@kwilliams I can't believe that was the fifth reply.

Copied the previous job in the CMS and forgot to update the meta information by the looks of things.

Users suck

Who the fuck are these people and why are they being paid?

Yes yes, a thousand times yes

Not yet

Do you have partial classes in your language?

That's my go to if in doubt (with a solid naming convention)

That is the very definition of micromanaging

I would cry if I had to reinstall my entire dev environment every month.

995 for the Pro edition, jeez.

I'd have to make do with Baby Semp1

100% record, well done

Good luck :)

Haha, actual lol.

Public override void DeductFromBalance(decimal amount){

// TODO:

}

????++

It's like 1.5%, I bet your percentage of mobile and tablet users is higher. I think tables is one thing we all broadly agree on.

A new definition for multicast.

That's just rearranging characters until something works.

If it makes you feel better there are many many YouTube vids of techies trolling these awful people

#iwanttoseeyourampage

I TOTALLY FUCKING AGREE!!!

except on tuna day.

Sounds exactly like the system we use.

Totally trying that.

God bless headphones

I think that warrants a resume entirely in caps

@KyleSoBold

That grates on me just reading it.

I would make him eat a turtle ass first.

That's what Google Tag Manager is for.

Spread the word.

Sounds like being a CEO

Thanks for your thoughts.

Following up your answer with more googling, it seems like helpers etc are an antipattern in general.

I'll file that away as something to keep in mind.

Just read up on this, top answer on SO is that they are bad because they:

Are concrete, violate single responsibility, cause tightly coupled code, carry around state for the duration of the application.

Umm... No, no, no (at least not in my applications), and best get rid of any kind of persistence / caching then.

Any other reasons? (genuinely interested)

Why are singletons bad?

I love the bastards.

@kapalaran sounds like a great teacher.