Hey guys, I missed yesterday..what a shame, haha. Just kidding, no shame at all. You’d better suit yourself for a day I’d do it again, I just can’t write if there’s too little progress.
Finalizing the frontend
Today is great day, we have yet another productive talk on the product. Bach has finished a demo on, which, to me, was totally awesome in rocket-fast duration. The design is super sleek, I can hardly imagine TagHub in this superior design with my frontend skills before. AWESOME!!
Another thing that we tapped on is the specs for the “dataset”, which was underspec-ed at the time. The question is “Should dataset be in or outside of a workflow”:
- “In” case: Dataset is import inside the workflow
- “Out” case: The “datasets” will be import at a general data page, outside the home page alongside with workflows and models, and needed to be mounted to a workflow to work
Writing too words about “out” case shows my concealed confession for the case: We decided to go for “Out” case, pursuing a “divide and conquer"paradigm. The dataset only works if it is mounted to a workplace
Finalizing the API
We agreed on this design database:
According to this design, CRUD API should be available on 3 different resources:
- Workflows: represents an analytics notebooks/session
- Datasets: Belongs to a workflow
- Datapoints: belongs to a dataset
I’ll share more about detailed specs tomorrow..
Btw I have manage to finish … 3 apis today despite of some bugs:
The next steps
Following today we started to think there’s ALOT of thing to do:
- Re-implement the draft design with React
- Finish the backend API
- Add more comments to API
Until next time…