trenches

It means that what constitutes the content of a good CS education doesn't map to in-the-trenches software development.

We are even beginning to get better about rewarding the people who work down in the comic-book trenches creating these characters.

Since railroads depend heavily on communications, they maintain their own poles/trenches and cables etc.

You can learn about all of these things the hard way: in the trenches with us, as we scale.

You need mastery, which can only be gained by time in the trenches.

The espionage act, dating from the world war (The one with trenches and horses, not that new one) has no explicit whistleblower protection.

Military training, 3 1/2 days of digging ad building trenches by hand.

The elite don't have to work in the trenches afterwards...

Once, but I hated it, back to the grunge and trenches for me.

This is important, as if you are laying underground fibre then the cost of digging new trenches (~AUD$100/m) is a huge component of the total construction cost.

This might be purely because we're the first out of the trenches...

Similarly, if there are existing poles that can be rented then installing aerial cables (~AUD$30/m) is cheaper than digging trenches, but more expensive than using existing underground duct [1].

From the trenches it's hard for me to consider Atlassian the "standard" of modern development focussed organizations.

I'll take a stab at it, at least my perspective on it from the "enterprise application" trenches.

"War stories." "Knife fight." "In the trenches." A trench is a muddy hole in the ground that you had to dig yourself to keep your innards from getting pierced by flying metal.

All LTE, all the time.) Regarding my limits - the nice things about Tier-1 ISPs (which Comcast is) - is that they don't pay for data use, as they engage in what is called "Settlement Free Peering" - what they do pay for is (roughly) Trenches + Vaults + Data Center Real Estate + Power + cooling + security + Chassis + Fiber + Interconnect Ports + Line-Cards.