You have just as much control over the (inheritance of) brains as boobs.

Soros was a *child* at the time, and is being held to an adult standard in this particular example.

This is exactly my experience. I moved from Sydney to Vienna to do a MA and a MSc. It's cheaper, with a much higher standard of living than doing the same back home.

Also, sometimes the things you want to study, are somewhere that you have to be.

There are many Americans doing the same all across Europe and enjoying a cultural experience.

Will remain in beta until discontinued.

a) Get something done on time cutting corners and ultimately fucking it up
b) Spending a little extra time and getting it right

To quote another rocketeer: "It's done, when it's done"

I can jump a chair

Free communications (beer and speech) is more important than the vote.

IKR?

I worked most of career in .au, the last 10 years as a contract Information Architect. All industries NGO, .gov, Big 4s, SMEs, Energy etc are depressingly not self aware. Like a complicated soup, they struggle with the laws of thermodynamics, Chinese whispers and too many chefs.

It's depressing as a stakeholder (ie citizen, customer, investor etc) to observe. OTH, it's been a lucrative career and I am enjoying a multi year sabbatical in Europe, studying Art History and (barely) managing a porn startup.

ymmv.

The benefit of compliance, is the license to trade.

You're correct of course, it can be expensive to test thoroughly. Depends on where your model and risk extend. The functional aspects of design? The maintenance of the software? Correct functioning of the ATM HW? Support procedures? Escalation? Audit? Independent verification? Monitoring of operational performance of it and other applications that provide inputs or consume outputs, etc ...the division, governance, the business?

My point is that especially in a fashionable Dev Ops world, the 'system' includes, but is not restricted to code. Do _you_ test the code, or do you test the system?

Yes, it can be cheaper to deal with consequences than to over engineer. Make sure you understand the consequences first before making that call however.

Often programmers or their leads or the PM etc are dimly if at all aware of the broader ecology in which their output features, or certainly more aware of short term requirements only. Like I said this is a business problem and not at all uncommon.

A coding error that was not caught in regression testing, and remained undetected and thus unpatched for years, breaking your organization's compliance... IS A BUSINESS ERROR.

https://en.wikipedia.org/wiki/...

In Australia, every year, cops kill more people than terrorists do.

It's not a bad thing.

distributed architecture.