Coté

A nice discussion that highlights the complexity id trade policy and, thus, rhe high risks of fucking it up. I like this critique of trade criticism: What makes Navarro’s critique challenging is that it’s not wholly wrong, at least from the American worker perspective, yet it’s not particularly actionable. So often, that last part is overlooked: you have to actually be able to on something, despite the past. Until we have time machines, finding flaws and suggesting how we should have fixed them is little use on its own.

A nice discussion that highlights the complexity id trade policy and, thus, rhe high risks of fucking it up. I like this critique of trade criticism: What makes Navarro’s critique challenging is that it’s not wholly wrong, at least from the American worker perspective, yet it’s not particularly actionable. So often, that last part is overlooked: you have to actually be able to on something, despite the past. Until we have time machines, finding flaws and suggesting how we should have fixed them is little use on its own.

A nice discussion that highlights the complexity id trade policy and, thus, rhe high risks of fucking it up. I like this critique of trade criticism: What makes Navarro’s critique challenging is that it’s not wholly wrong, at least from the American worker perspective, yet it’s not particularly actionable. So often, that last part is overlooked: you have to actually be able to on something, despite the past. Until we have time machines, finding flaws and suggesting how we should have fixed them is little use on its own.

A nice discussion that highlights the complexity id trade policy and, thus, rhe high risks of fucking it up. I like this critique of trade criticism: What makes Navarro’s critique challenging is that it’s not wholly wrong, at least from the American worker perspective, yet it’s not particularly actionable. So often, that last part is overlooked: you have to actually be able to on something, despite the past. Until we have time machines, finding flaws and suggesting how we should have fixed them is little use on its own.

A nice discussion that highlights the complexity id trade policy and, thus, rhe high risks of fucking it up. I like this critique of trade criticism: What makes Navarro’s critique challenging is that it’s not wholly wrong, at least from the American worker perspective, yet it’s not particularly actionable. So often, that last part is overlooked: you have to actually be able to on something, despite the past. Until we have time machines, finding flaws and suggesting how we should have fixed them is little use on its own.

It’s the end of the year - might as well be over once I wrap up today. On the other hand, if you’re in sales, it’s hardly the end of the year. It might be the most white-knuckling two weeks left. I’m sure glad I don’t do that work. Infrastructure Software in 2016 summerized Coté Content 2017 Predictions, Software Defined Talk In the last episode we make whacky predictions (not too whacky, actually) for 2017.

When we're talking with customers about the value that Puppet brings to them, invariably we talk about the future, and the future in their mind in some ways includes containers. There's a lot experimentation going on. There's a lot of Docker work being done and container work being done, Kubernetes work being done on their laptops. The conversations we have with them is how does Puppet help you bring it into production, into mission-critical production?

When we're talking with customers about the value that Puppet brings to them, invariably we talk about the future, and the future in their mind in some ways includes containers. There's a lot experimentation going on. There's a lot of Docker work being done and container work being done, Kubernetes work being done on their laptops. The conversations we have with them is how does Puppet help you bring it into production, into mission-critical production?

When we're talking with customers about the value that Puppet brings to them, invariably we talk about the future, and the future in their mind in some ways includes containers. There's a lot experimentation going on. There's a lot of Docker work being done and container work being done, Kubernetes work being done on their laptops. The conversations we have with them is how does Puppet help you bring it into production, into mission-critical production?

When we're talking with customers about the value that Puppet brings to them, invariably we talk about the future, and the future in their mind in some ways includes containers. There's a lot experimentation going on. There's a lot of Docker work being done and container work being done, Kubernetes work being done on their laptops. The conversations we have with them is how does Puppet help you bring it into production, into mission-critical production?