- btbuildemIt's terrifying because it's true for a majority of developers.
- glock > flock
Is mass vandalism the final answer to this problem?
- Tinkercad is a very low-barrier-to-entry option here
- Exactly -- vibe coded PoC becomes a living spec for prod
- Right -- and that's likely because search was completely broken, people always complained about it, and nothing was ever done to improve it.
- That's chasing the effect, not the cause. Forget taxing AI. Liquidate billionaires instead -- redistribute anything over $1B. Death penalty for any fancy avoidance schemes (applicable to the individual and everyone standing to inherit the wealth, including any kind of corporate structure).
This unbridled greed has metastasized into a global existential threat, and needs to be aggressively eradicated.
- I think UIs will become more "generative" or "on demand". Not necessarily always generated anew, but assembled from pre-generated (reproducible) components, to suit a specific workflow.
I think especially in context of software that is complex and takes a long time to master, this could be the next breakthrough. Instead of paths-to-goal being buried in sequences of menus and config panels, workflow pathways would be invocable with plain language.
- I really like the simplicity here (maybe because it mirrors my own approach). No build chain, no node_packages, no frameworks.
I wonder if packaging the results as web components would be the next logical step.
- Local archive + client for search
- I've spent a weekend making something similar for my gmail account (which google keeps nagging me about being 90% full). It's fascinating to be able to classify 65k+ of emails (surprise: more than half are garbage), as well as summarize and trace the nature of communication between specific senders/recipients. It took about 50 hours on a dual RTX 3090 running Qwen 3.
My original goal was to prune the account deleting all the useless things and keeping just the unique, personal, valuable communications -- but the other day, an insight has me convinced that the safer / smarter thing to do in the current landscape is the opposite: remove any personal, valuable, memorable items, and leave google (and whomever else is scraping these repositories) with useless flotsam of newsletters, updates, subscription receipts, etc.
- > Palantir ended up having to rent a second-floor building that housed its Tel Aviv office, to accommodate the intelligence analysts who needed tutorials
Has anyone here tried using their software? It's salesforce-level fucked. They did a great job spewing lofty concepts, with their ontologies and their kinetic layers, but in the end it all ends up being a giant wormy ERP. There might be one good idea in there (articulating the schemas and transformations in separate layers) but overall it's a perfect vibe match for orwellian bureaucracies.
- > the bigger bottleneck to productivity is that very few people can correctly articulate requirements.
One could argue that "vibe coding" forces you (eventually) to think in terms of requirements. There's a range of approaches, from "nitpick over every line written by AI" to "yolo this entire thing", but one thing they have in common is they all accelerate failure if the specs are not there. You very quickly find out you don't know where you're going.
I see this in my work as well, the biggest bottleneck is squeezing coherent, well-defined requirements out of PMs. It's easy to get a vision board, endless stacks of slides about priorities and direction, even great big nests of AWS / Azure thingnames masquerading as architecture diagrams. But actual "this is the functionality we want to implement and here are the key characteristics of it" detail? Absolutely scarce.
- > lack of real integration is basically the core design of most Copilot products
I would wager a month's wages that this is the doing of some internal Security Review, wherein a bunch of out-of-touchers decided that the customers will want to prefer to be Safe and Secure instead of getting some actual value from integrating copilot into shell workflows.
Meanwhile people are yolo'ing it with various janky DIY wires and duct-tape githobbits that mash together whatever open weights model and user-level access to the system (or worse).
- > FirstPageSage AI Chatbot Usage Chart (December 3, 2025)
What a bizarre way to organize the chart. Clearly Anthropic is leading -- their early bet on "programming" as the main use case is paying off.
The recent report from Openrouter [1] confirms as much: coding is the number one use case, with role playing / fantasy writing in second place.
I have a feeling the remaining use cases will never dominate, instead they will slowly mature into acceptable practices across the various industries. That will probably take longer than the investment bubble can hold though.
- This is so neat. I quite like this one: https://turtletoy.net/turtle/782a9f5329
- > The way Bryan approaches an LLM is super different to how a 2025 junior engineer does so
This is a key difference. I've been writing software professionally for over two decades. It took me quite a long time to overcome certain invisible (to me) hesitations and objections to using LLMs in sdev workflows. At some point the realization came to me that this is simply the new way of doing things, and from this point onward, these tools will be deeply embedded in and synonymous with programming work. Recognizing this phenomenon for what it is somehow made me feel young again -- perhaps that's just the crust breaking around a calcified grump, but I do appreciate being able to tap into that all the same.
- It turns out DeepSeek only made BUY trades (not a single SELL in the history in their live example) -- so basically, buy & hold strategy wins, again.
- It was (is?) free with eg. opencode -- so, open-source coding agent + free sota model, it's hard to resist. That said, grok fast is fast, but not that great when compared to the other top tier models.
- Before I watched the video, my brain ran ahead and I imagined it would be one of those led "fans", except also rotating around it's base. It might be harder to sync the two rotations, but you'd have much less mass in motion that way.
The solid state ones are cool! The real mystery there is how the pixel volume was manufactured -- it doesn't seem like something easily DIY'd