Live data from Hacker News

xlskubectl – a spreadsheet to control your Kubernetes cluster

github.com

51–60 of 78 posts

Re: xlskubectl – a spreadsheet to control your Kubernetes cluster

#51
This has to be the perfect passive aggressive comeback to bitchslap a project manager with a mirco-management fetish into the PaaS cost control limits the moment they demonstrate the power at their fingertips by adding a few zeroes. You have setup those limits didn't you, project manager?

Re: xlskubectl – a spreadsheet to control your Kubernetes cluster

#52
post #36
post #22

Better than yaml. Spreadsheets are underused as an UI. Every time you embed a table component in your app you probably wouldn’t complain about it being one.

The problem with spreadsheets vs regular tables is that spreadsheets allow for a lot of customisation (which is kind of the point of a spreadsheet vs a table). As a programming interface, that makes spreadsheets deceptively powerful. But as a UI were you need to have control over how the user interacts, that makes spreadsheets incredibly painful to integrate. Source: myself. I worked on a project around 20 years ago…

I wonder… there are all sorts of cloud offerings for office suites nowadays. Google, Microsoft.

If you have a shared spreadsheet in one of these systems, surely there must be some way to lock down some rows and columns, right? Then, the spreadsheet simply becomes a program where intermediary values are displayed and can be read. It seems really convenient.

Re: xlskubectl – a spreadsheet to control your Kubernetes cluster

#53
post #45
post #36

Earlier quoted context omitted.

The problem with spreadsheets vs regular tables is that spreadsheets allow for a lot of customisation (which is kind of the point of a spreadsheet vs a table). As a programming interface, that makes spreadsheets deceptively powerful. But as a UI were you need to have control over how the user interacts, that makes spreadsheets incredibly painful to integrate. Source: myself. I worked on a project around 20 years ago…

The great thing about spreadsheets is that most grown ups understand them. I've used it as the best UI for Accountants, Lawyers and other people that are famous for being afraid of technology. It's a great "bridge between "the system" and the people who want to get something from it.

If I were an accountant, I would be afraid of a lot of technology. In particular, if somebody offered me a Python code, and I didn’t know Python, I’d be quite worried about the handling of rounding and that sort of stuff, by some random programmer.

Excel was also written by some random programmer. But the code that does anything complicated was at least used by everybody in my field, so if there’s a hidden bug in there, at least the responsibility is diffuse. And the code written by me or by someone at my office… well, you can at least see what every cell does.

Re: xlskubectl – a spreadsheet to control your Kubernetes cluster

#54
post #36
post #22

Better than yaml. Spreadsheets are underused as an UI. Every time you embed a table component in your app you probably wouldn’t complain about it being one.

The problem with spreadsheets vs regular tables is that spreadsheets allow for a lot of customisation (which is kind of the point of a spreadsheet vs a table). As a programming interface, that makes spreadsheets deceptively powerful. But as a UI were you need to have control over how the user interacts, that makes spreadsheets incredibly painful to integrate. Source: myself. I worked on a project around 20 years ago…

There are a bunch of options for blocking cells from being edited etc.

Excel pros (I am none) can do quite some nice tools on top of Excel.

Excel runs the world ...

Re: xlskubectl – a spreadsheet to control your Kubernetes cluster

#55

Hey, I'm the person behind this project. Thank you for sharing this. Many people have reached out to improve it, and I might come back with a Jira version one day.

How about a Workday version? Maybe also one integrated with an Epic EMR somehow?

Re: xlskubectl – a spreadsheet to control your Kubernetes cluster

#58
post #36

Earlier quoted context omitted.

The problem with spreadsheets vs regular tables is that spreadsheets allow for a lot of customisation (which is kind of the point of a spreadsheet vs a table). As a programming interface, that makes spreadsheets deceptively powerful. But as a UI were you need to have control over how the user interacts, that makes spreadsheets incredibly painful to integrate. Source: myself. I worked on a project around 20 years ago…

I wonder… there are all sorts of cloud offerings for office suites nowadays. Google, Microsoft. If you have a shared spreadsheet in one of these systems, surely there must be some way to lock down some rows and columns, right? Then, the spreadsheet simply becomes a program where intermediary values are displayed and can be read. It seems really convenient.

There are ways. But there’s also countless ways you can mess with the contents. Plus the problem that spreadsheet “administrators” need to unlock to make their changes and remember to re-enable those locks when they’re done.

At some point, something invariably gets missed and someone else finds a way to tamper with it.

Bear in mind that the “tamperers” are never doing so maliciously. They’re just trying to do their job too. But when you have a UI that allows for unlimited abstractions, those “tamperers” will dream up a new way to represent their needs without realising that they’re breaking someone else’s workflow.

Re: xlskubectl – a spreadsheet to control your Kubernetes cluster

#59
post #45

Earlier quoted context omitted.

The great thing about spreadsheets is that most grown ups understand them. I've used it as the best UI for Accountants, Lawyers and other people that are famous for being afraid of technology. It's a great "bridge between "the system" and the people who want to get something from it.

If I were an accountant, I would be afraid of a lot of technology. In particular, if somebody offered me a Python code, and I didn’t know Python, I’d be quite worried about the handling of rounding and that sort of stuff, by some random programmer. Excel was also written by some random programmer. But the code that does anything complicated was at least used by everybody in my field, so if there’s a hidden bug in the…

You speak to me as an insurance guy that also writes code to get things done. Excel is everywhere. So - everyone has the same lens/bug. Also, rounding/numbers in SQL
Post reply on HN