[...] I install the toolkit. Immediately, I'm not impressed. The documentation is a mess. It's outdated, and most of the API is just blank. StackOverflow is filled with questions about programs randomly crashing, and smug answers belittling the poster. I'll have to poke around blindly looking for something that works. You laugh, but this is the true state of affairs for the software that runs your phones, cars, medical devices, and military hardware. Do we really expect that we'd approach human programming more rigorously? We can't stop the development of technology just because we haven't figured out programming yet. We also can't use the argument, "but these are people!" That holds little weight to the decisions made by giants like Facebook and Google -- who essentially already control our lives through the software they write. Alright, I have some code. I can't just deploy this. I need to test it. I wonder how this will even work. Do we have some emulator? Maybe, but it looks buggy. I see there's an offer from India to outsource my testing. They've got a web form and ability to upload the code. I'm best off not thinking about what happens on the backend. As long as I get my results, it's their concern, not mine. [...] This demands the question: what level of completeness is okay? It's currently impossible to set a deadline and a planned feature set in software. This isn't a lack of planning ability, it's a fundamental uncertainty in how the profession works. There's no reason to assume human programming will be any different. What defects are we willing to accept when it comes to gene editing? [...] If I think about the self-driving car discussions, we have a fundamental lack of knowledge to deal with morality and software. And the repercussions will be played out at a high political level, it might never even involve the programmer -- despite them being essential to the answer. https://dev.to/mortoray/would-you-program-a-human-57gb