Even just one of the smaller models is good enough for the grunt work I use them for 90% of the time. Currently doing most of my home hobby projects with OpenCode Go and Qwen 3.7 Plus, it's not great at diagnosing issues in the code, but if I can clearly articulate a test suite or boilerplate refactoring it works fine.
I think you're missing the point OP was making. He's saying it's profitable but not optimal, those who recognised that quickly outstripped the slave owners in wealth.
I could ask you about your spending habits and why you don't pump all your money into an S&P 500 ETF, but that's ignoring time and consumption preferences you have, as well as perceived opportunity cost. It's not a useful observation to make at an individual level.
> We want to make these capabilities available to the scientists and research organizations best positioned to advance human health, while maintaining strong safeguards against biological misuse. The Life Sciences model is launching through a trusted-access deployment structure for qualified Enterprise customers in the U.S. to start, with controls around eligibility, access management, and organizational governance.
I'm absolutely ok with a legitimate lab scientist conducting biochemical research getting suggestions about substances that are generally considered dangerous but might be appropriate for their study, and it'll be up to the scientist to discern whether it is indeed appropriate to use.
I'm working on moving as much as possible to self hosted options. Have forgejo, Authentik and Nextcloud set up so far. Slowly finding alternatives for things, I think my next goal is Nostr
I think it's awesome that AI is enabling this. I think the the future of software engineering is in helping make this kind of thing resilient and removing the fragility that AI generated code always seems to inject
Just the hype seeking people left to Discord and Reddit to be able to lament about how these new places are awful and crying about phpBB and vbuletin being dead.
I always liked reading about it in uni in the mid-late 00s. It made me feel smart in my OS tutorials when I could rattle off all the design choices and how they differed from Linux and Windows
My observations match this. I can get fresh things done very quickly, but when I start getting into the weeds I eventually get too frustrated with babysitting the LLM to keep using it.
Last place I worked had long running end to end tests that would take 30 minutes on GHA (compared to maybe 5 locally) on every PR. This is going to make that a very expensive endeavour
We host a fair bit of Terraform code in a repos on GitHub, including the project that bootstraps and manages our GH org’s config: permissions, repos, etc.
Hilariously, the official Terraform provider for GitHub is full of N+1 API call patterns — aka exponential scaling hotspots — so even generating a plan requires making a separate (remote, rate-limited) API call to check things like the branch protection status of every “main” branch, every action and PR policy, etc. As of today it takes roughly 30 minutes to do a full plan, which has to run as part of CI to make sure the pushed TF code is valid.
With this change, we’ll be paying once to host our projects and again for the privilege of running our own code on our own machines when we push changes…and the bill will continue to grow exponentially b/c the speed of their API serves to set an artificial lower bound on the runtime of our basic tests.
(To be fair, “slow” and “Terraform” often show up and leave parties at suspiciously similar times, and GitHub is far from the only SaaS vendor whose revenue goes up when their systems get slower.)
reply