Would you want to hear the crazy stories of a two decades ago child murderer too?
I didn't think so.
254 karma · joined April 16, 2018
Would you want to hear the crazy stories of a two decades ago child murderer too?
I didn't think so.
I typed in plenty of games from computer mags in the 80s and they almost never worked first time. The problems were sometimes my errors (have you ever tried retyping 100s of lines of small-primt code?) and sometimes present in the published listings.
Whichever, the errors meant that reasonable debugging skills were necessary to get any of them working. It was good training.
I don't use PayPal any more. Their support staff are impossibility hopeless so any kind of problem with your account will cause you a world of pain.
For example, all the localisation files could live in a separate project (if we accept the need to commit them at all). Some tools would be needed to deal with the inevitable problem that developer working sets would not align with project boundaries, but that seems like an easier job than making git scale while maintaining response times.
The only possible justification for duplicating code would be that creating an appropriate abstraction is harder. Given that there are generally economies of testing when you factor out common code, that's usually just not true.
"Duplication is evil" is a more reliable mantra.
Diving rebreathers are an interesting implementation of these rules in that they are lethal if you get it wrong.
300MW is a lot of energy to passively release into the environment. Does this design really fail safe? And if so, how?
The Fukushima issues were caused (IIRC) by failure of the backup generators to run the cooling system after the reactors were shut down. Do these small reactors really not need any external power when in that state? And do they get into this state by default? I.e. do they shut themselves down without external power and if the control systems fail? That would seem to be a massive safety advantage if it's true.
I remember reading about UK magnox reactors where the graphite control rods were held above the core by electrically powered actuators and which were designed to fall into the core (and stop the reaction) if there was a power failure. Perhaps these reactors are similar.
The article doesn't explain why horizontal scalability wasn't pursued instead of their approach of performance efficiency (i.e. greater performance from a given amount of resource). It's certainly true that at the time that SO was starting, scaling horizontally required far more handbuilt tooling than it does today but it certainly was already a widely used pattern. The likely reason is cost, but that then comes back to the first question - would SO have been equally successful if it had higher infrastructure costs in its early days?
The persuit of efficient performance at the cost of aspects of quality (of which testability is only one) can only be justified if efficient performance is truly necessary for success. A much smarter person than me warned against premature optimisation. That seems relevant here.
This assumption was challenged at the time by various groups - I was closest to the Equities Operations software team (although not part of it) who absolutely dug in their heels and refused to use Quartz. The assumption was explosively invalidated when people started implementing in Quartz applications that fell under Sarbanes/Oxley regulations and Quartz picked up a severity 1 audit finding - because Quartz was explicitly designed for "Hyper Agility" (literal quote from the quartz docs) - and anyone-can-change-anything-at-any-time does not make for applications that the regulators trust.
There was an interesting trajectory of Python hiring during my time at BAML. I joined just as Quartz was getting started and we managed to easily hire tens of python devs in London because it was easy to sell the fact that BAML was making a strategic investment in Python and therefore their (at the time relatively uncommon) skills would be highly valued. But as Quartz matured, Python developers generally came to dislike it (for reasons see original article) and it became hard to retain the best ones. And after a while Python 2.x became a massive embarrassment and, as Python became a more common skill in the marketplace, it became harder to hire good developers into BAML.
There are lots of things wrong with technology in large banks but the business knowledge of developers is pretty low on the list.
I left banking a few months ago, so I am no apologist for the sector.
I guess that you've never been on a bike on a very hot day. It's much, much more pleasant to be ventilated by your self-created airflow on a bike than it is to to have sweat pouring down your back as you walk around.
I'd like to say that I'm astonished that modern aircraft still use the 1553 bus, but nothing surprises me when it comes to the use of stone-age tech in military hardware. For example, the other Harrier I worked on in the early 90s (GR-7 - same as US AV8B) still used core memory.
Volvo introduced Aeb in 2007 on the XC60. The XC90 only got it when they introduced the new generation a few years ago. Therefore claiming that the exceptional safety record of the XC90 is in any way related to AEB is just rubbish.
The reason why XC90s are associated with so few passenger injuries (note, no claims are made for injuries to other road users by XC90s) is that they are large, heavy and chosen by safsr-than-average demographics.