Quotes About Deployment

Conflating thought experiments with reality could slow the deployment of AVs that are reliably safer than human drivers.

Debugging tip: For server applications, be sure to always specify the -server JVM command line switch when invoking the JVM, even for development and testing. The server JVM performs more optimization than the client JVM, such as hoisting variables out of a loop that are not modified in the loop; code that might appear to work in the development environment (client JVM) can break in the deployment environment (server JVM).

I remember during the Gulf War, my father's ship had just finished a deployment in in the Gulf and was on its way back when the war started in Kuwait. They turned around and went back to the Gulf.

Threatening words are dispatched like soldiers under strict orders: Cause anxiety that cannot be ignored. Surprisingly, their deployment isn't entirely bad news. It's bad, of course, that someone threatens violence, but the threat means that at least for now, he has considered violence and decided against doing it. The threat means that at least for now (and usually forever), he favors words that alarm over actions that harm.

We must either reduce the number of our engagements or increase the number of our troops.

Without the Guard and Reserve, our active duty troops could hardly deploy.

Make no mistake, our troops will be in Afghanistan and Iraq for a long time.

I have a very deep concern about President Obama putting in another 21,000 troops into Afghanistan with the promise of more to come.

The Obama presidency has seen the U.S. military's elite tactical forces increasingly used in an attempt to achieve strategic goals. But with Special Operations missions kept under tight wraps, Americans have little understanding of where their troops are deployed, what exactly they are doing, or what the consequences might be down the road.

Any soldier deployed overseas will think fondly of home. It is only right and fair that they are able to settle back into a home life once they leave their service.

I volunteered to deploy to Iraq. I was one of the few soldiers who were not on the mandatory deployment roster - close to 3,000 Hawaii soldiers were.

When I deployed to Iraq with my fellow soldiers, putting our lives on the line for our country, no one in the media questioned our patriotism because of our religion.

I don't think anybody accepts the idea that somehow I should be punished because I actually served our country during a very difficult time post-9/11. That required me to actually be out of Arkansas for a few years.

When you get out of the military, all you are doing is a work-up for the longest deployment of your life.

When we released JUnit 4 recently we spent nearly half of our engineering budget on reducing the cost of deployment for our clients. We tried to make sure that new-style tests would work with old tools and old-style tests would work with new tools. We also worked to make sure we had the freedom to make future changes to JUnit without breaking client code.

XP always keeps the system in deployable condition. Problems are not allowed to accumulate.

The fault of the courage culture, therefore, is not its underlying message that courage is good, but its severe underestimation of the complexity involved in deploying this boldness in a useful way.

Except for naval and air exercises, our military should be stationed on American soil, where service men and women can lead normal lives in close proximity to family and friends.

Platforms can bootstrap their networks by issuing a token with an additional value proposition in the network. Users can keep the token and deploy it in the context of the network or sell it for a profit. Either way, employing tokens in a platform usually increases activity.

I've seen this movie before. The plot is simple: First, you take an urgent date-driven project, where the shipment date cannot be delayed because of external commitments made to Wall Street or customers. Then you add a bunch of developers who use up all the time in the schedule, leaving no time for testing or operations deployment. And because no one is willing to slip the deployment date, everyone after Development has to take outrageous and unacceptable shortcuts to hit the date.

There should be absolutely no way that the Dev and QA environments don't match the production environment.

So much about DevOps is counter intuitive, contrary to common practice, and even controversial. If production deployments are problematic, how on earth can deploying more frequently be a good idea? How can reducing the number of controls actually increase the security of our applications and environments? And can technology really learn anything from manufacturing?

This kind of service-oriented architecture allows small teams to work on smaller and simpler units of development that each team can deploy independently, quickly, and safely. Shoup notes, "Organizations with these types of architectures, such as Google and Amazon, show how it can impact organizational structures, [creating] flexibility and scalability. These are both organizations with tens of thousands of developers, where small teams can still be incredibly productive.

What use is it having all these offshore developers building features if we aren't getting to market any faster? We keep lengthening the deployment intervals, so that we can get more features deployed in each batch.