My employer bought me a Claude Max subscription. On heavy weeks I use 80% of the subscription. And among software engineers that I know, I'm a relatively heavy user.
Why? Because in my experience, the bottleneck is in shareholders approving new features, not my ability to dish out code.
"Age-restriction laws push platforms toward intrusive verification systems that often directly conflict with modern data-privacy law" - when you make rules contradictory, someone always violate these laws, and you can use selective persecution to "convince" companies to favor you, the incumbent politician. You don't even have to use such power, just a "joke" may be enough to send have any rational CEO licking your shoes.
European proponents of "anti-big-tech action" make it pretty explicit - broad discretionary power should be given to executive branch, because otherwise "international corporations" will use "loopholes" (and these "loopholes" are, in practice, explicitly written laws used as intended).
Asynchronous (you don't know when and where you will get Internet/local network connectivity) mesh (there is no gov infrastructure to be trusted) networking in presence of malicious (gov operated) and unreliable (destroyed by gov) nodes is probably among hardest problems known to computer science.
Mining in Arctic is a technical nightmare. Typical alloys become brittle in these temperatures, darkness severely limits operations and/or workplace accidents, transport requires ice-breakers, permafrost is fundamentally unstable (heat from buildings melts it, causing sinking), and you need to pay people a lot to work there.
Because almost everyone involved in AI race grew up in "winner takes it all" environments, typical for software, and they try really hard to make it reality. This means your model should do everything to just take 90% of market share, or at least 90% of specific niche.
The problem is, they can't find the moat, despite searching very hard, whatever you bake into your AI, your competitors will be able to replicate in few months. This is why OpenAI is striking deal with Disney, because copyright provides such moat.
Oh, you mean specifically GPL v3 license, not any GPL license.
Yeah, broad tivoisation and patent clauses make it a problem, because making any patent litigation on unrelated grounds has potential to lose ability to ship the entire OS.
The hardest part of building nukes is acquiring weapon-grade enriched uranium, because it's controlled as hell and you will get bombed if you try to make your own.
If you spend hundreds of millions of dollars on enriched uranium, paying salaries for team of engineers is the easy part.
Conflict of interests is a real thing to worry about. I wouldn't trust scientist working in tobacco company on cigarette harm, even if I have no evidence of wrongdoing.
Asymmetric cryptography isn't a rocket science. Airline keeps encrypted recording and public key, certain government institution keeps private key, you need both to decrypt.
Title "People cough more during classical concerts" implies that people are more likely to cough during classical concerts than non-classical concerts. Article implies that people cough more in classical concerts than at home.
There are numerous biological, physical and neurological factors that can affect cough rate, and implication "it's voluntary" seems to be rather ridi... far-fetched.
I was already running home server, so for me, setting up smart home was relatively simple:
- Buy Zigbee USB dongle
- Install Home Assistant and Zigbee2MQTT in Docker on server
- Initial configuration
It requires basic technical knowledge, but after initial configuration it just works.
There were three major pains:
- Configuring camera (ONVIF is pure pain) - it works initially, but I physically plug-in cameras only when I'm going on holiday
- Configuring voice assistant
- Finding good ZigBee remotes
- Price of Hue Wall Switch (DIY approach is possible by gutting cheap button)
Cameras and voice assistant troubles were arguably result of my "keep as much as possible within local network" approach.
Minor pains:
- Binding remotes to light bulbs, so they work even if server is down
- Finding instructions how to bind certain ZigBee accessories (they have "just open our proprietary app and it will explain what to do" manual)
History as social science was basically invented between 19th and 20th century. Ancient writers generally had agenda and they happily filled missing pieces with ideologically-fueled speculation.
Why? Because in my experience, the bottleneck is in shareholders approving new features, not my ability to dish out code.