So I can only skip the update with a pro account?! 😡

The Onedrive Experience

Men of culture

Outlook - providing useful reminders since forever

Yikes...

How developers deal with someone else's code!
Fixing bugs after bugs and it goes on.

It's true, that's the saddest bit.

.......

..........

Final build...

Wife clearly knows I’m a geek with this new mascot!

Legacy System Support

Interesting plug-in (Intellij)

I think we all know who the Atlas really is.

I've had this feeling ever since I've started my IT career.

This hurts 🥺

Found this...

........

Why windows ......

You have to assume mongodb didn't make it that far 😁

“Judge a man not by how he themes his editor, but by how he writes his commit messages.”

Lol lol

Remember that 😏

Good advice

programmer's situation

hex is sexy 💁

Meme is a meme!

Funniest O'Reilly meme so far :)

Cat.js meme

Juniors are a fun bunch to work with.
Over confident, hero complex of that fresh graduate high, and then thrown in to the real world! Where there hopes and dreams are crushed in minutes when they see what monolithic applications really look like!!

But don't let that overwhelm you, your not going to be changing all of it any time soon, hell some of this code hasn't been touched in 5+ years and still works without fail.

Don't stress about the work load, you can only write 1 line of code at a time anyway, and hell, even seniors make mistakes.

The key about being able to manage this beast is simple, break it! Because the more you break it, the more you'll understand how a project is put together, for better or worse. Learn from the examples in front of you, and learn what not to do in the future 😎

But more importantly, plan your changes, whiteboard the high level logic of what it is you want to add, then whiteboard in the current codebase and determine where to slice this bitch up, then when it all looks well and good, take out your scalpel and slice and dice time.
Don't worry, your changes aren't going to production anytime soon, hell, you'll be lucky to get past the first pull request with this working 100% the first time, and that's a good thing, learn from tour short comings and improve your own knowledge for the next time!

1. You don't code to add a feature or whatever. You do it to solve Users' problems. It's a User-centric system.
2. You read more code than you write. So help yourself and write code intended to be read.
3. If people don't know you did something, you did nothing!
4. Never answer a call at 3 am if you're not paid to be on night call-duty. You'll become the guy who answers at 3 am.
5. Remember the big difference between you and me is that I failed to do stuff more times than you have tried to do.
6. When you start shaving the yak, stop!