painful

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.

Agreed 100%

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.)

Is there a single programming language for which static analyzers are a part of the language rather than external tools?

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.

Granted it's an opinion, but if you've been through as much scrum as I have, especially if you're a senior developer, you'd know it's a true article.

It's an extremely serious article. If you think it's good for a laugh, the joke's on you.

Hopefully you won't subject your workers to scrum; it is evil. Refer to https://michaelochurch.wordpress.com/2015/06/06/why-agile-an...

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.

"See no evil"!

How about people stop using unsafe languages such as C and C++?

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.

Good find. Also see https://arxiv.org/abs/1802.05968

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.

Please be careful to not take on too much. It's not the job of this service to compile and test code.

GitXiv has been very unprofessionally maintained. Their RSS feed often has junk posts like by a child. They were once good, but that time is long gone. I still subscribe to its feed, but there isn't much to find in it.

##machinelearning on Freenode IRC: https://freenode-machinelearning.github.io/

An experimental RSS feed for it is now available. Please find the link to it at the new project repo: https://github.com/ml-feeds/arxiv-ml-reviews

An experimental RSS feed for it is now available: https://us-east1-ml-feeds.cloudfunctions.net/arxiv-ml-review...

It's configured to be updated once a day.

The feed is in the works, but its content body will only contain the abstract, not the full paper.

It's currently ordered by date, with most recent on top. It's not unordered.

Just how is the subject provided by arXiv? By subject, do you mean the categorization such as stat.ML, cs.AI, etc.?

Categorization would definitely be good to have, but it requires the use of good quality ML to discern them accurately :) Meanwhile, please use Ctrl+F.

A higher priority is to serve a RSS feed for the results.

I recommend asking the manager to put you on a different project where your code and theirs is completely separate. Moreover, don't even worry about code reviews of their code. This advice is terrible for the company, but it's nearly optimal for you.