For example, a recent article shared on HN highlighted that the cheap drones become useless once there is any signal jamming going on. Russia can't jam too aggressively as their own comms are not good enough to be useful in such an environment. But what about NATO? Would they just jam the EM spectrum to oblivion and render all these drones useless?
Not a great point of comparison, but Israel v Gaza seems to use next to no drones (certainly not the small cheap variety), and the little that is known of Israel v Iran also focused on big expensive manned and unmanned aircraft. Plus massive, enormous, eye-wateringly-expensive bombs. Not converted Mavic drones. To the extent that Iran used drones, reportedly they gave no tactical benefit, as they were all shot down long before they reached Israel.
There is also a need in adaptability. Delivering parts that meets a specific demand at a specific time is where 3D printing and diy drones shine and it's important in Ukraine frontline.
There is also a system in the way Ukraine is doing war that favorise diy drone. Basically, each units have a budget and you get more if your unit kill Russian soldiers/equipment. This in return give you access to more advanced drones.
I think today the drones are quite well equipped and the diy versions are less present.
So what's the point? Riding the neural network hype?
But the results and use cases seems to be legit to me. Agin, I'm not an expert on computer science and quantum physics.
and someone did it!
If it's not addreased correctly, llm won't be a progress for humanity.
But if you want to compare it "technically", maybe it's better to look at computer usage now vs with llm maybe (how many google request, sim failed, screen on etc.)
Which is stupid.
Nowadays, very good oscilloscopes with 200 MHz bandwidth, good user interfaces, and responsive displays are selling for $300 - I'm talking Siglent, Rigol, UNI-T. So the merits of DIYing something much worse just aren't quite there. It's that one piece of equipment you use to troubleshoot all your other designs, so you want it to be dependable, easy to use, and accurate.
This is not to say it's not a fun, geeky project to work on and publish... but you know, only once you have a real oscilloscope. If you're just setting up, do yourself a favor and spend a bit more money on this. The remaining equipment is not nearly as critical.
I think it does have its place even today.
In many domains, the scope and complexity of software systems goes beyond the ability of a single software engineer to manage. A coordination layer becomes necessary when the number of engineers required goes beyond a threshold (say 5 or so). When the development effort must be coordinated over extended periods (say several months or years), mechanisms to raise capital and manage risk become necessary. These functions are why companies exist.
Consider that a massive increase in software engineer productivity will make coordination unnecessary for many kinds of software. In the market that opens up, companies with expensive executives, middle management and coordination inefficiencies will not be competitive. Smaller shops with a solo engineer or a team of less than 5 will outcompete larger players because their costs will be significantly lower. Massive one-size-fits-all products will be harder to justify when a small dev shop can quickly build or customise software for the unique requirements of a business or niche.
Before the CEOs stop needing engineers, engineers will stop needing CEOs and managers to coordinate their efforts and raise capital.
But with the externalization of intelectual work (which happen without IA, for ex. India tech) I wonder if such solution is possible.