They:Why didn't you come up with this solution 2 years ago?

Me: The framework on which the new solution is proposed DID NOT exist 2 years ago.

This industry is fun!

* TALKS to someone from Portland about a potential Amtrak trip to Portland.
*opens youtube after an hour or so*
Top suggestion -> TOP 25 things to do in PORTLAND

Good old days where we use to laugh off such "coincidences" as Paranoia! Now this shit scares me for real

If you dish out the same shit you inherited from your senior colleagues onto your juniors, you have just successfully become the part of an ongoing shit show.

Be kind and supportive. Earn their trust, be approachable. Listen to them and help them learn to solve problems. Give constructive feedbacks, not harsh criticisms. Point out room for improvements, not belittle someone. Be that mentor/teacher you wish you had.

Learn. Build. Teach. Grow

Amazing how people misuse the term technical debt.

A bug is a flaw in your design/development.

Tech debt is a conscious decision/tradeoff, which is often tracked and removed as the product matures.

The difference is subtle. Avoid this mix up at least in written communication.

!rant

Breaking point in System Architecture. The point where you define it is ok for the system to break if you user doesn't meets the expected threshold of intellect.

In plain words, you say "F**K it, if someone is that stupid, let the system go down"

They don't teach this in college.

Three days after I purchased iPhone XS, I had to install a new modem at home. The phone wouldn’t connect to the wifi network in the higher frequency band. The guy who came to install the modem dished out the theory that the phone must be too damn old to support it. That burn!

PS: it connected almost a couple of seconds later that. As if it was some kind of extra layer of authentication. Well played Apple.

Nothing stops you from experimenting out like a highly stable system. Never let stability become a plateau.

LLD | CODE

I have NEVER had a trust issues with a hard-working developer. It is always good to have someone you know would move heaven and earth to solve a problem, if demanded. It was a privilege to have worked with a handful of them.

PS: If your team doesn't have one such, either be one or change the team/company!

DevOps is less of Dev and more of Ops. #FML

https://bit.ly/2yaWZFd

An interesting article on silent meeting. I think this is extremely efficient. Thoughts?

The error in database entry was negated by a bug in front-end code. Two mistakes cancelling out each other!

How is your day going ?

I want legit data on how many times your second build attempt succeeded though you made absolutely no change from the previous build and sort of hope the compiler will be merciful this time around.

It is the part of the brain that still believes in supernatural stuffs I guess.