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.

The big takeaway is that small increases in IT budgets are the new normal. Unlike previous recoveries, we have not seen a large jump in IT spending over the past five years. So if a CIO is only seeing a two or three percent increase this year, he or she should understand that is pretty much in line with other companies. See more guidance charts on IT priorities, n=190.

The big takeaway is that small increases in IT budgets are the new normal. Unlike previous recoveries, we have not seen a large jump in IT spending over the past five years. So if a CIO is only seeing a two or three percent increase this year, he or she should understand that is pretty much in line with other companies. See more guidance charts on IT priorities, n=190.

Integration talk, plus the idea of IT becoming BT: “business technology.” Link

Integration talk, plus the idea of IT becoming BT: “business technology.” Link

Integration talk, plus the idea of IT becoming BT: “business technology.” Link

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.

The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has awhole slew of updates across the board. My selective highlights: Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support). Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput. Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.