Nick Andre

6.2K posts

Nick Andre

Nick Andre

@nickandre

information security, hackery, nutrition, photography, and occasionally photos from failed car repair. I love bacon.

Seattle, WA Присоединился Haziran 2011
307 Подписки1.1K Подписчики
Nick Andre
Nick Andre@nickandre·
@1a1n1d1y I’ve stopped using the 1m context window for most things. These patterns get much more likely when your context exceeds 200k. I had it go completely schizo and had to spend an hour extracting the context to transfer to a new session.
English
0
0
1
11
Nick Andre
Nick Andre@nickandre·
@1a1n1d1y They definitely added a “you should go shower bro” feature that has this unintended side effect. A few weeks ago it started asking if we should quit for the night. Seems to inject this sort of behavior pattern.
English
2
0
1
18
andy
andy@1a1n1d1y·
presented without comment
andy tweet media
English
299
99
2.5K
453.6K
Gain of Fauci
Gain of Fauci@DschlopesIsBack·
Christina Koch has officially become the farthest any woman has ever traveled from the kitchen.
Gain of Fauci tweet media
English
834
1.8K
27.7K
1.2M
Nick Andre
Nick Andre@nickandre·
We all been making fun of @Apple for bungling the AI rollout but jokes on us: they have the most important feature implemented from day 1. @Microsoft might be able to learn something here.
Nick Andre tweet media
English
0
0
0
23
Nick Andre
Nick Andre@nickandre·
@adamghaida The real lie was when they were claiming 2 9s of uptime until today 🤣 I think it’s the cost of moving fast tbh.
English
0
0
1
45
adam ghaida
adam ghaida@adamghaida·
jesus what is happening
adam ghaida tweet media
English
293
61
1.7K
482.9K
Three Year Letterman
Three Year Letterman@3YearLetterman·
@jonatanpallesen A 130 IQ isn’t possible. I have a 104, and that’s 4 points above the highest score you can get - there’s no way anyone out there is 26 points above me
English
65
4
1.6K
21.8K
Nick Andre
Nick Andre@nickandre·
Example of my Python image rendering versus the native windows driver. Kinda wild this stuff would not be doable by mere mortals with a job.
Nick Andre tweet media
English
0
0
0
31
Nick Andre
Nick Andre@nickandre·
Claude successfully reverse engineered the driver and nozzle patterns of a Chinese Newyes inkjet printer. It also enabled me to identify an error in their firmware USB stack as well as identify that their nozzle map in their driver was off by one. wild. github.com/nickandre/newy…
Nick Andre tweet media
English
1
0
0
114
Nick Andre
Nick Andre@nickandre·
I agree with the first half but am unsure about fundamentals. My experience in college from the BC (before Claude) era of taking down the CS computer network with a UDP storm during coding of a networking project is instrumental towards my knowing how to use Claude efficiently. From my personal experience people who are good at Claude can just fucking figure it out in about 4 weeks and develop an addiction to it where they’re clauding with bloodshot eyes at 3AM and trying to figure out the next market opportunity for the new software system. I don’t think you can teach that skill I think it’s a knack. I think the compounding effect of your hypothesis on employment pipelines is that in the BC era we needed large bureaucracies of SWEs to do things slowly and with a million meetings but in the modern era a lean team of a few (previously “10x”) engineers can power an entire engineering organization. So for the up and comers who were destined to be that annoying petulant bitch who waxed philosophical ad nauseam about “code quality” the market has entirely evaporated unless they are already embedded within such a bureaucracy. And such bureaucracies will in short order be an endangered species.
English
0
0
1
1.2K
Aakash Gupta
Aakash Gupta@aakashgupta·
The CS job market tells two stories, not one. MIT’s placement rate is 97%. UMD just reported 93%. Purdue’s 2025 grads averaged $108K starting salary. Top-tier CS programs are operating like nothing happened. Meanwhile this mid-tier state school went from 89% placement to 19% in four semesters. Average salary dropped $33K. Half the career fair was MLMs. That professor saying “we’re teaching students to build the systems that eliminate their own jobs” isn’t being dramatic. They’re describing the actual curriculum-to-employment pipeline at their institution. The numbers explain why. CS degrees doubled from 52,000 to 113,000 per year over the last decade. Universities kept expanding enrollment because the demand signal from 2021 said “hire everyone.” Then three things happened simultaneously: tech companies overhired, corrected with 250K+ layoffs across 2024-2025, and started replacing junior engineering tasks with AI tooling. The entry-level funnel collapsed while the supply pipeline was locked in at peak capacity. CS unemployment for recent grads hit 6.1% in 2025. That’s nearly double philosophy majors at 3.2%. The “learn to code” era produced a generation of graduates competing for jobs that are either gone or now require 3+ years of LLM integration experience they couldn’t possibly have. The split is geographic and institutional. If you’re at a top-15 program in a tech corridor with two internships on your resume, the market looks tight but navigable. If you’re at a mid-tier state school with no internship pipeline, you’re watching the career fair fill up with insurance companies while your $140K in loans accrues interest. That faculty meeting fight about “pivoting to AI collaboration skills” is the right debate happening two years too late. The schools that retooled their curriculum in 2023 will survive. The ones still teaching data structures as the core value proposition while job postings demand LLM orchestration are training students for a market that no longer exists. And the parent meetings are going to get worse. Because the next cohort is already enrolled.
Tech Layoff Tracker@TechLayoffLover

A CS professor at a mid-tier state university just sent me their internal placement data Fall 2023: 89% of their graduates had offers by graduation. Average starting salary $94k Spring 2024: 71% placement rate. Average dropped to $78k Fall 2024: 43% placement rate. Those who got offers averaged $61k Spring 2025: 31% of graduates employed in software roles six months out This semester? 19% placement rate and falling Faculty meeting last Tuesday got heated when the department chair suggested "pivoting curriculum toward AI collaboration skills" One professor stood up and said "we're teaching students to build the systems that eliminate their own jobs" The career fair last month had 12 companies show up. Half were MLMs and insurance sales Students keep asking why they're learning data structures when the job postings all say "3+ years experience with LLM integration" Professor told me the hardest part is the parent meetings "My daughter took out $140k in loans for this degree and she's working at Starbucks" Meanwhile the university is still running ads promising "94% job placement rates in high-growth tech careers" The disconnect is crushing everyone involved Faculty knows the industry has fundamentally shifted but the marketing department is still selling the 2019 dream These kids mortgaged their futures for careers that evaporated while they were in class

English
78
171
1.8K
482.4K
Nick Andre
Nick Andre@nickandre·
AI coding philosophy musings: Base Claude is 10000x more productive than I was before — it requires that I can think laterally. Not everyone can. The new skill is “can I teach this ADD-laden rowdy 12 year old who is also a servant to do what I need.” Optimizations and day to day shifts will modulate the productivity between 5,000 and 20,000x but the skill of working with the chaos machine is the key benefit. The old philosophy of code quality and domain expertise is gone. Anyone who dismisses the value of the new tools offhand is to be ignored. “I once tried to use a drill and cut myself therefore drills are bullshit.” The workflow is “can I second order infer based upon the responses what next context I have to drip feed in what order to restore this chaos to the right direction.” The best analogy is a rusty 1997 Chevy S10 with a cinder block on the gas going down a snowy road with your goal being to pile up snowbanks on either side to keep it moving directionally forward. Conservative thinking is gone. Hail Mary with a plan B to regress context only as needed is how things will be done efficiently. We now push the model to the absolute extreme and then walk back towards specificity only as needed. This allows us to discover the limits as the situation improves. It’s sufficient to focus on the core skill without worrying about the syntactic sugar. Features be flying. Swap notes but it’s ok to hunker down for a week and actually do things. We can adapt in the future as long as we remain adaptable. I’m back to coding though sail on sailors 🫡
English
0
0
1
81
Nick Andre
Nick Andre@nickandre·
@seconds_0 I wish you the best of luck but if you give in lmk I’ll give in as well.
English
0
0
1
265
Nick Andre
Nick Andre@nickandre·
@richcollins @dlandre @trq212 What I love about this whole present situation is it’s entirely immediately evident who the real engineers are because we all be swapping notes as frantically as possible to optimize this chaos 🤣
English
0
0
2
21
Rich Collins
Rich Collins@richcollins·
@nickandre @dlandre @trq212 The release rate is wild. I used to get excited about new products and features but now it's almost disheartening since I can't keep up!
English
1
0
1
23
Thariq
Thariq@trq212·
Voice mode is rolling out now in Claude Code. It’s live for ~5% of users today, and will be ramping through the coming weeks. You'll see a note on the welcome screen once you have access. /voice to toggle it on!
English
1.1K
1.3K
17.3K
3.6M
Nick Andre
Nick Andre@nickandre·
@richcollins @dlandre @trq212 The feeling when you’ve spent a few weeks actually using Claude code to code and miss out on the fact that they’ve rolled out new features 🤣 here I am cave manning it with a regular old chrome browser.
English
1
0
1
47
Rich Collins
Rich Collins@richcollins·
@dlandre @nickandre @trq212 I would like to use some of the Desktop app only features like Preview. I'm sure I could figure out how to do something similar in the shell though.
English
1
0
0
36
Nick Andre
Nick Andre@nickandre·
@richcollins @trq212 Guess we have to use the fallback of bumping techno and staring at the same console through the night.
English
1
0
1
23
Rich Collins
Rich Collins@richcollins·
@trq212 Would like to use desktop app but it keeps dropping my requests when I switch sessions. That a known issue?
English
1
0
1
155
Nick Andre
Nick Andre@nickandre·
@nicknorwitz This clocks. I recall chatting about it at the time and the calculated data failed like basic first principles check. Like you can’t have a steady state environment with an average duration of 4 years where the delta between year 3 to 4 is greater than the baseline quantity.
English
0
0
7
781
Nick Norwitz MD PhD
Nick Norwitz MD PhD@nicknorwitz·
I feel like I can breathe again! Get ready for a rant I've been waiting to let loose for a year. 🔥 First, here are the core facts about the Keto-CTA study to date: 🚨PART 1: THE FACTS 👉From its inception, Dave, Adrian, and I, being associated via the funding body (the Citizen Science Foundation), were blinded to certain elements of the data. The purpose was to protect the integrity of the project. 👉The profound irony is this also meant that, prior to publication, we couldn’t perform certain ‘checks’ and had to trust others to do so. Speaking for myself, it’s now painfully clear that was a mistake. 👉However, after the April 7th paper was published, "anomalies" (if I’m being polite) were noted with the Cleerly scans. 👉 Cleerly refused to redo the scans, despite multiple requests and being offered payment. 👉Importantly, and to my dismay, the original Cleerly reads were UNBLINDED, introducing a major source of bias. 👉At additional expensive, the scans were rerun through HeartFlow in a properly blinded analysis, and via the pre-specified QAngio methodology. 👉HeartFlow and QAngio agreed with each other and were discordant with the Cleerly analysis. 🚨PART 2: THE NEW NEWS What happened next was brilliant! And, truth be told, I only found out about it yesterday. For my own legal security – and at the recommendation of my friend and colleague who was taking the worst of it on the back end – there was a lot I didn’t know until this point. This is what happened… 👉Several participants independently submitted their scans to Cleerly as a workaround to obtain a truly blinded Cleerly analysis. 👉Those results were highly discordant with the original Cleerly analysis and aligned with the HeartFlow and QAngio analyses. The difference between the original Cleerly scans and the repeated blinded scans was massive! The original unblinded analysis reported a +20.9 mm³ mean increase in non-calcified plaque volume, while the blinded repeats showed a -5.1 mm³ mean decrease. I mean, MY GOODNESS!!! I basically did a backflip when I found out (@realDaveFeldman can release the footage of the meeting at his discretion) If you’ve been following the KETO-CTA story up to this point, the consistency of the findings across HeartFlow, QAngio, and now Cleerly itself (based on the blinded reads) should bring much-needed clarity. The converging results fundamentally reshape the narrative and directly refute the claim that the study demonstrates massive, unprecedented plaque progression in LMHR and near-LMHR And, after all that, the fact remains that every single analysis found no association between ApoB levels or LDL exposure and plaque progression. LET ME REPEAT: And, after all that, the fact remains that every single analysis found no association between ApoB levels or LDL exposure and plaque progression. 🚨 PART 3: NEXT STEPS In terms of next steps, I’ll quote my colleague Dave: “we have already taken steps regarding last year’s paper that contained the original Cleerly analysis.” I’ll leave it at that for now so I don’t overstep. But let me say, that’s the highly polished and diplomatic version. I certainly have stronger words about this process, but perhaps now is not the time. Where I will speak more plainly is in regard to the behavior of some detractors over the past several months. In a few cases, I’ve reached out privately to individuals who should know better, gently suggesting that, in light of the new evidence (Heartflow and QAngio), it might be time to reassess or lighten the abuse. For anyone sincerely paying attention—and for anyone with even modest insight into how scientific bureaucracy works—I hope it is now clear why we were not more forthcoming earlier in the process. 👉And trust me when I say, it’s never been harder to keep my mouth shut about anything in my life. I've accumulated more cortisol AUC in the last 11 months then in the entirety of my life to age 29. 🚨PART 4: SPEAKING FOR MYSELF Speaking for myself, I have been beyond frustrated and disappointed. At multiple stages, it has become painfully—and increasingly—clear to me that our scientific system, which presents itself as purely meritocratic, is far more political than most would imagine. These are difficult words for me to say as someone who comes from a family of doctors and scientists and who has spent his entire career in academic institutions—multiple Ivy League universities @Harvard @dartmouth, two doctorates, and top-ranked institutions in both England @UniofOxford and the United States. I was groomed in conventional academic medicine. If I have any bias, it’s to see the best in conventional medicine and modern scientific process. Most of my loved ones have made their living within this ecosystem. But when you pull back the curtain, the reality can be sobering. To those detractors who have verbally abused or personally attacked my colleagues and me—perhaps out of naivete or ignorance—I will say this plainly: it’s time to check yourselves. Too many people have spoken out of turn, seemingly to score points rather than to engage thoughtfully with an evolving scientific story—one that has been evolving for quite some time. When the HeartFlow and QAngio analyses were released, that alone should have prompted serious reflection. At minimum, it should have raised questions. The subsequent silence from some of the loudest critics, after they believed they had “won” a round, is telling. Science deserves better than scorekeeping. It deserves intellectual honesty and the humility to update one’s position when new evidence emerges. At times over the last year, the lack of curiosity, sincerity, and intellectual honesty from people who I tried to give the benefit of the doubt has made me want to vomit. And trust me when I say, this isn’t a victory lap. This is a promise. We are now over a hurdle that I have been waiting for almost a year. And frankly, I am ready to run headfirst through brick walls with my colleagues and friends by my side — those whom I trust to pursue the hard questions and the honest answers — and do so indefinitely using the tools and resources at our disposal, even when, and especially when, the scales are improperly tilted against us. Lucky for us, the intellectual environment is expanding — the black box of academia beginning to crack open. So someone hand me a crowbar, because I’m committing myself fully and completely, over the coming years and decades, to prying it wide open. Not gently. Not quietly. But decisively. My final words of this verbose dissertation? LFG
Nick Norwitz MD PhD tweet media
Dave Feldman@realDaveFeldman

I want to share a crucial update on our study, KETO-CTA. (The video for this article is in the next tweet) Our study recruited 100 participants, each undergoing two high-resolution heart scans, known as CT angiograms, one year apart. (For more background on this study design, see preprint in the following tweet) There are now four analyses of those same 200 scans. But one of those analyses stands out — and I have some new developments to report. For a quick background, the first quantitative analysis was from an AI company, Cleerly. We published their analysis of our scans last year. After the paper was published, the Citizen Science Foundation was free to look at the raw Cleerly data, and we found a number of patterns that appeared different from what is typically seen in other coronary plaque studies. For example, in Cleerly's analysis, not one of the participants showed lower plaque levels at follow-up — even though CTA scans typically show some natural variation in both directions, especially in people who start with very little plaque. For another example within their data, people with no detectable calcium in their scans appeared to have several times more plaque progression than those who already had some calcium present. This runs counter to what many in cardiology call the "power of zero" — the well-established finding that having no coronary calcium is typically associated with lower risk and slower disease progression. Another major development: shortly after publication, we learned that the scans Cleerly was analyzing were not fully blinded. In studies like this, the order of scans is typically kept unknown to the analyst to help prevent any potential for bias. But in this case, the chronological order was available in the scans. We therefore asked Cleerly to repeat their analysis using a properly blinded set of scans, which is standard practice in longitudinal studies. Cleerly declined to perform a blinded reanalysis. Because of this, we commissioned an additional, independent analysis from Heartflow. Heartflow has been a leader in this space and is the most extensively validated AI platform for coronary CTA analysis. The Heartflow analysis was conducted with full operational blinding and completed right before the prespecified third, and final quantitative analysis, which uses Medis QAngio. These two independent platforms were consistent with each other, yet both differed substantially from the Cleerly results. As these independent results became available, we shared them privately with Cleerly and again requested a blinded reanalysis of their original work. We offered to cover any costs involved just in case this was the barrier to reanalysis. Cleerly again declined. However, a new development emerged. Several participants requested their scans from the study and submitted them directly through their own, personal cardiologist. Any cardiologist with a proper Cleerly account can appropriately submit scans on their patient's behalf. So in a sense, our participants themselves were able to provide a portion of the blinded analysis we were originally requesting. This was then shared with me on behalf of the Citizen Science Foundation. In total, there are 19 of these individual submissions — about 10% of the total scans in our study so far. Individual Submissions vs. Study Data We focused on the 8 participants who have both a baseline and a follow-up individual submission of their scans (the other 3 submissions are unpaired). [Please Note: These data are preliminary] Figure 1 compares the change in soft plaque (Non-Calcified Plaque Volume or NCPV) reported by the original Cleerly study analysis against the results from each participant's individual submission. [See Figure 1] Of the 8 participants, four showed an increase in soft plaque in both datasets — but in three of those four cases, the individual submissions reported substantially less progression than the study data. The remaining four participants all showed progression in the study data, yet every one of their individual submissions showed a decrease — a complete reversal of direction. The largest discrepancy was a single participant whose study data reported an increase of 32 mm³, while their individual submission showed a decrease of 48 mm³ — a reversal of approximately 80 mm³. The median change in soft plaque for these 8 participants was +20.6 mm³ (a 31% increase) in the original study data, compared to just +0.7 mm³ (about a 2% increase) from their individual submissions (Figure 2). The mean average is even more pronounced: the study data shows an average increase of +20.9 mm³ (42% from baseline), while the individual submissions show an average decrease of 5.1 mm³ (an 8% decline). In other words, the study data says plaque went up; the individual submissions say it went down (Figure 3). Direction of Change Across Platforms To put these individual submissions in broader context, Figure 4 compares the direction of soft plaque change across three analyses of these same scans. On the left is the original Cleerly study analysis — 99 participants after excluding one who had a procedure between scans. 98% showed an increase in soft plaque. Only 2 showed no change. Zero showed regression. In the middle are the 8 individual submissions, split right down the middle: 50% showing progression and 50% showing regression. On the right is the full Heartflow analysis across 95 participants. While 8 is a small sample size, the direction-of-change in these individual submissions is far closer to the Heartflow analysis than the original Cleerly analysis. It is worth emphasizing: 4 out of the 8 participants — fully half — received individual submission results showing less plaque in their second scan than their first. But after accounting for the single exclusion mentioned above, not one of the 99 participants in the original Cleerly study analysis showed plaque regression. We are not sure what happened with the original Cleerly analysis. We just know the other analyses are largely consistent with each other — and now, that includes these individual submissions to Cleerly as well. Next Steps We have already taken steps regarding last year's paper that contained the original Cleerly analysis. We are working with the journal on that now, and we expect news on this very soon. In the meantime, the preprint of our current paper with both Heartflow and QAngio results is available at the link below. Importantly, the two principal findings reported in the original paper have been reproduced in both the Heartflow and QAngio analyses: (1) baseline plaque strongly predicts future plaque progression, and (2) ApoB was not associated with plaque progression I want to once again thank Dr. Budoff and the Lundquist team for providing these scans to study participants who request them. If you are a participant in our study and interested in sending in your scans through your cardiologist, we now have a budget to help cover the cost of that submission. You can contact us at info@citizensciencefoundation.org for more details. Thank you again to everyone for your support. 🙏 cc @nicknorwitz @AdrianSotoMota

English
104
198
978
366.7K
Nick Andre
Nick Andre@nickandre·
@trq212 Nothing like my morning ritual of brewing a cup of joe and brewing the daily update to Claude code to get rid of the harassing yellow warning message.
English
0
0
1
81
Thariq
Thariq@trq212·
We've reset rate limits for all Claude Code users. Yesterday we rolled out a bug with prompt caching that caused usage limits to be consumed faster than normal. This is hotfixed in 2.1.62. Make sure you upgrade to the latest and hope you enjoy using Claude Code this weekend!
English
727
449
11.1K
1M
Anthony Morris ツ
Anthony Morris ツ@amorriscode·
SSH support is now available for Claude Code on desktop Connect to your remote machines and let Claude cook, TMUX optional.
English
348
318
4.4K
1.6M
Nick Andre
Nick Andre@nickandre·
@elonmusk Ok. But why does anyone care about its opinion on the matter? If blender goes full Texas chainsaw massacre I won’t stop to ask it for its feelings before I pull the plug…
English
0
0
0
62