Maybe I am being contrarian, or maybe I don't understand; if I am reading input, I am always going to validate that input after parsing. Especially if it is from a user.
I understand that they should be separate, but they should be very close together.
I didn't think there would be a gain of speed or productivity, but just a (possibly ominous) idea of 'cutting out the middleman'. Granted, that middleman is very important.
Natural language is not the best language for formal descriptions of projects, but it is the one that humans use most day to day. Perhaps a chain like this would be the start of on demand programs.
You are right that this is an error prone process, but as these tools are used now, are much like how compilers were used in the past. It is, after all, another layer of abstraction.
Is it foolproof? No. I do think the idea had some merit, though.
This may offend some, but I think the large amount of women joining the labor force may be a factor. American society, pre-WWII, usually had only one member of the household at work. More often than not it was the man who went to work, and the women stayed home to take care of the children. American society, pre-1930s (the Great Depression saw the rise of the female workers) was build on a one-income household.
And yes, there is a big income disparity in the US. However, the fact that labor has practically doubled is another thing.
This is the most milquetoast take I have ever seen.
From what I read of the article, a 'Bad Person' is just someone you have bad vibes with. Quote:
> They tend to be charming, capable, but since the beginning your intuition tells you that something’s not right.
So if someone tells you, "No, that is physically not possible, you will lose money, here is my evidence" and you just have some bad vibe about them, ignore them! They're just a bad person. In fact, remove them!
What a joke. The idiom "If you lie down with dogs you get fleas" comes to mind. Usually this rhetoric comes from people who have been on their high horse for too long, and call many other kettles black.
I think that a lot of web developers and users have gotten too comfortable with large amounts of memory usage. On one hand of the spectrum, web browsers are essentially remaking the idea of the operating system, but on the other hand, is the "HTML is good enough" crowd. Quite frankly, there SHOULD be a balance between these factions; and personally, I lean towards the "HTML is good enough" crowd. I've never been a fan of web apps, and I think systems programming is not beloved enough. A web page should be just that; a web page, like paper. Anything fancier shouldn't be stuck in the browser, IMHO.
I guess it would have to provide audio in order to be accessible, and if blind and deaf... well, do most people prepare applications for the blind and deaf?