Would be nice if the dates in the selection range were highlighted, and unselectable dates (eg. later than the end date in left calendar, earlier than start date in right calendar.) were grayed out.
I agree with most of this issues, but it sounds like his editor doesn't have auto import and jump to definition like Eclipse.
eg complaint about nested packages. (not that I agree that this is a necessary class):
instead of MuffinMail.MuffinHash.MuffinHash, type MuffinHash and have your editor add:
from MuffinMail.MuffinHash import MuffinHash.
Sure, but as the guy talks about in the article, he is hands on. He just spends a certain fraction of his time trying to maintain a global picture of the project and applying insights that come from that.
I haven't worked on a project with more than 4 people for ages, but I don't think I would mind this.
Perhaps my biggest advantage is that, while I do spend some time coding, when I think about our software I am not constrained by the fear that I will have to implement my own ideas. It may seem crass, but as someone who has worked long years in the trenches I know that there is a subconscious tendency to discount ideas that may have huge long-term benefits if it means a lot of work in the short term.
Hate to admit it, but it's true. It's something you fight against.
It's not supposed to be something you learn from, but something you reference.
Really? That's the exact opposite of how I think of it. An encyclopedia is something you learn an initial shallow understanding from. A field specific reference text is something you reference. eg. My linear algebra text book.
For sure re usefulness, which is why moultano's work is greatly appreciated.
Way too often I find a math article jumps straight into the equations without a good overview that can be understood by someone without a math background. Example applications, for example, would greatly reduce the abstract nature of these pages.
Personally I am pretty damn sure that WSGI no longer carries the importance it had a few years ago. I think it no longer makes sense to merge different applications on the WSGI level together, it should be done on a higher level and JavaScript is a nice way to do that.
Just think about Google's gray bar. You can totally throw such a bar on top of different independent parts of the application by emitting a tiny piece of JavaScript that generates that bar and handles your user session.
I started thinking about it and was like "Right, you can make multiple async requests to hit multiple apps!"
Rather than building these data analysis/visualization programs from scratch each time, my thought is that scientists should instead be writing them as modules for a data workflow application like RapidMiner.
If you haven't heard of RapidMiner, you basically edit a flowchart where each step takes inputs and outputs, eg take some data and make a histogram, or perform a clustering analysis.
This is why I think, rather than every data analysis/visualization program being written from scratch with it's own custom UI and I/O, formatting etc, these programs should be written as modules to a data workflow program like RapidMiner that handles all that for you.