3 ms·

In these scenarios these low code tools feel like the evolution of excel. How many times did people who couldn't write full on apps throw something together wit

In these scenarios these low code tools feel like the evolution of excel. How many times did people who couldn't write full on apps throw something together with some excel formulas to do a version of what they needed?

cudgy 4y ago
This was (and may still be) the foundation of tax software: domain experts in each province specifying tax formulas in a spreadsheet with an interpreter that takes those formulas and translates it to code libraries in Java, C, C++, etc.
ok_dad 4y ago
At a previous company, where we developed and built medical devices that were not just a toothbrush, we couldn't install or build any software that did anything that made almost any decisions about the design or production of the devices. In other words, we were stuck using Excel spreadsheets to make decisions then we had to validate the decision and sign off on it as the human who was deciding. Basically, we could build prioritization and tracking "software" out of spreadsheets, but anything other than that, such as the software used to log inspections, had to go through the same process our medical devices went through in order to be used for the design or manufacture of the actual devices. Excel was an absolute life saver there for at least the stuff we could use it for!
- analog31 4y ago
  Yup. The rule of thumb I learned was that at a FDA regulated facility, "anything that touches the product" is regulated just like it's the product. And when the FDA audits a facility, they focus primarily on software.
  - ok_dad 4y ago
    Yep, and for one spreadsheet that prioritized some work, we had to show the FDA that the spreadsheet didn't materially affect the devices we were manufacturing. Basically, this particular one just told us which lots of goods to inspect first, so at worst case it would have just slowed down our line, not affected the device's quality. We still had to take 1 hour to walk some inspectors through our use of it, and why it wouldn't fuck things up. I also started a project to upgrade some software from some old in-house developed stuff to an SAP module (gross, but effective) and it took about 18 months just to make the development and rollout plan, since it was incoming inspection software so it was super important to get right. I left before I saw how long it took to develop, but I think that's the easy part of the whole process.
  - runevault 4y ago
    I don't think I could do FDA software, it sounds so painful. Same with voting machines that are properly regulated (had a CTO at one point who previously did that sort of work and he had stories to tell). Fintech is hard enough.
sokoloff 4y ago
How many times have people who can write code spent many weeks on something that could be done in excel in an afternoon?

cudgy 4y ago

This was (and may still be) the foundation of tax software: domain experts in each province specifying tax formulas in a spreadsheet with an interpreter that takes those formulas and translates it to code libraries in Java, C, C++, etc.

ok_dad 4y ago

At a previous company, where we developed and built medical devices that were not just a toothbrush, we couldn't install or build any software that did anything that made almost any decisions about the design or production of the devices. In other words, we were stuck using Excel spreadsheets to make decisions then we had to validate the decision and sign off on it as the human who was deciding. Basically, we could build prioritization and tracking "software" out of spreadsheets, but anything other than that, such as the software used to log inspections, had to go through the same process our medical devices went through in order to be used for the design or manufacture of the actual devices. Excel was an absolute life saver there for at least the stuff we could use it for!

analog31 4y ago
Yup. The rule of thumb I learned was that at a FDA regulated facility, "anything that touches the product" is regulated just like it's the product. And when the FDA audits a facility, they focus primarily on software.
- ok_dad 4y ago
  Yep, and for one spreadsheet that prioritized some work, we had to show the FDA that the spreadsheet didn't materially affect the devices we were manufacturing. Basically, this particular one just told us which lots of goods to inspect first, so at worst case it would have just slowed down our line, not affected the device's quality. We still had to take 1 hour to walk some inspectors through our use of it, and why it wouldn't fuck things up. I also started a project to upgrade some software from some old in-house developed stuff to an SAP module (gross, but effective) and it took about 18 months just to make the development and rollout plan, since it was incoming inspection software so it was super important to get right. I left before I saw how long it took to develop, but I think that's the easy part of the whole process.
- runevault 4y ago
  I don't think I could do FDA software, it sounds so painful. Same with voting machines that are properly regulated (had a CTO at one point who previously did that sort of work and he had stories to tell). Fintech is hard enough.

sokoloff 4y ago

How many times have people who can write code spent many weeks on something that could be done in excel in an afternoon?