3 ms·
I want to see in the first 5 minutes: 1) a simple explanation of what it is - don't assume I know anything about the problem 2) why this solution is better than
by brodouevencode 3y ago
I want to see in the first 5 minutes: 1) a simple explanation of what it is - don't assume I know anything about the problem 2) why this solution is better than the others/what unique problem it is solving 3) a quick demo. As an engineer then I want to see the architecture from a high level and how to most easily implement into my shop. Save the code deep dives for last unless there's some really unique and interesting things going on under the hood. Underpromise and overdeliver.
- lovasoa 3y agoInteresting. Since the tool I'm presenting is something that lets you write websites in SQL, "code deep dives" referred more to code that you can write as a user of the tool than things going on "under the hood". I wanted to show small SQL queries and the web pages they generate. Do you think it's something I should keep for the end / skip ?
- brodouevencode 3y agoMaybe our definitions of "deep dives" is different. To demonstrate how the product works, using code, I would be all for especially since this is a developer-centric tool. I take deep dives to mean how the product is built.