If spreadsheets were two-way connected with your core systems like SaaS tools, DBs, Slack, etc then you could represent serious business logic and actions without being a programmer. It is the best platform to build a "no code" tool for non-programmers.
I am curious about one aspect though: Debugging spreadsheets is seriously hard. How do you help customers verify their spreadsheet has the right things they are looking for, avoiding regressions due to a random change by some inexperienced person, etc.?
Also, at what point do you see companies move from spreadsheets to simply hiring developers to do what they want? It seems like beyond a point, spreadsheets can get in the way, and the company has enough resources to hire a team to build custom internal tools.
Good luck with Coefficient!
Spreadsheets have many problems. We are going after their "connectivity" to the rest of the company systems. Hidden errors / debugging is definitely another big problem which we are only tangentially solving. If your data is imported into the sheet through Coefficient (instead of a copy-paste of a downloaded CSV), then you can always trace the lineage/timestamps/etc all the way to source.
As for hiring developers, the truth is that day-to-day business needs grow faster than you can hire devs. So yes, at a certain point companies move some workflows to dev-built tooling or specialized SaaS tools, but their bucket of unhandled workflows still grows larger every day. That is why you can't kill spreadsheets.
The problem starts when whatever frankensheetvbasharepointdb is now an engrained part of a workflow, excelbizdev has disappeared, and 'maintenance' falls to nonexcelwhizz, or perhaps worse, a dev team that lacks much legacy business understanding to figure out why the particular implementation was done, screws up understanding, and creates something worse.
> Does coefficient.io work with MY system?
What databases can you connect to?
Tried fillable PDFs and a bunch of online stuff. None of it worked well. The spreadsheet fields' font sizes were all weird, and even if you manually correct them it would reset on every edit. There were some promising web-based options described as "responsive character sheet", but they tended to fall apart at large text sizes.
Best option? A spreadsheet from Knights of The Braille: https://knightsofthebraille.com/59-2/
Instead of trying to shove an 8.5x11 paper layout into a phone, it just groups stuff into tabs that make more sense anyway. And if you were completely blind I bet it's still easy to navigate with VoiceOver.
We're using Numbers because it's what we both have, but I think Excel should work similarly.
If anyone's reading this from the Google Docs team, please take another look at Sheets' pinch-to-zoom behavior. That was the first place I ended up when I went looking for character sheet spreadsheets online, and it was the first one I ruled out because of how shitty the experience was on mobile.
My last five uses of excel are widely variant in theme:
- validate my taxes make sense
- track Bloodborne platinum trophy progress
- collab with wife on Christmas gift planning
- estimate lumber purchase for project
- collab with coworkers to explore ota data culling options.
2. How does the UX for your R solution to the "DND Character Generation" problem compare to the screenshot from grandparent comment, for users not familiar with either R or Google Sheets?
I mean, I work with laymen that use Excel to encode multimedia content state machines and its not pretty (dreadful bespoke schema with all the caveats you can imagine) but it satisfies their need
I don't usually have that problem. Inserting or deleting rows or columns around the cells doesn't break these formulas. Only changing what type of information a cell contains would. Does this happen often for you?
And you can just name a cell or range if you want to use a variable name to refer to some data in a pivot table or formula.
I mean, this is I reach for Pandas over Excel, but most people would be infinitely more comfortable with spreadsheets than specialized tools. Spreadsheets also happen to be useful enough for almost everybody.
For example, if any of you play D&D online, you might be familiar with dndbeyond's character sheets. They're a fantastic way to onboard new players who might not have the inclination to spend hours with the rule books before they even start playing. It does all the calculations for you and gives you some buttons like "roll athletics" and doesn't let you add more spells than your character can have with their stats.
I recently persuaded some friends to give FATE a try and built analogous push-button character sheets with google sheets [0]. It was quick and simple. With conditional formatting, you highlight bad states (rules say you can't have more of X than Y!). With the script editor, you can add full on buttons for dice rolls and other state changes with whatever logic you want (anything you can code up!). Checkboxes are obvious but super useful. And the transparency of the calculations is helpful for teaching people the system (this stat is "min(A4, B1+C5)").
Without google sheets, it would be a serious endeavor to build a stateful, database backed, live collaborative GUI that can be added to and customized on the fly by my users. With google sheets, it was a quick fun afternoon hack. Excel/google sheets is an amazing piece of technology.
[0] Screenshot of the "app": https://raw.githubusercontent.com/imh/public_images/main/Scr...