by hazelnut-tree on 7/5/23, 9:02 PM with 34 comments
by danielvaughn on 7/6/23, 2:37 AM
My method is meant to expose the business rules. I start out with a single column, and I list every "rule" of the application. So something like "A user cannot export their dashboard without a premium account". Once I have a complete list, I go back and tease out any significant nouns and verbs.
So given the sentence "A user cannot export their dashboard without a premium account", the significant terms are "user", "export", "dashboard", and "premium account".
For each of these terms, I create a separate checkbox column and mark the checkbox if the rule applies to that term.
Once you've done this with enough rules, you'll start to see your domain model form. It exposes all sorts of inconsistencies in your rules and forces you to be very clear about how the application is expected to behave. It also forces you to clarify your language because there will be multiple terms that refer to the same concept, and part of the process is removing these duplications.
It's a great way to get clarity around your product before you start building out the experience.
by topspin on 7/6/23, 4:53 AM
I translated that prototype into JavaScript to implement a somewhat complex web page that had a lot of interrelationships between inputs. This was back when "DHTML" had just become a term of art. It worked perfectly and I'll never forget when, months later in a meeting, a tester was asked if that part of the project was ready; she said "Yeah, he did it. I don't know how he did it but it works."
I keep thinking there is a need for some sort of "next level" spreadsheet software. There are a bunch of uncoordinated ideas in my head for what that would look like, and I haven't seen anything like it emerge yet.
by extr on 7/6/23, 1:07 AM
Similarly, I have known many people who use powerpoint for design work. UI design, interior design, even blueprints/architectural drawings. It just works, everyone already has it.
by mcdonje on 7/6/23, 2:02 AM
To put it another way, if you were to boil this down to a one-liner to a colleague, "investigate before developing" is useful advice and "use spreadsheets" is not.
by Arrath on 7/6/23, 1:36 AM
Compared to the last couple days at work, where a previously existing dynamic(ish) table of contents in a word document is driving me absolutely batty with how it tries and/or fails to format lines as I edit them to reflect further changes to the document. I want to scream and tear my hair out, good god.
by distortionfield on 7/6/23, 5:27 AM
But seriously; I love working in a csv to start and then just parsing it into whatever go or rust or Python I’m working with when it comes times to scale it up further. A lot of MVPs would be better suited as a Google sheet shared between customers or friends.
by dsgnr on 7/5/23, 11:39 PM
by pazimzadeh on 7/5/23, 11:56 PM
by efortis on 7/5/23, 10:23 PM
I look forward to hearing from you
by endisneigh on 7/5/23, 11:36 PM
With 2D things like websites I still find sketching to be the best tool.
Ideally there would be a nice app that lets you sketch and create forks of sketches when certain things are pressed. balsamiq does this but the UX isn’t good enough imho.
by pxc on 7/5/23, 11:14 PM
by mud_dauber on 7/5/23, 10:50 PM
by catchmeifyoucan on 7/5/23, 10:18 PM
I was looking to see if this scraping is a Sheets feature or something, but it's not clear if the author manually visited all of these pages and extracted all the headers.