528 karma · joined June 23, 2014
Interesting read though.
I've been working on a project involving some highly optimized C++ code, where the smallest architectural mistakes can cause serious slowdown. My architectural strategy thus far has been to 'just try' all of the decent options and then pick which one is the fastest. It's been working out well, but luckily my code is ~1K lines and the cost of doing this is minimal. (fun fact: template classes >> polymorphism in terms of speed, also, cache yo trig functions)
In contrast, I worked on a partial refactor of a fairly large (~150KLOC) code base, and the 'just try it' approach was definitely not an option due to the person-months work required to even make a small dent. That took quite a lot of thinking to figure out a reasonable path forward. And a lot of diagrams...
I'm definitely interested to see how this iteration plays out over the next few decades.
[1] http://www.ers.usda.gov/media/259572/eib3_1_.pdf [2] https://en.wikipedia.org/wiki/Technological_unemployment
[1] http://www.hhs.gov/hipaa/for-professionals/privacy/guidance/...