This is my biggest frustration. Why not check with the compiler to generate code that would actually compile? I've had this with Go and .Net in the Jetbrains IDE.
Had to turn ML auto-completion off. It was getting in the way.
Any book about technology's effects on society written before 2022 needs a massive update since the LLM revolution. Sadly, Gertz's "Technology and nihilism" was published in 2018.
Been reading about Systems Thinking lately.
I think the command and control assumption comes from the influence of System Dynamics (Forrester, Meadows, Senge), which attempts to simulate the system. This seems to be a North American view of systems thinking due to the popularity of Systems Dynamics. But the European views have a focus on emergent behaviour and critically looking at hierarchies and power structures. Although Meadows emphasises 'dancing with systems' in contrast with controlling systems.
Or that Telco who had an API that couldn't handle more than one concurrent request per minute, and will fall over if I did more than that. Throw in FTP for extra complexity..
Integration challenges are hard. Makes sense for Stripe to buy someone who has solved it.
This was our experience as well. There was no way I would have left my wife alone for the first 4-6 weeks. Even though we didn't have any complication and a relatively "easy" birth. First month was just survival mode. I took 5 weeks off (4 weeks paid paternity leave and another of annual leave) . I'm glad I was around. It increased my confidence as a father too.
It depends on the project. CF isn't the only platform. I've worked on non-CF projects under the GDS umbrella. There is a bit of Azure PaaS and AWS too.
Also, don’t be surprised if the team was given a project which was really hard to deliver with the team’s capabilities, and the CEO or his team leader, should have recognised that in the first place, and they (CEO etc) will be hard to convince that they are part of the issue.
Also your list of things look like something that would take a rather long time to implement (many months), especially if you have a late project to deliver on at the same time.
There is a fine line to tread to make these changes whilst delivering. There was never a point were we stopped everything to make all these changes. The changes have to happen gradually, and they do take a long time, many months. It involves changing people, teaching them new habits and helping them do it. The habits have to be sustainable.
Limiting work in progress, forces the issue upstream. Managers are forced to realise how much of a precious resource the team is, and why they are struggling. Throwing more work at a struggling team makes it even worse.
Bingo, you've hit the nail :) This is what I love about K8S. In addition you've got the K8S reconciliation loop running constantly to make sure the system is in the state you described via the API.
