Probably more nonprofits could be started that just cost extra money to recycle stuff (like, you might not be able to make it into a business where the recycled stuff pays for itself, but people might be willing to pay to prevent e-waste from being created)
Managers don’t even need to push anything. FOMO does all the work.
Overheard a couple of conversations in the office how one IC spent all weekend setting up OpenClaw, another was vibe coding some bullshit application.
I see hundreds of crazy people in our company Slack just posting/reposting twitter hype threads and coming up with ridiculous ideas how to “optimize” workflow with AI.
Once this becomes the baseline, you’ll be seen as the slow one, because you’re not doing 5x work for the same pay.
You do it to yourself, you do, and that's why it really hurts.
> Importantly, the company did not mandate AI use (though it did offer enterprise subscriptions to commercially available AI tools). On their own initiative workers did more because AI made “doing more” feel possible, accessible, and in many cases intrinsically rewarding.
was trying to figure out how I could run this basically on a computer that's offline / local
maybe I could feed the link to an AI that could walk me through an easy way to set up element (to chat?) and ollama (for the LLM?) and then whatever else you need with the various SOUL.md, HEARTBEAT.md, MEMORY.md files...
The problem is education, and maybe ironically AI can assist in improving that
I've read a lot about programming and it all feels pretty disorganized; the post about programmers being ignorant about how compilers work doesn't sound surprising (go to a bunch of educational programming resources and see if they cover any of that)
It sounds like we need more comprehensive and detailed lists
For example, with objections to "vibe coding", couldn't we just make a list of people's concerns and then work at improving AI's outputs which would reflect the concerns people raise? (Things like security, designs to minimize tech debt, outputting for rradability if someone does need to manually review the code in the future, etc.?)
Incidentally this also reminds me of political or religious stances against technology, like the Amish take for example, as the kind of ignorance of and dependence on processes out of our control discussed seem to be inherent qualities of technological systems as they grow and become more complex.
KSPS was my favourite surfing game growing up. What I dislike about it though is the infinite/perfect waves (always a truck-sized barrel opened, you can do tricks anywhere, almost no differentiation between waves) and the focus on impossible airs and tricks.
In my game the waves start, break and end, with different sessions and hollowness, so there's more wave reading involved. Also the focus is on being able to stay on the wave and generate speed, doing cutbacks, snaps, off the lips, etc.
After reading a bunch of blog posts like this, I'm now kind of glad to see "good code" go away and am also glad to pour more gasoline on the flames of fire burning away at such code, so to speak
I think "good code" t was a "nice" pursuit but became too much of an end in itself while code was always - for me - just a means to create something that "just werks"
But I'm not sure the "good code" fans need to worry because they might be able to obsess over "proper prompting" and the "correct way to use agents" or "appopriate ai tooling" or something like that on this next wave of "code creation"
I think the sweet spot is ai-assisted chat with manual review: readily available, not as costly
agents jump ahead to the point of the user and project being out of control and more expensive
I think a lot of us still hesitate to make that jump; or at least I am not sure of a cost-effective agent approach (I guess I could manually review their output, but I could see it going off track quickly)
I guess I'd like to see more of an exact breakdown of what prompts and tools and AI are used to get ideas on if I'd use that for myself more
Suspect the sweet spot also depends on the objective. If it’s a personal tool where you are the primary user then vibe coding all the way. You can describe requirements precisely and if it breaks there are no angry customers.
reply