I agree with the part that says Agile (and Scrum in particular) is drinking the koolaid. Managers who don't themselves write any code, but micromanage their workers with their version of Scrum, are the worst.
I would not write it at all. Instead, I would write only the test cases, thereby documenting the requirements. I would then evolve the software using modern machine learning techniques which are capable of program synthesis: https://arxiv.org/abs/1802.02353 The underlying implementation can keep changing but the requirements and tests don't change so much.
This seems like a narrowly thought out proposal. Contrary to what Wikimedia may think and see today, Wikipedia is not the future. The future is something closer to robotopedia or machinepedia or autowikipedia, if you get what I'm saying. The name Wikimedia is fine.
I have seen the future, and there is no place for human writers in it.
As an American, I'm frankly sick of the US inaction on climate change. It makes me hate being an American. It almost makes me want to live somewhere saner from a climate pov. (Disclaimer: I'm a pacifist.)
Have you actually found cold-start delays to be an issue with serverless services, or are you just speculating? To my knowledge, the cloud provider keeps enough instances hot based on a forecasted demand. I have not found cold-start delays to be a real issue.
I recommend against using Zeit. I tried their offering this year and it was too much in beta. I honestly couldn't even get a basic service deployed because my defined dependencies wouldn't install. My web service deployed fine using the serverless offering of another cloud that I won't name, although it was not AWS. As a disclaimer, I have no conflict of interest.
I'd say managers and crappy team leads are the problem. They're often asking the developer to deliver code that is not quite ready or adequately tested. I admit though that the absence of senior engineers who perform an unforgiving code review is also a problem.
mypy is a joke of a tool. I have actually used it, and 80% of its messages are useless junk or just plain wrong. Granted, the other 20% can be on point. All things considered, it's better to be with a tool like it, than without.
Thanks, but using "WTF" in a title is unprofessional. If you wouldn't include it in the title of a research publication, you probably shouldn't include it in a TDS article either. After all this isn't your personal blog that you've published it on. I'm writing on behalf of the hundreds of users in my community who follow TDS articles; they expect decorum.
I have seen this in a prior article from you too where you used &%$*# in the title. The same logic applies. You say you "want to help", so please do. I am not a prude. I use swear words too, but only when no one else is listening.
Thanks, BTW, to the person who edited the title for us on HN.