Doing software better at the south east’s largest power company. www.charlotteagenda.com/97827/sko…

Doing software better at the south east’s largest power company. www.charlotteagenda.com/97827/sko…

> There is also the cost of different people thinking about data differently because they are working with different platforms and not really speaking the same language as each other. I hear about this all the time from customers. They’ll have two people from their own organisation pitch up in a meeting with two different answers to the same questions, supposedly from the same data source. > But those data sources are being run through different platforms and end up getting corrupted or changed or amended.

> There is also the cost of different people thinking about data differently because they are working with different platforms and not really speaking the same language as each other. I hear about this all the time from customers. They’ll have two people from their own organisation pitch up in a meeting with two different answers to the same questions, supposedly from the same data source. > But those data sources are being run through different platforms and end up getting corrupted or changed or amended.

“Lock-in” is about switching costs (a Simon Phipps put it long ago, “the freedom to leave”) and can thus be considered strategically, even financially, rather than numbing, stupefying FUD. aws.amazon.com/blogs/ent…

“Lock-in” is about switching costs (a Simon Phipps put it long ago, “the freedom to leave”) and can thus be considered strategically, even financially, rather than numbing, stupefying FUD. aws.amazon.com/blogs/ent…

> ITIL came from a very different IT setup compared to that of today’s startups. IT had a supporting, not central role in the organizations’ daily operations

> ITIL came from a very different IT setup compared to that of today’s startups. IT had a supporting, not central role in the organizations’ daily operations

> In practice, most stakeholders are not interested in detailed diagrams, but rather in one or two high-level diagrams which reflect the modularity and boundaries of the system. Beyond these, for a deeper understanding, the code should be the source of truth, which in most of the cases only developers are interested in. www.infoq.com/articles/…

> In practice, most stakeholders are not interested in detailed diagrams, but rather in one or two high-level diagrams which reflect the modularity and boundaries of the system. Beyond these, for a deeper understanding, the code should be the source of truth, which in most of the cases only developers are interested in. www.infoq.com/articles/…