Most embarrassing and lucky moment on the first week of job.

Me and my best friend were selected in the same company as developers. I was having some trouble with my system. So I mailed the description to our support department. Pop up was displayed from our chat client and person on the other end happened to be a lady. She wanted me to share a team viewer link with click access. So I did it and within 2 minutes of efforts she solved it. I thanked her, closed the chat conversation and started installing few packages. Meanwhile, I was curious to see her as she was really nice throughout the conversation. So I opened LinkedIn, searched for her name and found her profile. I zoomed in her photo and she was a pretty chick. I didn't stop and found her on FB too, and quickly saw all her DPs. I just copied her profile URL and sent it to my friend ( the one that got selected with me ) and told him about my conversation with her. Then I asked my friend
"She's hot. Should I send her a friend request or have to find some more troubles in my pc and talk to her few more times ? :P "
He replied "Dude what are you wanting for ? "
Out of no where, a pop up showed up. It was the girl we were talking about. The exact message was

"You can now close your team viewer session, and we can talk over FB :)"

Embarrassing AF!

Trying to figure out why the damn error keeps appearing - then I realized I was refreshing the /Error page instead of going back to /Login for each of my tests.

Worst thing? Absuse LINQ and not in a fun sexy way.

Entity framework > check.
LINQ query > check.
Standard IEnunerable magic > check

The developer had decided that it would be a good idea to thread the enumerable all over the place and collapse it anytime they wanted access to the data.

I know it’s a rookie mistake a lot of people make, but it was some pretty core data that ended up being used all over the place, so it was a nightmare to correct and it really impacted performance.

Needless to say they felt very silly when we explained how LINQ was deferred.

As a rookie programming, I wrote really bad code and didn't understand why. Now, I've improved to where I know bad code, but I continue writing studios horrible solutions. And in the end up refactoring much until I don't have energy to look at my code anymore. This although knowing what I should/shouldn't do. Shame!

Spent 2 hours in frustration trying to fix a bug in my code. Then i found a > where a < should have been.

Always spend an hour debugging your container services before you think to clear the browser cache.

Testing is important. Like when you test your server program that forks another program in the privacy of your home, only to discover you put the child code where the parent code should have gone and vice-versa.
You and your wife can have a laugh about it, instead of getting reamed out by the client or your boss for fork-bombing the server.
Sucks because it's still a stupid mistake, but at least I managed to minimize the amount of shit that would have otherwise landed on me.