Day 16/66 → Wrap up of this week: list of metrics, design system on @NotionHQ , next steps for our content engine, if you want to learn more and be part of the first users, let me know in the comment 🙏
Why do you need a design system for your graphs? and how we built one for social media aggregator project today.👇
A design system is a complete set of standards intended to manage design at scale using reusable components and patterns. #buildinpublic#66daysofdata#design
Aggregation and analysis of social media content is not an easy job. I see 3 main problems: 🔴 access to the platforms APIs 🔴 refining the data your get for analysis 🔴 focus on KPI's that measure value, not vanity!
😅 Our principles at naas.ai : - Build a product to fix your problem - Opensource it, make a freemium cloud version - Let people use and contribute to it - Organise chaos to focus on a valuable niche, then expand.
⏰ When you are “scheduling” notebooks in Naas, this is what happens:
1) A copy of the notebook you are working on is sent to the production folder. 2) A “cron” task is registered in the Naas manager to know when to run it.
Then, the whole notebook will be executed. #naaslife
Do you know Cassie Kozyrkov (aka @quaesita) ? Cassie is Head of Decision Intelligence of Google. Her work keeps inspiring us in the building of naas.ai
Unbelievable. Today, I’m at Netflix HQ. Presenting @JupyterNaas
I have been invited for lunch by a Top Executive and will follow by a meeting with the person in charge of the Notebook Infrastructure - the Data Platform Edge.
At @JupyterNaas we do low-code formulas: if a notebook has too much code that can be reused, we create an abstraction to it in a #python package. Obj: make things as simple as an excel formula.