louniks

Except we don't, not really. We're still leveraging 15 or so years of experience living the real world and walking on sidewalks and crossing streets and observing how other humans drive cars and being passengers in cars before we ever try driving ourselves. Not to mention, some humans definitely don't learn to drive in a matter of hours, they need weeks if not months.

From what we were told this morning, this is a purely Red Hat decision not influenced by IBM, primarily intended to reduce our spending and save cash in light of the increased cost of money caused by rising interest rates.

Roles affected will be "general and administrative" (apparently this is a GAAP - Generally Accepted Accounting Practices - term), and folks directly involved in developing or selling products (my interpretation: software engineers and sales) are safe.

Source: am Red Hatter, opinions/interpretations are my own.

I wonder if this can be viewed as (yet another?) example of companies externalizing the negatives. Pollution is the classic example, both during manufacture and at the end of the lifecycle. In this case, it would be financial risk. Founders bootstrap a start-up, either with their own money or outside investors, and these folks carry all the risk. The established players can safely wait until the startup either fails or succeeds, and buy into a sure thing in the latter case.

I'm a Red Hatter, and I'm not sure what they mean either. I obviously only know my own little corner of engineering, but I've seen no signs whatsoever of being gutted. From where I stand, it's just a change of ownership that, at least for now, is completely transparent on the ground. I expect the situation to continue for as long as Red Hat keeps making money.

If someone's willing to put in the time to redo our code in Python, I wouldn't be opposed to that. However, keep in mind that it'd be a massive undertaking. Last time we re-wrote our apps, it took a full-time developer multiple months. Admittedly, everything was brand new, and included collecting requirements and validating the prototypes with the volunteers. So perhaps a "simple" rewrite, keeping all the logic the same, wouldn't be so hard.

Also keep in mind - a good chunk of the volunteers aren't tech-savvy, and are nervous when faced with changes. Just upgrading to a new phpBB version, with a new theme, was met with some grumbles.

I realize I'm a horrible salesman, but something about LibriVox just keeps me involved. I don't even participate in the audiobooks aspect of it, just tech. I was initially brought on as a paid sysadmin as part of that project to modernize our code that took that full-time developer months. When that ended, I stuck around as a volunteer.

I'm not married to Gerrit, and I concede that it could be a hurdle. It's what I use for my day job, so I chose it out of laziness and familiarity more than anything else. I'll probably drop it, and learn the GitHub PR tools and workflow - I've gotten a few random PRs already.

Edit: I'll talk to the volunteers about making that Google doc public, good suggestion.

Playing devil's advocate for a bit, would the A220 have accumulated so many orders had it not been backed by Airbus? The program was clearly in trouble when Airbus took over, which may have discouraged airlines from taking a chance on a great aircraft, but whose manufacturer ran the risk of running out of money to keep the program going.

But why? From my very limited knowledge on this, it seems everyone is saying that a no-deal crash out will be bad economically. So is it just ideology (dare I say dogmatism) from the Johnson government at this point?

You just got all the 90s kids hooked on skruf.

I instinctively read it as "what-wee-gee"

Did I understand your purpose wrong, or can the same thing be achieved by running sshd on a (cluster of) machine(s) that mount a GlusterFS/Ceph/OtherDistributedRedundantFS volume?

Remember the "at Amazon, everything is a platform" Google+ post?

Drones as a Service.