Chinh (lelouvincx) / Backlog

Created Mon, 25 May 2026 00:00:00 +0000 Modified Mon, 25 May 2026 06:02:25 +0000
1475 Words
page

A. Work

  • Internal

    • TODO Handle multi-currency exchange rates for MRR

    • Current pricing setup

      • Zoho’s base currency = SGD. Plans are priced in SGD, exchange rate is hardcoded in Zoho (example, 1 EUR = 1.4 SGD).
      • Plans are created in Zoho Billing with prices in SGD (base currency). Zoho doesn’t allow creating products in EUR/USD directly.
      • A manual exchange rate is set in Zoho (e.g., 1 EUR = 1.4 SGD).
        • Why? To prevent customers’ purchase amount can potentially fluctuate over time, the team does not use live rate in Zoho.
        • Customers see stable local currency prices on their subscription.
        • This is updated periodically (~yearly) to stay close to market rates.
      • The same plans are mirrored in Holistics App’s Tenant Admin.

    • Customer payment flow:

      • Customer sees a clean, stable price in their local currency on the billing page based on public.tenant_subscriptions, derived from Zoho source of truth for pricing.
      • Customer clicks pay => redirect to a Hosted Payment Page => charged the displayed amount in their currency.
      • Holistics receives payments in the customer’s currency, 3 separate balances (SGD, EUR, USD), conversion to SGD happens at will.

    • MRR recording (Zoho):

      • Zoho records MRR based on the hardcoded SGD plan price at plan creation time (e.g., SGD 1400).
      • Existing customers stay on their original exchange rate even if rates are updated later.

    • Problem:

  • {{embed ((69b21fb9-6f3d-4c38-8483-892aa9d89cac))}}

  • WAITING Fix excluding internal testing Zoho accounts

    • Close the lingering loop here. Decision to backlog this task. Will do after big projects such as MRR and exchange rate.

  • TODO Upgrade dbt-core of repo dbt to the same version as prefect (compatible)

  • WAITING Create an agent skill for fixing data pipelines (currently dbt) for #data-ops-bot

    • This may not a good timing for this since anh Triet’s direction is to let Thuan handle data-ops-bot to train him with our data system.
    • Maybe next 3-6 months when he’s good with the system, we can get back to this

  • TODO Check if it’s feasible to load tenant info from BigQuery to Clickhouse (OpenAI tracking request)

  • TODO DAT-504

  • TODO Optimizing internal dbt CI with defer

  • Presales

    • TODO Showbie loss synthesis

  • TODO Onboarding call with Wamly

    • WAITING. Farren cancelled Apr 29 call (urgent matter), now on 10-day paternal leave since May 1. Chukwudi will reach out in ~2 weeks. No action this week — re-pick up around May 11–15.

  • WAITING Polish document embedding because there are frictions for prospects/customers to set up embed portal, while there are more and more leads coming to us for embedding solution

    • Context:
      • I built a demo app at https://holistics-embed-demo.pages.dev that demonstrates Embed Portal, multi-user Row-Level Permission, Ask AI, and a custom embed URL renderer.
      • Repo: https://github.com/holistics/holistics-embed-demo
      • The app is already serving presales (presenting in onboarding calls) this week: Jonas Chorum on dynamic data source demo with per-hotel RLP, Showbie on embed portal/single dashboard.
      • Recent technical calls (Basata, Superb, Showbie, Innerspace, Jonas Chorum) need embedded analytics:
        • For Basata, I shared a playbook on embed portal with different logic workflow. Document link.
        • For Superb, I guided him step-by-step setting up embed portal with RLP. Call link.
        • For Innerspace, I and Marcus shared a playbook on app/embed 2 way communication. Document link. Call link.
      • We already have a embed demo site at https://hooli.getholistics.com, if creating one more site, that might be a friction in distinguishing which site to pick. We need to make it really clear to internal team/customers, otherwise, consider unifying them.
    • With this foundation, I think we can improve, output a kind of playbook or a highly customized industrial data for each specific customer before the call.
    • Anh Triet’s comments:
      • Who should maintain? Data/presales or product?
      • What to maintain? The site? The data? Who own what?
    • Will share with anh Huy on tomorrow presales sync for advice.
    • I think no need to do it for now. Maybe I can continue customizing this page for several next prospects, gather more data points, wait for a good timing like UX revamp project release then talk about this.
    • {{embed ((69dc6bac-43c5-47f8-b0eb-c27caa3386ea))}}
    • Advice from Ampcode:
      • Frame it as formalizing something that’s already working, not proposing something new. “here is what’s already happening, let’s make it official.”
    • I should find a stronger evidence rather than my app looks prettier (not strong enough). Frame it as a unified toolbox.
    • A unified toolbox that serves:
      • Sales/Presales team for demoing.
      • Prospects/Customers who want to try on their own.
    • Streamline prospects’ embed developing experience to end-to-end smoothest.

  • TODO Read Modeling Patterns

  • TODO Watch the onboarding call with Taxdome

  • TODO Learn embedded analytics use case, prevent hiccup like Taxdome

  • TODO Summarize the Mawave use case and tell dbx team about how to quickly collaborate on a dataset schema

  • Duty Support

    • TODO Check with Product on displaying level of details on hovering a metric Link

  • Docs

    • TODO Add demo video for local development docs

  • Draft a scenario of how I want the development experience would look like, then discuss with anh Huy Vu/Dat for advice and progress.

  • https://omni.co/blog/announcing-omnis-modeling-agent

  • DONE on Khai To (PM lead, squad modeling) to release the 2-way sync tool in holistics CLI. Demo video should land after that ships so we can lead with the new flow.

  • TODO Feedback - auto-export dashboard PNG

    • Ampcode
    • TL;DR: PNG export already works in the canvas dashboard UI. Exposing it via holistics CLI (or API) would unlock a dashboard-as-code review flow — auto-attach a PNG preview to the GitHub PR whenever a canvas dashboard changes. Visual diffing for dashboards, similar to chromatic for storybook.
    • What already exists
      • Canvas dashboard UI: Export dashboard → PNG/PDF (per docs/delivery/export-data and the canvas-vs-quick comparison in dashboards/quick-dashboards).
      • Public API (docs.holistics.io/api): only CSV/Excel via POST /dashboard_widgets/{id}/submit_export → poll /jobs/{id} → GET /exports/download. No PNG export endpoint documented.
      • holistics CLI: pull/push for AML, but no dashboard-render command (waiting on your 2-way sync release).
    • The ask — pick whichever fits the squad’s roadmap:
      • (preferred) holistics dashboard export <id> --format png [--out path] — fits squad modeling’s CLI surface; lets us wire it into CI cleanly.
      • or: extend submit_export to accept format=png, returning the PNG via the existing job/download flow. Same pattern, no new endpoint shape.
    • Why this matters now (signals from this week)
      • BuyCo asked vision questions about AMQL/AQL as canonical spec → visual artifacts of a dashboard-as-code flow strengthen that story.
      • External signal: ggsql alpha, Shaper, benn.substack — How do you make a chart. Markdown/PR-embeddable charts are a recurring pattern.
      • Internal: dbdocs CI gap (raised in dbt#860 review) shows we already feel the lack of pre-merge visual validation on AML changes.
      • Concrete payoff: PR reviewer sees a thumbnail diff inline; AML refactors (like the W18 Calendly migration on rep_calls) get a visual sanity check before merge.
      • LLM-friendly bonus: a stable PNG URL per dashboard means agents can read renders, not just JSON.
    • Happy to pair — once a CLI flag or API param exists, I can prototype the GitHub Action side (canvas-dashboard-changed → render → comment-with-image on PR) and dogfood it on internal-aml-project. Not asking the squad to own the CI piece — just the render primitive.
    • Open question for you: is the UI export already a server-side render (headless browser job) we could trigger, or is it client-side canvas? If the latter, the CLI path is heavier than I’m assuming and worth a separate conversation before scoping.
    • References to drop in the message
      • This journal note ([[2026-05-04]])
      • W18 weekly report — Learning & Notes section ([[Weekly Report - 2026-W18]])
      • Original idea capture ([[2026-04-27]])

  • TODO Document Tricia’s use case on A/B comparison

  • TODO Think about a roadmap or treemap to navigate the reader with our docs better

  • TODO Probably need to find a way for LLM to read images from the md document

  • Misc

  • B. Personal

    • TODO Review and update [[Personal Context]]

  • ((69b68520-d834-4332-9be3-0d5cef9f9735))

  • TODO The bigquery agent skill often gets trouble mapping logical (dbt) and physical table names (BigQuery). Improvement: use dynamic mapping from INFORMATION_SCHEMA (excluding dev_* in prod)

  • TODO Learn an overview about Data Modeling

  • TODO Migrate from Obsidian

    • DONE Migrate journal notes
    • TODO Migrate other notes

  • [[Personal Finance Manager App]]

  • TODO Think about studying Master Degree

  • TODO New blog UI?

  • TODO Self-host readeck?

    • Monetize self-hosted readeck?
      • Benefits
        • Link Rot Insurance: The archived articles are yours forever. You can download your own data anytime. And if you want the link to be available in public internet you go with the subscription plan, which uses my domain name.
          • Imagine you have a mini Internet Archive.
        • Privacy: You own your data. I don’t sell them to Ad services. You can export your data anytime.
        • E-reader Sync: One click send-to-kindle/kobo.
        • Zalo/Telegram Chatbot: Immediately save a link by sending it to my Zalo/Telegram chatbot. Just like using “Cloud của tôi”, but you own that.
    • Alternative: karakeep

  • Teaching

    • {{embed ((69abeee3-b624-4e96-bd98-696afff2a17b))}}
    • TODO Figure out how to teach shifting from row-based thinking to set-based thinking

  • TODO Checkout pudding.cool’s resources

  • TODO Research visualization resources

  • Freetime

    • TODO Read articles from duckdb

  • TODO Read levels of detail in communication