230 karma · joined December 28, 2017
They are right, however the conclusion that should be drawn from this is that the most likely outcome of your organisations implementation of agile will be equally as poor, and that it should prolly be skipped.
So a simple shader would be something like (in pseudo code):
function shader( x, y ) { if( x > 0.5 ) return white; else return black; }
would color one half of the screen black, and the other white.
Making big assumptions about what the software project here. Given the article was mostly complaining about software developed for developers by developers, I don't think we can blame the suits for this one.
I would say that in the domain of game development C++ (which is where I'm guessing that most new C++ development is done) has such a moat that Rust in it's current form will not be able to displace it.
Contra, "rules" are only effective when they are enforced, and when push comes to shove, most of the keepers of the rules will just discard them when it gets in the way of things they really care about.
Getting the enforcers of stupid rules to waive away rules so things can get done is a valuable skill in anyone's tool chest.
In the article's case, the teacher was being a pain. He didn't consult the team when the disqualifying issue was found, nor did he consult with the TSA to clarify or get an exemption from the rule. The real lesson is to avoid or work around these types of people in any endeavor, they don't want to work with ppl to advance the cause of their organisation, they just love their rules.
In my experience, internal apps need far more love. Maintaining internal apps is far more useful than most 'real' work, just because it can be a multiplier on so much other 'real' work.
While they certainly do value engagement over quality, I suspect that the systems are put in place because they don't scale in terms of manpower, and they don't trust their users to do formalize the structure of the site.
https://tradingeconomics.com/hong-kong/households-debt-to-gd....
vs.
https://tradingeconomics.com/france/households-debt-to-gdp#:....
I find this is particularly the case when the design flaw is particularly bad, the developers end up adding complexity to work around the flaw, which has the effect of hiding the flaw, making it alot less obvious to the novice.
In Australia apparently all you have to do to get into this group would be to actually own a paid off house. :/ I think this says far more about housing then wealth inequality though.
Unless you are doing firmware where all those constraints are still around, and you have to deal with whatever compiler the vendor supplies for their microcontroller, which will almost certainly be some variant of C.
https://www.finder.com.au/australias-personal-debt-reported-...
I'm including 'Investment debt' cause who are we kidding? It's all investment properties.
Well if it's found that the construction/design of the building is at fault, then it will be the developers.
Not for individuals, but when you are a high net worth individual, it's all the same.