An online notebook
But the real answer to the question depends on how IT is defined. If narrow definition is used and IT is taken to mean nothing more than base infrastructure, then Carr’s viewpoint remains correct. If, however, the definition of IT encompasses the entirety of an organization’s technology portfolio and strategy, however, the assertion that IT doesn’t matter could not be less accurate today.
Original: https://redmonk.com/sogrady/2018/06/29/it-matters-again/
They’re part of “working in the open”, sure. Showing what you’re doing, and that you haven’t (yet?) replaced everyone by robots. But corporate blogs that are consistently a good read, and not done by a tiny start up, are not “open”. At least not in the way we normally think of “openness”, as a synonym for unmediated.
Original: https://medium.com/@fitzsimple/professional-blogs-are-a-lot-like-reality-tv-96c405589c9b
Writing great APIs demands we use a range of techniques to improve the way we write code. Pair programming, test-driven development and coding in the open are all important attributes of writing great code and therefore making our APIs reusable outside Hackney.
Original: https://blogs.hackney.gov.uk/hackit/Developing-our-API-strategy
There should be a situation where outsourcing in the public sector can be managed appropriately and used to complement in-house service delivery and policy-making.
The problem is that such a balance demands in-house skills – and we outsourced all of them!
Original: https://government.diginomica.com/2018/06/26/outsourcing_liddington_government/#.WzuS0AW5WUQ.twitter
The Anchorage payroll project, now in its seventh year and with costs ballooning from a projected $10 million to over $80 million provides a solid example of how to guarantee an enterprise project failure.
Original: https://diginomica.com/2018/06/27/how-to-guarantee-an-enterprise-project-failure-the-anchorage-payroll-example/