After a really productive few days, I thought it was a good time to update what’s happening Now. And as I was journaling what I was involved in, I realised benefits of my recent blogging habit — I had my microposts as reference. That’s one big positive.

★ Liked “Inside X, the Moonshot Factory Racing to Build the Next Google“

(..to qualify) It must involve solving a huge problem. It must present a radical solution. And it must deploy breakthrough technology.

May be that’s why Loon is all we hear.

“Magic Leap Finally Demoed Its Headset And It Is… Disappointing” – the valley between promises and reality keeps biting the tech media. When will we learn to not get excited by demos?

Though I agree with Daniel’s sentiment, it’s part of the overall cycle of creation – inspiration, ideation, implementation, appreciation, recognition. It is not must for all creations to pass through this, but it’s significant if one does.

So, AirPods remain the wireless earphones of choice for many, primarily due to the ease of use, design and comfort. Bluetooth is a hated technology amongst staunch audiophiles, Apple just made it bearable by making the experience frictionless.

I could be more sensitive to Musk's challenges. It's easy to leap on somebody who presents themself so willingly for public appraisal.

— Daniel Jalkut (@danielpunkass) July 12, 2018

One of the worst feeling is the helplessness you feel as you look into the painful eyes of your child down with fever, as they look back at you with a hope that you will abate this pain they are going through. Ah. Absolutely crushing! 😣

At times, I just wish I wasn’t following the technology space closely. My buying decisions would’ve been simpler, driven completely by what’s on display now. And not by the fear of roadmap, fear of remorse in future.

My MacBook is dying and I find nothing that can replace it.

I really liked this comment from a hacker news thread¹ on a post around how Microservices architecture failed a product’s dev team.

Everytime (sic) you touch something under a repo, it affects everyone. You are forced to use existing code or improve it, or you risk breaking code for everyone else. What does this solve? This solves the fundamental problem a lot of leetcode/hackerrank monkeys miss, programming is a Social activity it is not a go into a cave and come out with a perfect solution in a month activity. More interaction among developers means Engineers are forced to account for trade offs. Software Engineering in its entirety is all about trade offs, unlike theoretical Comp Science. Anyway, this helps because as Engineers we must respect and account for other Engineers decisions.

Working on a shared code is indeed a social activity. And this principle is something I just can’t stress enough when amongst my team. There is a misguided view of coders as lone warriors, sitting in the dark corner somewhere, beating at their keyboards and delivering working software day and night.

Reality can’t be farther in most work environments, especially enterprises. Every coder needs to be accountable, extra cautious with each line of code he or she commits to the repository. If not, it might lead to a sleepless night of debugging for the whole team.

★ Liked Throwing and Catching by Seth Godin

We spend most of our time in catching mode. In dealing with the incoming. Putting out fires. Going to meetings that were called by other people. Reacting to whoever is shouting the loudest.

But if we learn a lesson from jugglers, we realize that the hard part isn’t catching, it’s throwing. Learn to throw, to initiate, to do with care and you’ll need to spend far less time worrying about catching in the first place.