Why believing in fortune telling, tarot cards, and zodiac signs is major shirk 🧵

"The engineers on my team just want to code. They don't want to have anything to do with product. They just want specs. What do I do?"

1/n Are you asking them do to X *and* do their "day job" as defined by their managers (and frankly your roadmap) ?

If so, start there...

2/n Do they have a reason to believe that doing X will in any way improve the quality of the product and make their lives easier? Have they ever seen X "work" ?

Show don't tell.

3/n Is there average day/week a quagmire of unnecessary meetings, wading through tech debt, struggling to get *anything* to work ... and jumping through process hoops to prove their worth?

If so...no they will not have bandwidth.

4/n How do incentives work on the engineering team? Maybe they want to help, but their "grade" is determined by something altogether different.

"I'd love to, but I am on the hook to deliver [some project] this quarter to make a good impression..."

Talk to eng management.

5/n Have they had any time to practice?

Or did they get thrown into the deep end the first time they were given a shot ... expected to brainstorm on demand, be as vocal as practiced PdMs and designers, and "participate" !

Make it safe to practice. Reasonable expectations.

@ImPranav_M @GunduHuDuGa That's a good qsn, if not a bit nuanced. Avataras are of many varieties and frankly, most of the classification is only for our understanding and not really binding on Paramatma Himself. We can take several approaches to understanding this. If you go by a Vedantic approach,+

@GunduHuDuGa Avatara means that which descends from an exalted state (Taara). Going by Upanishadic observaton of Purnam adham purnam idham, every manifestation of Bhagavan is indeed wholesome. In fact, Avataras usually happen when Iswara is propitiated with certain qualities already+

@GunduHuDuGa described in the Vedas by other Devatas. So, in order to please them, He assumes the form that best envisages the said Vaidika tatvam. For example, Varaha and Nrusimha avatars, though they have sthoola prayojanas, also exemplify the Tejovanna tatvam propounded by Upanishads.+

@GunduHuDuGa All these tatvams ultimately emanate from Him so whatever form He takes is indeed Purna. Now, one may ask then if that's the case, why such a distinction had to be made in the first place. That is because of upasana vidhis and understanding of how Bhagavad tatvam shines+

@GunduHuDuGa with each Leela being performed. Let's take Nrusimha avatar. The purpose of the avatar is neither to save Hiranyakasipu nor rescue Prahlada. For that He need not descend down as H's boons are applicable only for Brahman's creation and not Paramatma Himself.+

So, here's my contrarian take on Why Trunk-Based Development Is Great But Probably Won't Work For You. Buckle up, it's a long one.

From time to time I talk about, or boost someone else's discussion of, "classical" continuous integration/trunk-based development/push-to-master/whatever. I do this because I've personally worked like this and I genuinely think it's a marvelous way to write software.

I've also, at this point in my career, failed—a bunch of times!—to bring this technique into practical use on the teams and organizations I've worked with. As a result, while I still do it myself, I don't focus as much on encouraging it in others.

The technoculture that's presently in vogue is what I think of as async/individual—optimize for the individual, performance-manage the individual, decouple the individual from others so they can be their best, most productive, most heroic selves.

This is in contrast to what I think of as sync/team—a culture that leans into interdependence and collaboration. If you've never worked on a team that collaborates very closely every day for months or years on end (and likes it) you've likely not experienced a team like this.