> Manufacturers may not have the money to do the research themselves, but are highly incentivized to incorporate the improvements if somebody else figures it out for them.
Which incentive is this exactly then if the cost is bore by society? "Polluter pays" creates both that exact incentive and the required funds for public research.
I told some of my coworkers that they should keep in mind that if their job becomes "passing messages between an AI Assistant and their co-workers", sooner or later someone will realize they can just cut the middle man and build an agent that does their job. Use AI assistants all you like but don't forget to add value.
> This is what government is for. Tax everybody to provide benefits to everybody. This is infrastructure spending, just like roads.
This is not roads, this is waste management. I pay proportional to the amount of waste my household produces to have it disposed correctly, the more waste I produce, the more I pay. That is what government is for, steering behavior through taxation, instead of letting the most morally depraved enrich themselves on the rest of society.
Right, privatize the profits, socialize the costs. The fast fashion industry makes billions in profit every year, what do you mean exactly by "Manufacturers may not have the money to do the research"?
Dont't be evil, etc... we've seen it all before. Eventually ads will be hidden in the answers, it's just a matter of time, enshittification ensues eventually.
was quite impressed after building my label maker application [1] and stylex playground [2]. Had some real world needs and both were built in bolt with 99% of edits made through prompts. My tips would mostly center around:
- don't try to fix mistakes, revert and try with an updated prompt. the context seems to get polluted otherwise.
- don't treat it as a black box, inspect the generated code and prompt to write specific abstractions. don't just tell it what to build, but also how. this is where experienced programmers will get way more mileage.
I wish they took the use-case of resizable panels into account. Even if the implementation is fully user-land, a styleable separator that can also receive events would be so useful.
my dad keeps his calendar in an excel file with almost the exact same format except he omits dates with no entries. Every week he prints a new version of this on a single A4 which he folds and keeps in his wallet. new events are hand written at the bottom and get included in the excel weekly. he's been doing this for as long as I can remember.
They are mostly advertisement platforms coupled to recommendation engines. The "communication platform" is just side business at this point. And it's being used to wave around as "free speech" when anyone dares to question the detrimental effect of the big mass mind control machine it actually is.
It's not illogical, but it's not adapted to half the applications it's being used on. That's what's illogical about it. "Document flow", "writing mode", the language used in this post indicates what CSS is meant for, formatting documents on screens. Yet half of us try to beat it into submission building highly interactive applications.
I was pretty early in my carreer at the time, working as an engineer, integrating PCS7 in food processing plants across western Europe. Our client had a few stuxnet infections at some point. they immediately put a no usb device policy into place.