This morning me and my colleague had huge debate about using GraphQL or REST. While I was in total favour of GraphQL, that guy was more on REST side because he read some random articles on dev.to and medium and was highly motivated to use REST instead of GraphQL.

The problem is, some people write anything on blogging websites without even doing a proper research.

Since, I have worked on GraphQL, I knew it's pros and cons very clearly and what are the things that can be done to solve them.

The guys said that we can't do native caching in GraphQL at which the lava from my head just got burst out.
I showed him the official GraphQL docs where it was clearly mentioned that we can do caching in GraphQL.
Poor guy couldn't say anything after that.

P.s: We are still going to use old school REST APIs but I am happy that I could prove my point. I'll use GraphQL in my side projects anyway, loss for him if he's not exploring something new.

Things gonna change pretty soon!

I got late at work today and top of that I really don't feel like working the rest of the day.

Is that normal?

One of my other dev colleagues believe that just because I don't want to work in a particular project and I don't like the decision of management, I'm being negative.
Where the fuck is Logic?

Just came across this wonderful video about Apache Kafka for building something real time and event based project.

https://youtube.com/watch/...

Earn heavy money. that's it.

What is horizontal and vertical scaling? Can somebody please explain in easy manner?

Although my profile is of full stack dev but at my company we barely do anything to scale anything.
Whenever I go for any interview, everyone asks me about scaling the application. What should I do?

I don't get it. Why do front end devs need to learn algorithms to get their interview done?

Manager: Unit testing is not our priority.
Me: What exactly is our priority?

My former manager thinks that 'React' is equivalent to HTML.