kottapar

This sounds very similar to BootC except that BootC is immutable

I tried with a name starting with E, max legibility; except for styles 5 and 7 the rest of them looked like a t.

From the example provided I can see that the KCL K8s sample had 18 lines whereas the generated YAML file had 21 lines. I'm sort of missing the point here as to how KCL is helping here.

> What was even more surprising, to me, is that Mercedes had this amazing nice center console unit to control things with your arm in a rested position. They removed that piece of brilliance!

Mazda also has this beautiful dial-joystick which we can operate in a rested position. It is so intuitive that I stopped using the touchscreen console itself. On the other hand even when we operate using a dial and buttons we take our eyes for an instant to look at the screen to check the changes. Now imagine looking away at a touchscreen just to see what operation to perform etc. This is a major distraction.

This was around 2009. A colleague in the team was checking a high cpu alert on a payment system cluster. He found some PIDs that were consuming high cpu and asked someone in the team on how to get more details. He was asked to use fuser to check. He did use the fuser but it was fuser -cuk. The -k for killing the process created quite a mess.

This is indeed surprising. Any time we have slowness issues the usual recommendation would be to throw resources at the problem; increase cpu, add more memory et al. We used to lament that we should spend time debugging the problem and fix the actual issue. We then used to say that probably at places like AWS and the other biggies they'd be following some excellent best practices and we should also strive to reach that level of excellence.

> We had a lot of little scripts here and there which would solve extremely specific situations but no focus was ever put on in building a general framework or trying to reduce the ticket count.

wow, honestly this is surprising. For me as an end customer I was always impressed with the way the services are engineered. Kudos to people like you for making this happen. But then I was also under the impression that AWS has very good best practices to take care of repeating issues.

Wouldn't interim patch-ups cause stability issues in the long term?