#SUGAR

Shared this update on sugar stocks in Feb on telegram.

Some of them have moved a bit but this is just the beginning.

Way sugar is setting up, it can very well replicate pharma rally of 2020.

However, looks extended on smaller tf. Will wait here for some retracement.

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.

The Ife Primary Education Research Project (1970-1983).

aka

The Ife 6-Year Primary Project.

In 1970, as the Director of the Institute of Education of the then University of Ife (now Obafemi Awolowo University, Ile-Ife), later Dean Faculty of Education, Prof. Babs Fafunwa & his team embarked on one of the most groundbreaking research projects in education for Yorubaland.

The aim of the project was to test the hypothesis that the best instructional medium for good concept formation at a very tender age is the mother tongue.

This was bolstered by the observation that “of all the continents and peoples of the world, it is only in Africa…

…that formal education is offered in a language that is foreign to the child.”

So, Yoruba was to be used & tested as an exclusive medium of passing information or instructions to a set of pupils.

The project was based on the premise that:

(a). the child will benefit culturally, socially, linguistically & cognitively.

(b). the child’s command of English will be improved if he is taught English as an entirely separate subject by a specialist teacher through the 6 years.

💬 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.

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.