@MikhailaFuller 1. How was it determined that his "flare up" was induced by mold exposure?
2. How was he diagnosed with "neurological injury"?
3. What is the biological mechanism of the onset of his "neurological injury"?
@dfolloni@cline The scariest part to me is the 'legitimate' GitHub repo getting compromised. You can't trust legitimate repos because of this. It's more important than ever to scrutinize all scripts before execution.
Imagine you're John Carmack
you're 22 years old and you just wrote a 3D engine in assembly that runs at 35fps on a 486
Doom drops. Quake drops. Half the planet is playing your code.
you're the reason GPUs exist. you're the reason your friend Jensen has a yacht today.
then in 2009, you sell id Software. people call it betrayal. you call it "they made an offer I couldn't refuse."
VR obsession. Oculus. Meta buys it for $2B. you're CTO.
but Meta thinks you're a liability. your demos are "too intense." your emails are "too long." your focus on frame timing is "slowing us down."
2022. they push you out. not fired officially. just "restructured."
the media writes "end of an era." some crypto bro calls you "washed up."
silicon valley moves on.
but you don't.
you don't write a book. you don't start a podcast. you don't collect speaking fees.
you go completely quiet.
you take the money. you buy a warehouse in Texas. you hire 10 engineers. and you start coding.
not games. not VR.
AGI.
two years. radio silence. no tweets. no conference talks.
while everyone's debating ChatGPT, you're debugging CUDA kernels at 3AM, testing world models.
then in 2025, Keen Technologies pivots hard. you're not "exploring" anymore. you're building it.
here's what people get wrong:
everyone calls it a comeback. a redemption arc. "revenge on Meta."
it's none of that.
you're a 54-year-old engineer who still codes 12 hours a day because you genuinely can't stop.
most CTOs would have bought an island. most legends would have written memoirs.
you just kept typing.
the most dangerous person in any codebase is the one who goes quiet and never stops shipping commits.
karma doesn't need to be real.
but obsession is.
welcome back, Carmack.
@atlfrz@karthikponna19 I noticed sluggishness and large memory consumption when I had a large project directory open. When I had a small (or none) project directory open, the memory consumption and responsiveness was great.
@brankopetric00 But that would indicate you didn't have full integration test coverage. Ideally, there would be through testing against actual interfacing services.