Something tells me that they may invest in the future in a safety coordinator and a fire marshal... Couldn't upvote the horror though; great display of human stupidity however.

Yep, spend 30+ seconds coordinating and setting up the scene, so you can in one move, replace 5 actions that take 3 seconds each.

It's brilliant! Brilliant, I tell you!

This is elaborate, and very Canadian visual metaphor. The naked man represents the terror of divulging that which is most vulnerable while being intoxicated, while the tackle represents the motor coordination challenges while same. Asking for help to "bring it in" being a rejected cry for help. The canoe represents the territory of self, surrounded by the depth of the dark feelings.

It's a very basic Canadian mode of self-reflection.

It's the team hive mind. It just happens in sports or any type of adrenaline meets muscle memory and group coordination.

Its pretty cool that its one shot, it must have been a really hard thing to coordinate and time perfectly, but I thought the majority of punches here REALLY look like obvious fake moviepunches, ie, a punch in the face is a light touch on the shoulder. I know that they ARE movie punches in every movie, obviously, but shooting from the right angle usually hides the cheat. In this shot, i guess they sacrificed that to get it all in one shot, but imo, that killed the realism.

Oh, and here's that interview with the stunt coordinator:

http://observer.com/2015/04/daredevil-stunt-coordinator-on-designing-a-one-shot-fight-scene-for-a-blind-hero/

So it was genuinely one shot? No cuts?

No cuts. We did do a few Texas Switches between our actor and our stunt double, but it was purely a one shot fight. There were no cuts in that fight. Every performer, the actors and the stunt doubles, were in there performing that fight full on. I’d say there was a minimum of 105 beats, and they killed it.

Immediately thought of this entry in "City of Dreams", a Wiki-like book of facts about Port Townsend (PT) WA:

"Centipedes"

The Port Townsend Centipedes (PTC) were a ten-man team who, on July 27,1977, thrilled some 10,000 Seattle Kingdome spectators by winning the Seafair World Championship Tug-of-War. They not only brought home the laurels but also a winner-take-all check for $10,000. The PTC's success story was an object lesson in strategy. By adding art, ratiocination, strategy, and what might best be called a strange brand of PT spirit, they essentially redefined the sport. One reporter described their tactics as a "gumbo of hatha yoga, marital arts, intense dedication, and communal discipline." They proved that tug-of-war can be a little man's sport. Their average weight was less than 150 pounds. On the evening of their victorious tug in the Kingdome against the Montgomery Loggers of Cle Elum, Washington, authoritative bystanders noted how much more muscular the opposition was and predicted an easy victory for the Centipede's opponents. But, as one of the Centipedes said, "We are one being when on the end of a rope." They chose their name as one indication of their strategy: traction. They reasoned that if they could get ten sets of arms and legs working in perfect unison, they would have an advantage over those who tugged with fewer, larger bodies. They were right.

They also practiced rhythm, which included not only coordinating their breathing, but also pacing, the use of the "standing arch," and allowing some members to rest at given times during the tug-of-war. The Centipedes developed their own mythology and terminology: their "house of pain" was a technique of prolonging the tug-of-war in order to exhaust the opposition before administering the coup de grace.

[Not noted in this article is the rules stated that the each team had a weight limit, not a number-of-people limit. The PT team chose to spread the weight over more people.]

63 months!

Not one torturer, not one wiretapper, not one CEO of a major bank in jail, none. But Barrett Brown gets 63 fucking months.

Meanwhile, the EU's counter-terrorism coordinator threw down the gauntlet, wants backdoors from all tech companies running the communications networks.

My post is not hyperbole, but actual personal observation.



You also have to factor in cost+ funding.

On one hand, it's necessary. Because you don't know how much something truly new will cost - you haven't done it before. You'll discover as you go.
It would be unfair to bind a company to a fixed cost, when nobody knows what the cost will be. It's mathematically unreasonable to entertain a fixed cost on new technologies.

(Granted, everyone gives silly lowballed best-case estimates when bidding. Anyone that injects a sense of reality into their bid is too costly and doesn't get the contract).

On the other hand, cost+ means that you make more money by spending more money. So hiring hordes of nobodies for every little task, making 89347589374 different position titles, is only gonna make you more money. There's no incentive to save.



F35 wise, like I said, it's not designed for any war we fight now.
It's designed for a war we could fight in the future.
Because you don't start designing weapons when you're in a war, you give your best effort to have them already deployed, tested, and iterated into a good sustainable state, before the onset of a conflict that could require them.

F35 variations are not complicated. The VTOL variation is the only one with any complexity. The others are no more complex than historical variations from early to late blocks of any given airframe.

The splitting of manufacturing isn't in itself a complication ridden approach. It's rather normal for different companies to work on unrelated systems. Airframe will go somewhere, avionics elsewhere, engine elsewhere, etc. That's basically a given, because different companies specialize in different things.

Keep in mind that the large prime contracts (Lockheed/GD/etc) don't actually "make" many things. They are systems integrators. They farm out the actual development for most pieces (be it in house contractors or external contractors - because they are easy to let go after the main dev is over), and they themselves specialize in stitching the pieces together. Connecting things is not difficult when they are designed with specified ICDs from the get-go. The black boxes just plug up to each other and go.

The issues that arise are often a matter of playing telephone. With one sub needing to coordinate with another sub, but they have to go through the prime, and the prime is filtering everything through a bunch of non-technical managers. Most problems are solved in a day or two when two subs physically get their engineers together and sort out any miscommunications (granted, contracts and process might not allow them the then fix the problem in a timely and affordable manner).

The F22 and F35 issues are not major insurmountable tasks. The hardest flaws are things that can be fixed in a couple months tops on the engineering side. What takes time is the politics. Engineers can't "just fix it". There's no path forward for that kind of work.

Sure, in a magic wonderland you could tell them "here, grab the credit card, buy what you need, make any changes you need, and let us know when you're done" - and a little while later you'd have a collection of non-approved, non-reviewed, non-traceable, non-contractually-covered changes that "just fix the damn thing"... and you'd also have to incur the wrath of entire departments who were denied the opportunity to validate their existence. The 'high paid welfare' system would be all over your ass.

-scheherazade

All well and good, but the reason why all the oversight costs piles up is because this plane isn't a solution to a military problem, it's a solution to an economical problem.

It's government stimulus, pure and simple. Get a whole bunch of different contractors from different companies and hand them money to build parts for a warplane that covers roles that are already covered. Keep those guys ticking over to prevent a collapse of the arms industry (or to prevent them developing products for sale to buyers the US might not consider kosher).

And then, because you're dealing with different companies, you need to coordinate, ensure compatibility, oversea each company to make sure they are on time/program/budget etc etc.

You build a plane under one roof, the entire process is overseen by the company and the government get's to check up on them. Far simpler. One department doesn't deliver inside that company, their management has to fix the problem or default on the contract. One company holds up the whole plane, do the other companies get penalised? Of course not, their staff sit around drawing wages with their thumbs up their asses waiting. And the government keeps paying.

Additionally, the planes the F35 is supposed to replace are all better at their jobs because they are specialised. You put every topping ever conceived on that government pizza and no one will like it (apart from perhaps the homeless who would eat anything to stave off starvation). Build a new warthog, improve on the materials, give it better armaments etc and put the tried and true design back to work. That's the core of the super hornet program, right?

When you look at the state of the world, the only real threats currently to America are the bloody terrorists (which, as you note, isn't exactly an existential threat), and the flexing of military might in 2nd world countries not withstanding, there is very little need for a frankenplane that doesn't do anything particularly good.

China and Russia? Lol, the US has 75% more combat aircraft and 400% more combat helicopters. Factor in China's pretty sparse air assets, in an air war, including force multipliers such as electronic warfare/early warning/air co-ordination and carriers, the US would be able to show down both nations handily with it's existing fleet.

I really do appreciate the point you're making, but that just adds insult to injury. The awful waste built in to the program is even more appalling when you consider that the F35 is a plane no one really needs, or even wants.

This video lacks a lot of salient details.

Yes, the F35 is aiming at the A10 because contractors want jobs (something to do).

However, the strength of the A10 is also its weakness. Low and slow also means that it takes you a long time to get to your troops. Fast jets arrive much sooner (significantly so). A combination of both would be ideal. F35 to get there ASAP, and A10 arriving later to take over.

It's not really worth debating the merit of new fighters. You don't wait for a war to start developing weapons.

Yes, our recent enemies are durkas with small arms, and you don't need an F35 to fight them - but you also don't even need to fight them to begin with - they aren't an existential threat. Terrorist attacks are emotionally charged (well, until they happen so often that you get used to hearing about them, and they stop affecting people), but they are nothing compared to say, a carpet bombing campaign.

The relevance of things like the F35 is to have weapons ready and able to face a large national power, should a nation v nation conflict arise with a significant other nation. In the event that such a conflict ever does, you don't want to be caught with your pants down.

Defense spending costs scale with oversight requirements.

Keep in mind that money pays people. Even materials are simply salaries of the material suppliers. The more people you put on a program, the more that program will cost.

Yes, big contractors make big profits - but the major chunk of their charges is still salaries.

Let me explain what is going on.

Remember the $100 hammers?
In fact, the hammer still cost a few bucks. What cost 100+ bucks was the total charges associated with acquiring a hammer.
Everything someone does in association with acquiring the hammer, gets charged to a charge code that's specific for that task.

Someone has to create a material request - $time.
Someone has to check contracts for whether or not it will be covered - $time.
Someone has to place the order - $time.
Someone has to receiver the package, inspect it, and put it into a received bin - $time.
Someone has to go through the received items and assign them property tags - $time.
Someone has to take the item to the department that needed it, and get someone to sign for it - $time.
Someone has to update the monthly contract report - $time.
Someone has to generate an entry in the process artifacts report, detailing the actions taken in order to acquire the hammer - $time.
Someone on the government side has to review the process artifacts report, and validate that proper process was followed (and if not, punish the company for skipping steps) - $time.

Add up all the minutes here and there that each person charged in association with getting a hammer, and it's $95 on top of a $5 hammer. Which is why little things cost so much.

You could say "Hey, why do all that? Just buy the hammer".
Well, if a company did that, it would be in trouble with govt. oversight folks because they violated the process.
If an employee bought a hammer of his own volition, he would be in trouble with his company for violating the process.
The steps are required, and if you don't follow them, and there is ever any problem/issue, your lack of process will be discovered on investigation, and you could face massive liability - even if it's not even relevant - because it points to careless company culture.

Complex systems like jet fighters necessarily have bugs to work out. When you start using the system, that's when you discover all the bits and pieces that nobody anticipated - and you fix them. That's fine. That's always been the case.



As an airplane example, imagine if there's an issue with a regulator that ultimately causes a system failure - but that issue is just some constant value in a piece of software that determines a duty cycle.

Say for example, that all it takes is changing 1 digit, and recompiling. Ez, right? NOPE!

An engineer can't simply provide a fix.

If something went wrong, even unrelated, but simply in the same general system, he could be personally liable for anything that happens.

On top of that, if there is no contract for work on that system, then an engineer providing a free fix is robbing the company of work, and he could get fired.

A company can't instruct an engineer to provide a fix for the same reasons that the engineer himself can't just do it.

So, the process kicks in.

Someone has to generate a trouble report - $time.
Someone has to identify a possible solution - $time.
Someone has to check contracts to see if work on that fix would be covered under current tasking - $time.
Say it's not covered (it's a previously closed [i.e. delivered] item), so you need a new charge code.
Someone has to write a proposal to fix the defect - $time.
Someone has to go deal with the government to get them to accept the proposal - $time.
(say it's accepted)
Someone has to write new contracts with the government for the new work - $time.
To know what to put into the contract, "requrements engineers" have to talk with the "software engineers" to get a list of action items, and incorporate them into the contract - $time.
(say the contract is accepted)
Finance in conjuration with Requirements engineers has to generate a list of charge codes for each action item - $time.
CM engineers have to update the CM system - $time.
Some manager has to coordinate this mess, and let folks know when to do what - $time.
Software engineer goes to work, changes 1 number, recompiles - $time.
Software engineer checks in new load into CM - $time.
CM engineer updates CM history report - $time.
Software engineer delivers new load to testing manger - $time.
Test manager gets crew of 30 test engineers to run the new load through testing in a SIL (systems integration lab) - $time.
Test engineers write report on results - $time.
If results are fine, Test manager has 30 test engineers run a test on real hardware - $time.
Test engineers write new report - $time.
(assuming all went well)
CM engineer gets resting results and pushes the task to deliverable - $time.
Management has a report written up to hand to the governemnt, covering all work done, and each action taken - documenting that proper process was followed - $time.
Folks writing document know nothing technical, so they get engineers to write sections covering actual work done, and mostly collate what other people send to them - $time.
Engineers write most the report - $time.
Company has new load delivered to government (sending a disk), along with the report/papers/documentation - $time.
Government reviews the report, but because the govt. employees are not technical and don't understand any of the technical data, they simply take the company's word for the results, and simply grade the company on how closely they followed process (the only thing they do understand) - $time.
Company sends engineer to government location to load the new software and help government side testing - $time.
Government runs independent acceptance tests on delivered load - $time.
(Say all goes well)
Government talks with company contracts people, and contract is brought to a close - $time.
CM / Requirements engineers close out the action item - $time.

And this is how a 1 line code change takes 6 months and 5 million dollars.

And this gets repeated for _everything_.

Then imagine if it is a hardware issue, and the only real fix is a change of hardware. For an airplane, just getting permission to plug anything that needs electricity into the airplanes power supply takes months of paper work and lab testing artifacts for approval. Try getting your testing done in that kind of environment.



Basically, the F35 could actually be fixed quickly and cheaply - but the system that is in place right now does not allow for it. And if you tried to circumvent that system, you would be in trouble. The system is required. It's how oversight works - to make sure everything is by the book, documented, reviewed, and approved - so no money gets wasted on any funny business.

Best part, if the government thinks that the program is costing too much, they put more oversight on it to watch for more waste.
Because apparently, when you pay more people to stare at something, the waste just runs away in fear.
Someone at the contractors has to write the reports that these oversight people are supposed to be reviewing - so when you go to a contractor and see a cube farm with 90 paper pushers and 10 'actual' engineers (not a joke), you start to wonder how anything gets done.

Once upon a time, during the cold war, we had an existential threat.
People took things seriously. There was no F'ing around with paperwork - people had to deliver hardware. The typical time elapsed from "idea" to "aircraft first flight" used to be 2 years. USSR went away, cold war ended, new hardware deliveries fell to a trickle - but the spending remained, and the money billed to an inflated process.

-scheherazade

@dannym3141

Broadly speaking, I tend to subscribe to the view that capitalism is the worst economic system anyone ever invented, except for all the others. There are plenty of problems with it but also practical solutions that could be implemented. Pining for a better system is great, but this quasi-vague revolution that Brand is espousing is as almost guaranteed to be as direction-less and short lived as the Occupy movement.

Take campaign finance reform, of what I'm familiar the Mayday PAC in the US is proposing a voucher system where either (1) each voter is given and limited to a set amount tax refund they can spend on campaign contributions or alternatively (2) there is public finance for something like a 10 to 1 matching system for smaller donations. That seems like a good solution to the problem. It's not perfect though, as speech via the media (TV, internet) would still be wielded disproportionately by those with power. But it's a start. More transparency on where donations are coming from would also help.

I'm no fan of inequality either, but it's a far more difficult issue to grapple with. If you approach it with taxes, the problem is you need global coordination. A single country raising taxes will just see incomes shift elsewhere particular the highest percent who are the most mobile. There needs to be some kind of standard on taxation globally as to whether it is incurred where it is earned or where the company is registered, otherwise you have companies like Apple paying next to nothing because they avoid it in both countries (known as the double Irish, although this has now been eliminated it's a good example).

Should investment income be taxed higher? Probably, I'm not too well informed on this subject but it certainly entrenches established wealth. Should there be an estate-like tax of sorts that limits wealth passed on through generations? Perhaps, but it seems like a band-aid of sorts and a double dipping on what should really be collected through income tax in the first place.

I'm all for public services where it makes sense to provide them publicly. I don't like political cronyism either. But solutions need to be practical. Eliminating tax avoidance by multinationals is good policy because otherwise these companies paying virtually no tax intrinsically sets up barriers to entry to smaller competitors which is terrible economically and leads to monopolistic behaviour and higher prices. Targeting finance with a specific tax probably isn't. Business will just shift globally and countries like the UK will lose out more than they gain.

Technically this is crazy impressive. The drone operator and camera operator have to be stupid talented. The coordinator and choreographer for this should get crazy awards. I agree that the song is meh, but OMG is the video impressive. I would love to see behind the scenes on this. BRAVO!

All that was required was for the RTH to climb 20 metres first and it would've been fine!

Don't some drones retrace their steps instead of drawing a straight line from current position to the initial GPS coordinates? Even a customisable minimum altitude for RTH would be enough in many cases.