I already submitted my take on this to Show HN: https://currantfeed.cc/. Noone gave a shit so it's most likely a very bad idea and certainly a very steep uphill battle. It's basically an Airbnb for websites that by default randomly sorts them and then you can filter by different attributes. Owners have to submit and maintain their "listings". It does have an optional subscription (I'm not sure if it works haven't tested it).
Oh and lame-self-comment, but it's at least partly EU stack: Hetzner and Brevo for hosting and transactional mails, Umami for the non-existing analytics.
As others have said it's just a fraction. I'm in a medium size tech-related company and we have 7500+ in one Github org. We have two orgs, so altogether easily 10K+. Of course most of it is stale, obsolete, sandbox, personal tools, etc. I wouldn't be surprised if Github would have 100K+ internal repos or even more.
Sorry for my ignorance, but then couldn't we build this into NPM itself? So before a package is publicly available it would be quaranteened and checked.
I’m running a local Whisper + Gemma 4 pipeline with a cheap USB mic to extract health related data and potential todos from ambient speech. It doesn’t have to be fast doesn’t have to be 100% correct because if it captures at least a few bits of interesting information that would otherwise go unnoticed it’s still a win.
I'm starting to feel like a parrot, but people seem to forget that software engineering is actually a very narrow slice of the white collar pie. You don't need a mega-model which can reason about 100 000 lines of code when you want to create a nice PPT (which consumed literally hours of your life before) to impress your boss. SOTA models will probably be used for frontier research, complex coding tasks, large scale data analysis, etc. And the average Joe shall be able to buy a pre-configured box with a plug-and-play harness and run medium models air-gapped. Or use such models through cloud APIs dirt cheap if privacy is not a concern.
I was thinking about this and there are several aspects that can still make this viable. 1) AI labs are incentivised to increase token consumption because literally that's their product. The only thing they sell AFIAK are tokens (and maybe a teensy bit of user data). So if you build a product that is actively reducing token consumption (which they simply cannot do without hurting themselves even if their marketing fluff says otherwise) you'll save large amounts of money for your customers and they'll choose you. 2) Big providers want to funnel every prompt into their servers. If you're in a regulated market or simply don't want to share every detail with an American or Chinese megacorp you are in trouble. BUT open weight models are now quite capable for "small business stuff" and they can be self hosted. If you can bundle this into your service, in other words actually care about their privacy, they will choose you. Even more so if you're in Europe.
The only place I'd ever talk to a machine is my car. Instead of huge flashy screens that distracts and kills thousands of people maybe they could build a buttons + voice agent system that could actually be useful and durable. I hate to tap Waze/Maps/etc. every time when I go somewhere or that I cannot comfortably switch to specific songs en route without risking my life...
Yes... I mean organisations have to adapt to this new working scheme. First they need new processes (maybe borrowed from SW development) that enables them to triage work products on a risk/reward scale. For example my wife works on medical device tenders. It is obligatory to translate every frikkin Word document to our native language which in the end noone will read. Do we use LLMs to do the translation? Hell yeah. For a critical legal document? Eeee. Also I think enablers like speical harnesses shall be developed/improved by keeping these folks in mind. For example to build hooks into the harness that forces the LLM to test/review/sample its output. So yes it's a complex topic, but my point was rather that the inherent capabilities of medium-large-ish open LLMs are sufficient for let's say 70-80% of such office work, and it's a huge market.
Critics are (rightly) pointing to the fact that these models are not on par with SOTA for complex coding tasks. But many seems to forget that a large part of white collar office work is Excel crushing, file moving, translating dry legal documents, e-mail drafting, PPT drudgery, etc. These are absolutely doable with 30-35b+ models with the added benefit of keeping company data private.
Perhaps you can create a compelling UX around it and sell it as a subscription. "Normies" will not be able/willing to build it. You can then patch the model/ship new features around it as it evolves. For example I have built an ambient todo list / health data extractor using Gemma 4 2EB and Whisper. Nothing to brag about but it does fairly decent job even in foreign languages.
I mean an LLM is a slightly stirred up soup of current human knowledge. It has an advantage in quantity of accumulated data and maybe connecting seemingly less connected parts of that data - but not reliably. The human has an advantage (for now) in data collection (seeing, hearing sensing the patient), actual agency, real world experiences and getting the useful data out of the stirred up soup. Both human and LLM are susceptible to bias and harmful influence. Let’s simply isolate them in the diagnostic process and then compare their output. Human collects data -> both human and LLM evaluate independently -> compare the results -> human may get new insights -> final diagnosis by human.
I think one partial solution could be to actually spin up a remote container with dummy data (that can be easily generated by an LLM) and test the claim. With agents it can be done very quickly. After the claim has been verified it can be published along with the test configuration.
LOC is a very-very weak proxy of "how many new features" I've built, and they don't have any other metric that can be measured easily. But it causes serious issues, because equating LOC with productivity leads to inevitable utter bloat, that no agent or human can ever rectify in a meaningful timeframe. I'm pretty sure this 600 000??? LOC could be shrinked to 60 K for the same feature set, but with better readability and performance.
Others have already partially answered this, but here’s my 20 cents. Software development really is similar to architecture. The end result is an infrastructure of unique modules with different type of connectors (roads, grid, or APIs). Until now in SW dev the grunt work was done mostly by the same people who did the planning, decided on the type of connectors, etc. Real estate architects also use a bunch of software tools to aid them, but there must be a human being in the end of the chain who understands human needs, understands - after years of studying and practicing - how the whole building and the infrastructure will behave at large and who is ultimately responsible for the end result (and hopefully rewarded depending on the complexity and quality of the end result). So yes we will not need as many SW engineers, but those who remain will work on complex rewarding problems and will push the frontier further.
Managed BYOK stateless agent orchestrator called BeeZee: https://beezyai.net/. Basically Claude Cowork / a coding agent on the web but provider agnostic, you own the data and you can connect several nodes to it. Instead of installing an agent for all your machines you have one master agentic server and executor nodes. The server is stateless the data lives on the nodes and in a managed database. I use Supabase and Google KMS so my auth keys are encrypted. Uses Pi agent under the hood. This enables me to code from my phone without a dedicated SSH terminal and without the need to babysit the agent. I describe the feature, off it goes, I close my phone and in 10 mins the results are there. Also using it to support my wife with white collar stuff like Excel analysis, translation, etc. It's a bit buggy but getting better.
I have a lawyer friend who’s complaining about versioning… but she also mentioned that Word is the de facto standard. What I’m trying to say is that this should be a Word addon.