4. 1. You’ve selected an idea.
2. You have a product narrative.
3. You have experimented with moving parts
and reasonably know how to build the alpha
product.
8. A general format for writing
specs is this.
[Customer Segment]
needs [feature/improvement]
so that
[a business need].
9. Example:
An SV.CO Founder needs to
see a tour on his first visit to
the dashboard so that she
can orient herself faster and
jump right into completing
targets.
14. Spec in human-readable form:
An SV.CO Founder needs to
see a tour on his first visit to
the dashboard so that she
can orient herself faster and
jump right into completing
targets.
24. 1. You’ve selected an idea.
2. You have a product narrative.
3. You have experimented with moving parts
and reasonably know how to build the alpha
product.
26. Basic Flow:
1. Customer sees a search bar
as the primary interface of
interacting with the product.
2. He types in queries in the
search bar and instantly sees
results.
3. The results are in tabular form
in the alpha version.
27. Types of Queries:
1. The customer cannot type
in anything like Google. This
is not a general search
engine.
2. Instead, he has a simple
syntax to learn to write
queries.
28. Examples of Queries:
1. Let’s assume 1 table:
students table with 3 fields:
name, location, marks
30. Example of Queries:
3. “students count by
location”
SELECT LOCATION,
COUNT(*) FROM
STUDENTS GROUP BY
LOCATION
31. Example of Queries:
3. “students sum of total
marks by location”
SELECT LOCATION,
SUM(TOTAL_MARKS) FROM
STUDENTS GROUP BY
LOCATION
32. I’m ignoring a lot of the other
particulars here: like
login/signup, connecting a
database schema.
33. I’ve also experimented with
technology moving parts and
reasonably know how to solve
this.
1. Connect to DB.
2. Parse the query &
translate to SQL.
4. Execute.
34. Note: before we proceed
further, this is an incomplete
solution.
35. Focus on step 2.
1. Connect to DB.
2. Parse the query &
translate to SQL.
4. Execute.