Thanks to everyone who supported me and contributed ideas over the past nine months! Here’s where I think we are and where we’re going:

So, today, for the first time in 25 (!) years of Apple, I downgraded. From the 2016 MacBook Pro to my 2013, which I had kept in a drawer...

It was pretty simple to do—Apple Time Machine backups let me do it with one click.

That first tweet captures, in two pictures, how badly Apple has “lost the plot” (to quote @wylieprof). On the right is the Apple MagSafe adapter, from 2013. On the left, what I had “upgraded” to.

Thanks, Apple! I really was nostalgic for worrying about yanking my computer off the table.

Oh and I really appreciated not knowing if my computer was charging. What was great was the little whoop sound you used, so that the speaker before me could be informed I was charging my laptop.

A thing which I unironically and enthusiastically believe which is unpopular among smart people of my acquaintance: financial engineering has in the recent past and present contributed substantially to human welfare. We should hope to see more of it.

Maybe more geeks need to meet someone who says “My job is teleporting value across time and space.”

Financial engineering is sort of a squishy term. I don’t primarily mean payments infrastructure or financial rails, although both of those involve substantial engineering.

I mean more “We took a thing and performed some alchemy, and now have a new thing.”

Except instead of alchemy it is generally quite a bit of math, a huge amount of contract law and due diligence, often an impressive amount of ops work, and a dusting of technology that web devs would recognize as such.

💬 I often get Q’s like these:

How did you get your first customers for WIP? How did you grow BetaList’s traffic? Etc.

Makers are looking to reverse-engineer success. I see it everywhere.

I don’t think it works that way and the answers to those questions are mostly useless. 💥

I have built dozens of different products over the last couple of years. The vast majority failed. 😭

Surely if I know the answers to these questions, but still fail over and over again, these answers aren’t that useful. 🤷‍♀️

So what’s a better question to ask? 🤔

99.9% of the questions I receive are about the products that did well. In a way that makes sense, because we quickly forget about those that didn’t succeed.

🧠 This is known as survivorship bias.

Focusing on what survived, while ignoring what made it survive in the first place.

The real question, what you really want to know, is this:

What makes @WIP, @BetaList, and to some extent @AllStartupJobs succeed where my countless other attempts failed?

What separates a failed product 👎 from a successful product 👍?

Honestly, I don’t know. I wish I did.

It’s like Steve Jobs said “I’ll know it when I see it.” 👀

Same is true when we make products. We don’t know upfront what will work. But once we see an inkling of a product that does have potential, it’s not that hard to spot.

Have you ever wondered why the sons and daughters of the colonial chiefs and guards who were collaborators live a good life while those of the MAU MAU fighters live in abject poverty?

***THREAD***

It should be known that the colonialists reached a point that they knew they had 2 leave Kenya since they couldn't handle the Mau Mau war & the world was moving toward accepting independent Africa.However,the colonialists devised an evil scheme that still eats Kenya upto this day

Under this scheme, the colonial state came up with a plan that saw the first crop of chiefly “big men” being empowered financially to take their children to schools and eventually have those children go to England for further studies...

...and eventually providing a ready-made socio-economic & political class whom state power could be entrusted in the post-colonial era.This explains why their children & grandchildren still hold majority of important positions in govt or in the private sector supported by state.

This also explains why children and grandchildren of these homeguards are always given preferential treatment when it comes to government appointments. Wewe na masomo yako you are always asking why you can never get a job in government...yet you're qualified..now you know.

Singing the Blues:
Taking Down an Insider Threat

"I had all of the advantages. I was already inside the network. No one suspected me. But they found my hack, kicked me off the network...

...and physically hunted me down."

Many pentests start from the outside, wanting to see how the perimeter might be breached.

This pentest started from the inside. My client wanted to assume they had already been breached, and, if breached, how far could an attacker go.

Could they stop me once I was inside?

So they snuck me in. Disguised me as a new employee. Gave me a work computer, an ID badge, an account in their system... hell, I even had a cubicle w/my assumed name on it.

The only person who knew who I really was was their CISO. Everyone else thought I was Jeremy in Marketing.

During most of the first morning, I completed onboarding, made introductions, and completed menial tasks.

But I had to act quick. I only had a week onsite. I had to hack their network while not raising suspicion.

So I set about it.

You have to understand... most "Internal Pentests" are straight forward. The hard part is breaching the network, but once you're inside, it's a target rich environment. End of Life computers, default passwords, everyone a Local Administrator...