The “making it” for variety of things have different time frames.

Fake it until you make it” is often dismissed as shallow, but it’s closer to Franklin’s truth. Faking it long enough is making it. The repetition of behavior, not the sincerity of belief, is what shapes character.

The time frame is dependent on how aligned your honest self is to your phony self[^1]

i'm referencing a post that can be found here: https://boz.com/articles/you-are-how-you-act

[^1]: https://en.wikipedia.org/wiki/Trueselfandfalseself?wprov=sfti1

The browser wars have officially begun and whoever participates is forced to improve the agentic flows and there would be (IMO) a local maxima beyond which prompt injection becomes a catastrophic vector.

If google chooses to not participate, a significant portion of people can choose to migrate off google chrome and google might lose a significant chunk of market share or something idk… only until things go belly up when really bad prompt injection events come to light

If google chooses to participate, then it’s over. Google chrome has a large market share and this means google will also be cornered into the aforementioned local maxima until damage is already done to small % of affected users. small % but large absolute number.

Prompt injections cannot be stopped until something novels comes about. but for time being it’s not looking good for google (in near term atleast). happy to be wrong about it.

i'm referencing a post that can be found here: https://x.com/daniellockyer/status/1980895459670634933?s=12

You must’ve heard the “why is my washing machine sending soo much data to cloud?” joke from a few years ago.

Well, now replace ‘washing machine’ with ‘bed’

Quoting Michael Zimmermann

Is 16+gb/mo a normal amount of telemetry? Can you not do any local compute of “get hot” or “get cold” with a multi core processor and multiple gigabytes of memory? Can’t just repeat the previous nights settings?

It’s bad enough that you slapped a $ 200/yr subscription on things, worse that it doesn’t work at all without internet.

This whole thing came to light after many instances of EightSleep mattresses (pods) stopped functioning due to an AWS outage (which is hilarious and horrific at the same time).

This reminds me of a joke (and a truth):

If you want to know how dependent something is to the world, turn it off

A single high-value region on AWS went down recently and several external entities were disrupted and EightSleep pods were one of them.

EightSleep is fine but anything else that’s very critical is not.

This global incident should be a wake up call for dependent services to plan and support failovers. For consumer products to support offline mode. (either ways for a temp controlled bed to depend on cloud to function normally is ridiculous to a layman).

i'm referencing a post that can be found here.

I tried to make a joke on x dot com

feature, not a bug

All on-call engineers should be hooked up to @eightsleep pods whose functioning is dependent on current uptime of the services they are up-keeping :)

DHH on freedom and software:

Omarchy, Rails, Kamal, Hotwire, and all the rest of it doesn't have to return anything on the investment beyond the joy of building something awesome and sharing it.

I have no interest in commercializing any of this.

i'm referencing a post that can be found here.

Today I learned that the generic function with multiple implementations based on the types of the a single arguments are called as single dispatch functions.

I'm dropping a reference to the mention on the official python 3 documentation

I don’t particularly like resource contention irl

I found Guido Van Rossum casually answering python queries on X

It's to my detriment because sometimes my speaking thread out-executes my thinking thread”

I too speak faster than I think and this is similar to explanation I give to my peers 😂😭😭

https://x.com/karpathy/status/1979644538185752935?s=46

Shipping with assertion turned on, should ideally be done from the projects' inception and not when project is already being used by customers.

The point I'm trying to make is that if you and you're team are still working on fast iteration cycles and aren't there yet, you can slowly adapt to using asserts in production code, and not all at once.

Turning asserts on in production codebase is definitely a way to help team build fast iteration cycles in terms of Nth order effects.

They learn (or) you go belly up. You choose. It's a do or die thing.