844 karma · joined January 8, 2011
Many of the components and practices in our software are quite specific to our business and environment. They'd just be useless or, worse, an impediment to other people wanting to reuse the software in a different context.
Even if we were to refactor parts of our code base to produce some "clean" components that didn't rely on the specifics of our business or other processes, there are many cases where that would just add to the overhead of maintaining the software for us.
Most sites in the early stages will have few visitors and due to variety of interests it's unlikely that a single person will be using a large enough number of these sites to start realizing this problem.
As the successful sites grow larger and move beyond the early stages it's likely the developers will have access to more resources to improve their site theme over time and move away from the bootstrap look.
I finally settled on using the Sennheiser PX-200 II headphones: http://www.amazon.com/Sennheiser-PX-200-II-Headphones/dp/B00...
They have good sound isolation, are extremely light, and very comfortable to wear for long periods. The volume dial on the cord is a nice added bonus as well.
It's basically impossible to find even the easiest of IDE functions in that mess. One of the purported advantages of GUIs is the discoverability of the interface. When I have to visually search through hundreds of UI elements to find what I need, that is all lost.
The monolithic IDE concept really needs a fresh breath of air. I do like the fact that they come with a lot of integrated tools for a programming environment, but they shouldn't clutter the UI because of it. Ideally I think an IDE would start off looking mostly like a text editor and give you clearly delineated views of different activities once you need them.
It's also been my experience that non-expert users don't understand the repository DAG model well enough to perform history rewriting reliably and without error, which I think is one reason these features are disabled by default.
Finally, as of Mercurial 2.1 they now have the concept of "phases" of commits which make local non-shared commits mutable whereas commits which have already been shared are immutable. This new feature is a first step to safer history editing operations becoming more mainstream mercurial commands.
Recently it seems it's been coming to light that their curation process is not nearly as thorough as they would have us believe.
Of course that's only going to help address the first stage of the pipeline, eventually you still need to do a bunch of research in to manufacturability of the drugs, clinical trials, etc. Those all take time. Maybe they could be sped up as well but I can't say that's an aspect of it I know much about :)
Now imagine you took the engineering team of GitHub (or one like it) and transplanted them to work on Widget Inc.'s CRM system that's primarily used by their sales, marketing and HR people. Instead of your end users being similarly savvy and motivated developers they're now your typical corporate office staff. They're not using your product by choice but only because it's what the corporate higher-ups handed to them. They couldn't care less about new whiz-bang features you add to the product, they're mostly concerned about getting their TPS report out on time. Interface changes only confuse them and slow them down. They're never going to tweet or post a blog post about how awesome the new thing you just rolled out is.
Do you think the engineers would be similarly motivated to work on such a product? I doubt it.
From the non-software perspective human brains make big mistakes all the time. Consider car accidents, gross errors in judgement, etc.