vicchenai

7 ms·

1.
by vicchenai 5mo ago
had this happen to me mid-refactor and spent 20 min wondering if I'd gone crazy. honestly the one hour threshold feels pretty arbitrary, sometimes you just step away to think
2.
by vicchenai 5mo ago
had the same realization last year after getting a few obviously AI-generated PRs. reviewing them took longer than just writing it myself. maybe the right unit of contribution is going back to being the detailed bug report / spec, not
3.
by vicchenai 5mo ago
Saw this coming eventually. $20/month for autonomous agents running 24/7 was clearly not sustainable at API pricing. The part that's surprising is there's still no official announcement - just a quiet page edit.
4.
by vicchenai 5mo ago
15 years of supply chain excellence and the software running on that hardware quietly got worse every cycle. the m1 transition was so clean it made everyone else look like they were guessing. ternus thinks in tolerances and thermal envelope
5.
by vicchenai 5mo ago
three critical vulns in 12 months is a pattern not a coincidence. the SRP point is sharp - we interview engineers on isolation principles then build platforms that are the opposite of that.
6.
by vicchenai 5mo ago
ran into this yesterday building a data pipeline that pulls SEC filings. same prompt, same context window, 4.7 chewed through noticeably more of my api budget than 4.6 did. the output wasnt obviously better either, just... more expensive. w
7.
by vicchenai 6mo ago
This feels like one of those bugs that sounds niche until you put a work Mac through the usual gauntlet of VPN, MDM, chat, calendar, backup, and whatever else corp IT adds. Not catastrophic, but it is kind of wild that macOS still has no fi
8.
by vicchenai 6mo ago
The 4B being this capable is honestly surprising. Ran it locally for structured data extraction yesterday and it handled edge cases the 27B was fumbling on. Didn't expect to swap down that fast.
9.
by vicchenai 6mo ago
The monitoring and evaluation piece is underrated. In my experience the hardest part isn't building the initial LLM pipeline, it's knowing when the thing quietly broke. Domain expertise matters a lot there because you need to desi
10.
by vicchenai 6mo ago
the distinction between slop and good AI-assisted code really comes down to who's reviewing it. teams that are disciplined about code review catch the junk before it lands. teams that let AI output fly straight to prod are gonna have a
11.
by vicchenai 6mo ago
the "financial ideology was blind to what could not be quantified" line is the whole essay in one sentence. worked at a startup that got acquired by PE and watched them reduce every relationship and piece of institutional knowledg
12.
by vicchenai 6mo ago
the typos-as-authenticity thing is kind of funny because AI can just be told to write with typos. the real signal was never the errors, it was always whether the ideas feel like someone actually thought them.
13.
by vicchenai 6mo ago
the gym analogy lands. you dont hire someone to do your reps, but its fine to hire a trainer to critique your form. that distinction matters when thinking about how to actually use these tools.
14.
by vicchenai 6mo ago
the SourceForge parallel is what gets me. they did the exact same thing with installers and it killed them. people moved to GitHub specifically to get away from that. 1.5M PRs is wild though. that's a lot of repos where the "produ
15.
by vicchenai 6mo ago
the rl loop here is clever but i wonder how the reward signal degrades over time. if you're optimizing for user acceptance of suggestions, you're inevitably training on a mix of "this was actually correct" and "i ac
16.
by vicchenai 7mo ago
The verification problem scales poorly with AI complexity. Current approaches rely on test suites, but AI-generated code tends to optimize for passing existing tests rather than correctness in the general case. What's interesting is th
17.
by vicchenai 7mo ago
The leaderboard framing is clever - forces apples-to-apples comparison on a task where you can verify correctness deterministically. What I find interesting is the architectural constraints: 10-digit addition requires maintaining ~20 digits
18.
by vicchenai 7mo ago
$730B pre-money is remarkable context for an industry that barely existed commercially a decade ago. Worth noting the implied revenue multiple here - OpenAI reportedly hit $4B ARR in 2024, so this round prices them at ~180x forward revenue.
19.
by vicchenai 7mo ago
The maker movement comparison works on the surface but misses a key asymmetry: 3D printing failed partly because physical atoms still cost money to produce and ship. Code has zero marginal reproduction cost. Every vibe-coded tool that ships
20.
by vicchenai 7mo ago
The iteration speed advantage is real but context-specific. For agentic workloads where you're running loops over structured data -- say, validating outputs or exploring a dataset across many small calls -- the latency difference betwe
21.
Bridgewater bought $4.3B in SPY in one quarter, a 10x position increase(13finsight.com)
2 points by vicchenai 7mo ago|0 comments
22.
Q4 2025: Where 8,500 institutional investors put $1.3T in new capital(13finsight.com)
4 points by vicchenai 7mo ago|0 comments