More and more abstraction. This is not necessarily a bad thing, but it can be if done poorly

Me: intern in XYZ company
Boss: boss of XYZ

Boss: Why are you taking so much time in developing a simple webpage.
Me: *explains because you asked for so much bullshit to include**
Boss: I can develop it in half an hour.
Me: *-_-*
Boss: I developed a website in PowerPoint when I was intern.
Me: In PowerPoint? How?... Really..?
Boss: Ya, that's the type of skills I have. You're so lazy, you take so much time to make a simple webpage.
Me: -_-

My manager gave me a project about integration & deployment to another internal product which involves consuming oauth credentials which were already available in AmazonS3. The worst part of this is I wont have any access to any AWS resources and no sandbox environment.

And I'm like. How the fuck should I do this? Should I just conceptualize and pray to the machine spirits and hope that this wont have any fucking issues?

So true 😂

So many wifes out there are having this problem right now I guess.

Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. 😂😂

If Programming Languages Were Girls:

Java: Your current girlfriend, you've been going steady for a while now. Things are okay.

Kotlin: The girl Java finds you cheating on, she's just amazing, and you wish you'd met her sooner.

Visual Basic: The girl you accidentally started a relationship with because you didn't know how to say no. But quickly realised your mistake and regretted it.

JavaScript: A childhood friend you occasionally hook up with. But you could never settle for a relationship with them.

Python: A bossy, manipulative girl who quickly turned things sour. But everyone else loves her because of her huge libraries.
-----------------------------------------------------
My and a co worker were joking the other day about what programming languages would be like if they were girls. This is what we came up with (Original inspiration: the Distracted Boyfriend meme (Feel free to add your own!)).

There is no need to architect the system before hand. We'll just do it on the go.

An entirely typical exchange at work:

PM: How long would it take to build an application that collates Gubblefluffs and exports them as a PDF?

ME: Hard to say. What’s a Gubblefluff?

PM: Nothing complex. Its basically an object with some stuff in.

ME: Erm, okay. So I’ll define a Gubblefluff object plus methods to add edit and delete, then for each Gubblefluff have it write a line to a PDF.

PM: It will need to email that PDF to somebody.

ME: Okay, cool. “Gubblefluffs-by-email” should take about a day.

6 hours later…

ME: I’ve done Gubblefluffs-to-pdf, I’m not clear on what’s in a Gubblefluff but I’ve made it flexible so it can take almost anything.

PM: No, a Gubblefluff can ONLY be one of 4 Snigglefingers plus a timestamp and some JSON.

ME: What? Right. Okay. What’s a Snigglefinger?

PM: (sighs) A Snigglefinger is the collection of relevant Babelsets.

ME: Babelsets?

PM: Yeah, a user can have any number of Babelsets but they must correspond to one of the four types of Snigglefingers.

ME: There are users!?

PM: Of course!

ME: But I’ve not coded anything for users.

PM: Shit. I’ve told the client they can have it today. How long to add in users?

ME: And Babelsets, and Snigglefingers and the new Gubblefluff rules?

PM: Yeah.

6 days later…

ME: This is done now. It’s a beast but it works. Who should it email the PDFs to?

PM: Client X, plus cc to Y and bcc to Z.

ME: What? It doesn't support CC and BCC!

1 hour later…

ME: This is done. I’ve tested it and sent you a copy of the PDF it generates.

PM: Okay thanks. Is the cron running daily?

ME: What cron?

…

ME: Okay, so the cron’s running once a day at 8pm.

PM: Oh, it’ll need to be at 3:15pm. That’s when we’ve told the client they’ll get it.

ME: Right. I’ll change it...

PM: Also, the PDF you sent me looks nothing like the visual.

ME: What visual?
...

Lovely 😍

I love python, its the language I never really struggled a lot with yet also progressing so fast with it as a programmer!

When you're so into your project that you feel like peeing is a waste of time...

Manager: Hi, here is component X with 200k lines of code. Can you go through the code and see if you can implement component Y using component X?

Me: What does component X do?

Manager: I don't know.

Me: Is there a design docs for it?

Manager: I don't know. Can you check? Let me know when it is done.

*Wondering if I should joke and say "Oh management, hard job huh?"*

*Remembering how life is fucked up unfair and I need food to survive and house to live in and follow the society's rules and work hard to make the rich richer and shove money into their fat belly of greed...*

Me: OK.