Prediction: What Will Happen to The Commercial Drone Revolution? https://propertarianism.com/2020/06/01/prediction-what-will-happen-to-the-commercial-drone-revolution/
Source date (UTC): 2020-06-01 13:27:35 UTC
Original post: https://twitter.com/i/web/status/1267447704738824193
They are extremely vulnerable, and the culmination of “Cargo Cult” opportunism. It will take a while for their density to be such that it’s worth making a living off investment with capturing their cargo, but you know, I sure as heck know how to make a living at it, and a gang that gets organized enough will make a great living at it. I mean, you know that video from south africa where the locals cut up a beached whale while it’s still living, and run off with hunks of meat? A distribution channel of drones carrying ‘Cargo’ is simply a an opportunity for many generations of the division of labor more evolved than whale meat. Drones fly at 120 meters (130 yards) according to FAA regulations. Now if you’ve shot skeet, you can shoot down a done with 3 1/2” 12 gauge OOO Buckshot, with a drop of 18″. If you lead, and fire three shots in sequence assuming 18″ drop it’s shooting fish in a barrel. (and yes the gang bangers will develop ‘talent’ that will do it, and vehicles to do it from, and spend all f’king day doing it. You can use a rifled shotgun and slug pretty easily at 130 yards. Even with a .22 semi auto – because it’s so quiet and can put a lot of rounds up there. Or with another drone you can just tie nails to a bit of fishing net and drop it on the drone, or just smack into it with your landing gear. Now that’s before we get to the fact that they are even more vulnerable during delivery of the goods. And that even if their reasonably autonomous they aren’t endlessly autonomous. And that capturing, modifying, and using them for ‘other purposes’ is profitable in and of itself. So now, you get your own and deliver drugs anonymously and don’t need runners. I mean, the disintermediation from the human being is awesome. And you know, load it up with explosives and now people won’t interfere with it. I mean.. it’s a whole new criminal industry just waiting to happen! 😉 Sorry. Just had to rain on the parade. Edit
They are extremely vulnerable, and the culmination of “Cargo Cult” opportunism. It will take a while for their density to be such that it’s worth making a living off investment with capturing their cargo, but you know, I sure as heck know how to make a living at it, and a gang that gets organized enough will make a great living at it. I mean, you know that video from south africa where the locals cut up a beached whale while it’s still living, and run off with hunks of meat? A distribution channel of drones carrying ‘Cargo’ is simply a an opportunity for many generations of the division of labor more evolved than whale meat. Drones fly at 120 meters (130 yards) according to FAA regulations. Now if you’ve shot skeet, you can shoot down a done with 3 1/2” 12 gauge OOO Buckshot, with a drop of 18″. If you lead, and fire three shots in sequence assuming 18″ drop it’s shooting fish in a barrel. (and yes the gang bangers will develop ‘talent’ that will do it, and vehicles to do it from, and spend all f’king day doing it. You can use a rifled shotgun and slug pretty easily at 130 yards. Even with a .22 semi auto – because it’s so quiet and can put a lot of rounds up there. Or with another drone you can just tie nails to a bit of fishing net and drop it on the drone, or just smack into it with your landing gear. Now that’s before we get to the fact that they are even more vulnerable during delivery of the goods. And that even if their reasonably autonomous they aren’t endlessly autonomous. And that capturing, modifying, and using them for ‘other purposes’ is profitable in and of itself. So now, you get your own and deliver drugs anonymously and don’t need runners. I mean, the disintermediation from the human being is awesome. And you know, load it up with explosives and now people won’t interfere with it. I mean.. it’s a whole new criminal industry just waiting to happen! 😉 Sorry. Just had to rain on the parade. Edit
Q: Biggest Programming Mistakes? https://t.co/3vPtRzb9sp
Q: Biggest Programming Mistakes? https://propertarianism.com/2020/06/01/q-biggest-programming-mistakes/
Source date (UTC): 2020-06-01 11:48:36 UTC
Original post: https://twitter.com/i/web/status/1267422795211956225
Q: Biggest programming mistakes? (from elsewhere) All my big mistakes are the same, and I remember them. I keep working when I’m too tired to keep working: So, I wrote more functionality than I needed to; I forget that I wrote something and wrote it again; I forget that I wrote it over there and wrote it here. I forgot that I did it that way and so did it this way, and now I have to fix one or the other. I made only one architectural mistake with a new product because I rushed with it. The rest are all the same. Tired = stupid. I keep lots of notes, I plan my work, I use diagrams to design it. I usually do databases for rules, then services, then ui designs; Then the class architecture. I pseudocode the work, I write code for readability first; I document as I go; I (mostly) write test then code, the reason I’m slower I think I should be is that I test more than I should, especially UI functionality, and so I revise too much. I refactor a lot. and sometimes I shouldn’t. I should focus on functionality coverage so that I have a better understanding of how different services interact in practice. Most recent mistakes that sit with me is the message bag in Oversing, where I’d replaced one technique with another and then forgot I’d done so until … oops. The other is writing one set of panels one week using one method of data propagation, and coming back the next week and writing another set of panels with a slightly different method of data propagation, when I should have used a different method of data propagation. My general strategy is to make it work, make it work together, make it durable, then make it elegant. I stopped writing code myself because there are people who are faster and better and my core strength is user interface design, business rules, and data structures, and not wiring everything together. And the reason is that with all the visual cues I do better than I do in code editors without them. ie: as I usually complain my weakness is short term memory. I remember almost everything. but that’s not the same as working memory. But in general, tired = stupid. Don’t write code tired. Don’t send emails tired (or angry)
Q: Biggest programming mistakes? (from elsewhere) All my big mistakes are the same, and I remember them. I keep working when I’m too tired to keep working: So, I wrote more functionality than I needed to; I forget that I wrote something and wrote it again; I forget that I wrote it over there and wrote it here. I forgot that I did it that way and so did it this way, and now I have to fix one or the other. I made only one architectural mistake with a new product because I rushed with it. The rest are all the same. Tired = stupid. I keep lots of notes, I plan my work, I use diagrams to design it. I usually do databases for rules, then services, then ui designs; Then the class architecture. I pseudocode the work, I write code for readability first; I document as I go; I (mostly) write test then code, the reason I’m slower I think I should be is that I test more than I should, especially UI functionality, and so I revise too much. I refactor a lot. and sometimes I shouldn’t. I should focus on functionality coverage so that I have a better understanding of how different services interact in practice. Most recent mistakes that sit with me is the message bag in Oversing, where I’d replaced one technique with another and then forgot I’d done so until … oops. The other is writing one set of panels one week using one method of data propagation, and coming back the next week and writing another set of panels with a slightly different method of data propagation, when I should have used a different method of data propagation. My general strategy is to make it work, make it work together, make it durable, then make it elegant. I stopped writing code myself because there are people who are faster and better and my core strength is user interface design, business rules, and data structures, and not wiring everything together. And the reason is that with all the visual cues I do better than I do in code editors without them. ie: as I usually complain my weakness is short term memory. I remember almost everything. but that’s not the same as working memory. But in general, tired = stupid. Don’t write code tired. Don’t send emails tired (or angry)
The Other Reason for Academic Reform: Use Tech to Scale the Best, and Exit the Rest. https://t.co/uG9oXY9M5D
The Other Reason for Academic Reform: Use Tech to Scale the Best, and Exit the Rest. https://propertarianism.com/2020/06/01/the-other-reason-for-academic-reform-use-tech-to-scale-the-best-and-exit-the-rest/
Source date (UTC): 2020-06-01 00:35:28 UTC
Original post: https://twitter.com/i/web/status/1267253394126909441
—“Most professors outside of the very top tier don’t break the 120 -130 range (not bright enough to move the dial). I was fortunate to have an outstanding Harvard educated law school professor, however, who was both intelligent (plus 3.83-4 standard deviations) and erudite. His course on contemporary legal theory alerted me to the enemy’s 20th c. techniques (Gramscian long march, Fabian infiltration, Frankfort cultural critique, feminism, post-modernism, and unrestrained legal positivism). Thank you Professor Durham.”—Scott De Warren