In addition to talking all about yourself and polishing your resume, take a bit of your time and learn something about the company that should hire you. Try to find out what they do, how they do it and what their success story is. And then put yourself in that picture.

When software matures and becomes bigger it feels like even a small change takes a day to implement. How do you remain innovative with a large code base?

To err is human;
To rant is developing

I have not used a lot of technology, but among the worst experiences was working with OR mapper. I don't think OR mappers are bad by themselves, but all the tutorials and entry level documentation drag the unknowing user slowly into a world of hurt. It looks super easy and super cool, but in fact if you don't know _exactly_ what's happening in the background you're about to deal with slow performance, terrible SQL statements, missing indices, etc. It makes shooting yourself in the foot a Starbucks-like experience, everywhere, all the time, and fast.

It's one of those promises that do not deliver the easy way despite most people advertising it like this. Except when you plan to write a book'n'author application with only 5 books and 3 authors. Yeah...

Why I hate internet media, because it's full of articles such as:
9 tips to make you lose weight faster
13 ideas on how to improve your sex life
8 ways to make you happy when you are sad
47 funny images that make you laugh
8482929 articles that use a pointless number as a headline starter

I admit that these articles are way more tempting to click than if they did not use that number. On the other hand, the number is just random, it only describes the extent of the article. I so hate it.

Becoming a High Reputation Stackoverflow Master

Can work like this:
1. Look for questions like "How do I add a value to a list"
2. Post "Use list.Add(x)" faster than any of the 20 expected answers that will be written for this question
3. Become accepted solution
4. Get 100 up votes as more people unaware of API documentation come across your answer

Sometimes answers and questions are so trivial you wonder how this would be upvoted by anyone ever.

Developers always know better what's best for others and when you do take their advice 2 weeks later and they're no longer using whatever they raved about 2 weeks earlier, because... something new and even better... and man you have to try this or otherwise you are a lame fool and that's definitely going to stay forever or maybe 3 weeks finally...

And if you ignore these fools because what works for them is not working for you, they in their ignorance keep pushing... at least until the 2 weeks are over...

The (in)significance(!) of a not:

if (!IamRunningParallel()) {...} else {...}