And the big #nocode benefit: speed! Sure I might need something more robust down the line - but the ROI from just piecing together a few powerful building blocks is 💯. I can always sprinkle on a little code to get more mileage out of this setup.
This was just a quick example demonstrating a tangible #nocode use case - hope it helps someone! I'm also writing a longer-form article on designing product-oriented customer feedback systems from first principles. ✍️ //
2
18
Complacency is one of the biggest threats to covid green zones. “Think of danger in times of safety” is the idiom du jour here
Jeremy retweeted
Replying to @cansar @RoamResearch
While there are benefits to a standard reading interface, you lose lots of the character and cues of a web *site*. Web pages are more than just content - they‘re designed locations that you *visit*. There’s value in digesting them in context, imo.
The Eloquent tool is available to install! Capture ideas in-context with:
• On-page highlighting
• Nested bullets
• /snippets
• [[braces]] and #tag syntax
Quick capture is a hotkey away. Bonus hotkey sends your highlights/links to @RoamResearch
All this twitter feedback is dope 🙂. Please do try to use the form for reporting issues though! It’s structured + goes to an Airtable so I can organize/automate 🙏
1
14
[An Eloquent Bug Story] A small self-reminder on how the blindspots of builders manifest in the products they create: wrote a /snippet expansion feature from scratch and V1 didn't work for some non-US keyboard layouts 😔 1/
Anyway re: addressing blindspots: you can try to come up w/ every test case (unrealistic) or expand the size/diversity of test users (a bit better). Obviously best: diverse teams w/ a range of views built in to the building process. 6/

