Page on lelouvincx's second brain

[dblineage] Gathering User Data

Mon, 25 May 2026 00:00:00 +0000

https://www.reddit.com/r/dataengineering/comments/1hq9dwl/complexity_of_data_transformations_and_lineage
- If you’re working with data as a primary focus, part of the job (a big one) is documenting what you’re doing and validating what you touch before shipping it.
- I’m confident that my systems are and remain correct because I confirm the state of things before starting new work and document what I did, it adds like an hour to a project.
https://www.reddit.com/r/dataengineering/comments/10usa5i/looking_for_an_opensource_data_lineage_app_where/
- Context: company has been documenting all its data objects manually and has a large csv explicitly showing each data object and its predescessor/s. These aren’t just the standard database/workflow/dashboard objects; these include things like power automate scripts. I’m just looking for a good way to show everything in a map, visualize them, and navigate through their connections properly) At this point, I’ll even be happy with a pure visualization engine, like for instance if I can repurpose kedro-viz or dbt’s lineage visualizer so that it can take a csv or json of object relationships as an input. Or even a custom power BI visualization or python graph frontend would be fine, but I can’t seem to see one that works. I’d also be happy if any of the aforementioned lineage tools I mentioned above have this functionality and I just missed it.
https://www.reddit.com/r/dataengineering/comments/1ba4g7v/how_to_diagram_sql_queries/
- Love dbdiagram :) I’m also using dbdocs as a light-weight data catalog instead of plain dbt docs. While I do find dbt docs useful for data lineage, I’ve discovered that I can achieve the same functionality through my dbt core setup using the dbt Power User VSCode extension. And dbdocs fill in the gaps: ERD, table metadata, easy to deploy, shareable,… almost cover 90% of my needs
  - => implying dbdocs isn’t the lineage surface
https://www.reddit.com/r/SQL/comments/nxbtxb/tools_to_draw_data_lineage/
- Good for data models and showing direct relationships between tables, but it doesn’t show data flows. When you visualize data flows, you want to see data from which table ends up where, it’s different than “Column X is an FK to Column Y”
- Will dbdiagram be possible to show how several columns are being transformed to one column?
https://www.reddit.com/r/dataengineering/comments/1kyi6hx/what_do_you_use_for_lineage_and_why
- i’ve used a bunch of these. real talk: data lineage is overrated at early stages & often overcomplicated. when ur team is < 10, physical lineage diagrams on a whiteboard + good dbt docs get you 80% there. we started with DBT lineage for our first year which did the job, then built custom lineage in Preswald when we needed more flexibility (needed to include non-dbt systems). the problem with most enterprise lineage tools is they force you into their ecosystem - great for huge teams with dedicated resources, massive overkill for startups. your investment should match your problems - if ur just trying to debug why a dashboard broke, dbt docs are prob fine. if ur trying to comply with SOX, yea get OpenLineage or something heavy duty.
- Hey , i also want an open source tool for automated data lineage for my company which we can integrate in our product which is a data security product . I am going through openmetadata , but finding it difficult . Can you suggest any lightweight and easy to use tool which is open source ? and which can be used for automated lineage . I went through many tools online like DataHub , Collate , Informatica , etc . Most sites and GPTs suggested to use OpenMetaData. WHat is your recommendation .
https://www.reddit.com/r/dataengineering/comments/1ijr4jd/what_data_lineage_tools_do_you_use_and_what_makes/
- I’ve been working with OpenLineage lately and I like it a lot. It’s an open standard for collecting lineage data. Great community and they are very open to PRs and new features. Not a ton of integrations right now, but they have most of the big ones.
- I’ve been looking closely at DataHub for awhile now, and I think I’ll be using in coming projects. It’s an open-source tool with a managed version by Acryl. It does a bit more than just data lineage too, so may be overkill for what you’re after.
What are the short comes of current data lineage tools?
- Do the current lineage tools address data audit needs?
- https://www.reddit.com/r/dataengineering/comments/1gjzsu7/what_are_the_short_comes_of_current_data_lineage/
- The field is pretty crowded and most of the data platforms are already providing lineage out of the box.
- Make it our own, with thst said 90% of our platform is custom pyspark code running on aws, databriks or azure. No comercial offer does cover that , but they could :). We hocked the backend into our internal llm bot, so not user can just slack into it. No commercial would letvyou do that, they would sell it to you as a addon. Plus we are global brand and we shared our code with other sister brands and we all exchange internal features.
- Bugs everywhere.
- We use Collibra for snowflake lineage. Coverage of sql syntax is ok but it’s very buggy and hard to manage. No proper APIs for lineage means manual management. Other issue is it works on scraping the query logs in snowflake for a period of time so it can produce confusing results after code changes.
Is data lineage one of the most underrated thing in DE?
- https://www.reddit.com/r/dataengineering/comments/1g8k2h5/is_data_lineage_one_of_the_most_underrated_thing/
- I worked for multiple companies as a DE and zero of them applied anything related to data lineage. Whenever my team mentions it would be important to do this it gets ignored.
- If they don’t do documentation, I wouldn’t even expect have of them to know what data lineage even is.
- Data lineage is one of those things no one thinks they need… until they do. Like when you are debugging why a multi-system process or ETL isn’t working. The question of, “where did this data come from” comes up and now you are wasting time trying to find that out. It really sucks if it passes through multiple systems or multiple formats. (ODBC and JDBC are really sneaky like that.) Be the person that documents their stuff and allocate time for it. It will be an uphill battle because documentation is one of the first things thrown overboard when the inevitable money/time crunch shows up.
- This question keeps me up at night, since I’m in the process of building a POC database engine that has cell-level data lineage, forwards and backwards. I’ve been in data over 20 years. Most in DE supporting analytics. I’ve NEVER been somewhere that had robust data lineage. It drove me nuts enough to spend years dreaming up a robust solution. Why don’t places care? As someone who wants to open source something and launch a business around it, it drives me nuts. Am I crazy for finding data lineage fundamental? I don’t think the current gen of tools are there. I don’t think OpenLineage is good enough. It’s progress. (I guess that’s why I’m building my own.) I haven’t used Dagster but anything that doesn’t preserve transaction logs in a way that syncs up with time travel in a consistent way, to me, just isn’t good enough. The major downside of my approach is you only get lineage inside my engine. That’s probably a non-starter for many places, especially those big enough to be early adopters. IDK.
https://www.reddit.com/r/dataengineering/comments/1g3e20y/data_lineage/
- How do you all like to track dataset lineages? Dependencies between tables, sources/sinks per job, something like Kafka to a Spark written Iceberg table joined with another table to eventually landing in Snowflake… etc?
https://www.reddit.com/r/dataengineering/comments/1cvmerf/data_lineage_tools/
- OP is describing the exact use case for OpenLineage, but it’s hard to estimate how complete their lineage graph would be without knowing more about their tooling. OL will give you column lineage for Spark and Airflow jobs. Dbt is supported, as well.
- There are open source catalogs, like DataHub, but data lineage in it is extremely limited. So they do exist, but most likely will not suit your needs. Then you have paid products like Informaticas data catalog, which is out of scope. They support more or less everything.
- Use SQLMesh, it has lineage, diffs, etc.
- I was pushing for OpenMetadata at my last job, lineage being one of the selling points. I never got it deployed.
https://www.reddit.com/r/dataengineering/comments/1iddujm/data_lineage_and_quality_tool/
- I’m exploring OpenMetadata for data quality, governance, and lineage. While I’m not necessarily opposed to containerized deployments, I’m prioritizing ease of use, especially when it comes to automated data lineage and quality testing. I’m looking for alternative tools that might be more convenient to work with in these specific areas. Are there any tools that are considered “better” than OpenMetadata in terms of simplifying the process of setting up and managing automated data lineage and quality tests? Any recommendations would be greatly appreciated!
- SQLMesh is a solid tool for managing transformations, plus you get column level lineage of your models as a part of the open source offering.

[Internal] Customers' MRR (Exchange Rate)

Mon, 25 May 2026 00:00:00 +0000

Goal
- Resolve discrepancies between MRR (Monthly Recurring Revenue) numbers on bi.holistics.io and Zoho Billing, and establish a single source of truth for customer MRR.
- Stakeholders: Data Team, RevOps (Quinn, Arden, Vincent), Finance (Sriram).
- Why it matters: MRR is the core metric for revenue planning (see [[Lead Funnel by Sales Motion]]’s $330K target). If the number is wrong, every downstream decision — pricing analysis, churn measurement, forecasting — is wrong.
- Decision-making questions:
  - Why does MRR on bi.holistics.io differ from Zoho Billing?
  - Which exchange rate methodology should we use for multi-currency subscriptions?
  - How do we handle customers with multiple tenants or multi-region setups?
MRR Definition
- MRR = sum of all active subscriptions’ monthly recurring revenue.
- Zoho’s base currency: Singapore Dollar (SGD).
- Per-subscription calculation: subscription.mrr / subscription.exchange_rate
- Customer = a HubSpot Company (one company can have multiple Holistics tenants and multiple Zoho subscriptions).
- Primary Tenant: for customers with multi-region or multi-tenant setups, the pipeline must select one primary tenant. This is the core identity resolution challenge.

Data Architecture

flowchart TD
 subgraph Sources["Data Sources"]
 Holistics["Holistics Backend DB\n(Tenants, Users, Trial Submissions)"]
 Zoho["Zoho Billing\n(Subscriptions, Invoices, Exchange Rates)"]
 HubSpot["HubSpot CRM\n(Companies)"]
 end

 subgraph Pipeline["dbt Pipeline"]
 stg_tenants["stg_holistics__tenants"]
 stg_users["stg_holistics__users"]
 stg_trials["stg_holistics__trial_submissions"]
 stg_zoho["stg_zoho__subscriptions"]
 stg_hs["stg_hubspot__companies"]

 domain["Domain Mapping\n(tenant → domain_name)"]
 customer_id["itg_mappings__customer_identities\n(Holistics ↔ Zoho ↔ HubSpot)"]
 dim_customer["dim_customers\n(primary tenant selection)"]
 fct_mrr["fct_mrr\n(MRR calculation)"]
 end

 subgraph Issues["🔴 Known Issues (9 problems)"]
 I1["1.1/1.2: Exchange Rate Errors\n(static rate, multi-step conversion)"]
 I2["2.1-2.4: Wrong Tenant↔Company Mapping\n(region bug, domain mismatch,\nduplicates, multi-domain)"]
 I3["3.1/3.2: Wrong Tenant↔Zoho Mapping\n(manual errors, multi-tenant sub)"]
 I4["4: Active but Unpaid Customers\n(Zoho subscription logic bug)"]
 end

 subgraph Output["Reports"]
 bi_h["bi.holistics.io\nMRR Overview Dashboard"]
 monitor["Customer Identity\nMonitoring Dashboard"]
 end

 Holistics --> stg_tenants & stg_users & stg_trials
 Zoho --> stg_zoho
 HubSpot --> stg_hs

 stg_tenants & stg_users & stg_trials --> domain
 domain --> customer_id
 stg_hs --> customer_id
 stg_zoho --> customer_id
 customer_id --> dim_customer
 dim_customer --> fct_mrr
 fct_mrr --> bi_h
 customer_id --> monitor

 I1 -.->|affects| fct_mrr
 I2 -.->|affects| customer_id
 I3 -.->|affects| customer_id
 I4 -.->|affects| stg_zoho

Data Sources
- HubSpot CRM: Companies.
- Holistics Backend DB: Tenants, Users, Trial Submissions.
- Zoho Billing: Zoho Customers, Subscriptions, Payments, Invoices, Exchange Rates.
dbt Pipeline Flow
- Staging: stg_holistics__tenants, stg_holistics__users, stg_zoho__subscriptions, stg_hubspot__companies
- Mapping: itg_mappings__customer_identities (Holistics ↔ Zoho ↔ HubSpot)
- Dimensions: dim_customers (primary tenant selection logic)
- Facts: fct_mrr (final MRR calculation)
Identity Resolution
- Currently relies on domain_name (extracted from tenant uname or email). This is fragile.
- Proposed long-term fix: a canonical customer_skey shared across HubSpot and Zoho.
ER Diagram
- dbdiagram.io — Concepts
Key Datasets & Dashboards
- Datasets:
  - DTS 100: Customer and Revenue
- Dashboards:
  - MRR Overview: https://bi.holistics.io/dashboards/v4/28300-0-mrr-overview
  - Customer Identity Monitoring: https://bi.holistics.io/dashboards/v4/45480-customer-identity-monitoring
  - MRR Bucket Breakdown: https://bi.holistics.io/dashboards/v4/41188-adhoc-mrr-bucket-breakdown

Exchange Rate Decision
- Base currency: SGD (Zoho uses only 1).
- Reporting currency: USD (agreed upon, >40% of revenue is in USD, USD is more recognizable and comparable).
- Problem: pipeline previously used static rates; Zoho uses per-transaction rates set at plan creation time.
- Agreed approach (Option 2): use live rates (e.g., Google Finance / ECB) — specifically the current/today’s rate for a “what is it worth now” view.
- Caveat: requires careful handling to avoid FX noise in historical growth metrics.

Identified Problems & Root Causes

Category	Problem	Root Cause
Exchange Rate	1.1/1.2: Inaccuracies	Pipeline uses static rates; Zoho uses per-transaction rates set at plan creation
HubSpot Mapping	2.1–2.4: Mapping Bugs	Missing regions, domain mismatches (e.g., `raft.ai` vs `vector.ai`), duplicate HubSpot companies
Zoho Mapping	3.1/3.2: Link Errors	Manual errors and system inability to handle multi-tenant subscriptions
Subscription Logic	4: Unpaid Actives	Zoho fails to re-activate tenants after past-due payments are settled

Edge Cases
- Multi-tenant customers: Datacubed — one Zoho account for two tenants.
- Multi-region conflicts: Kognity — SG database shows expired trial while US database shows active paying status.
- Domain mismatches: Vector AI — HubSpot uses vector.ai, app uses raft.ai.
Technical Fixes
- PR #812: Fixed missing regions in manual mapping.
- PR #852: Implemented hard-coded patches for edge cases:
  - map_holistics_zoho.csv: maps specific tenants (e.g., Datacubed) to shared Zoho accounts.
  - partner_programs.csv: excludes freemium plan IDs from MRR.
  - dom_holistics__internal_tenants.sql: filters out internal Holistics testing tenants.
Progress
- DONE Identify root causes of MRR discrepancies
- DONE Agree on exchange rate methodology (Option 2 — live rates)
- DONE Fix missing regions in manual mapping (PR #812)
- DONE Implement hard-coded patches for edge cases (PR #852)
- DONE Set up Customer Identity Monitoring dashboard
- TODO Replace static exchange rates with live rate ingestion — DAT-576 (for quick win)
- TODO Implement canonical customer_skey for long-term identity resolution
- TODO Handle Zoho re-activation bug for past-due subscriptions
References
- 1-Ampcode (DE-187 investigation) 2-Notion (Data alignment) 3-ER Diagram 4-Dashboard MRR Overview 5-Dashboard Identity Monitoring 6-Linear

[Internal] Identity Resolution

Mon, 25 May 2026 00:00:00 +0000

TOGA case:

https://media.secondbrain.lelouvincx.com/2026/05/b9dc56ec029f34bc9c15156003755c85.png
Ampcode
2 HubSpot companies map to one tenant (SG-2163)

[{'hubspot_company_id': 4018874875, 'all_domain_names': [togltechnology.com, togalimited.com]}, {'hubspot_company_id': 10207389977, 'all_domain_names': [togalimited.com]}]

1-on-1 Planning - 2026-04-13

Mon, 25 May 2026 00:00:00 +0000

Plan for Next 1-on-1

Key topics to discuss with manager

MRR project transfer — status update after handoff from anh Hieu (due Apr 15). Any open questions or risks from the transfer.
Presales capacity & portfolio review — currently active on 5+ customer accounts (Showbie, Jonas Chorum, Basata, Innerspace, Superbexperience). Request alignment on which accounts to prioritize vs. hand off. Discuss whether the embed demo app should become an official presales tool.

1-on-1 Planning - 2026-Apr 13, 2026 – May 20, 2026

Mon, 25 May 2026 00:00:00 +0000

Plan for Next 1-on-1 (covering Apr 13 – May 20, 2026)

Meeting context: anh Hieu left this period; presales surged to dominant project; DAT-576 MRR exchange rate is 5-week carry-over. Two backlog drops on the table. Bring 3 prioritization options for DAT-576 — this is a prioritization ask, not a scheduling ask.

P1 – Must Discuss
- Internal
  - DAT-576 MRR exchange rate — re-scope or re-assign. 5-week carry-over. Anh Hieu left → context lost → restart. Bring 3 options: (a) re-scope to 1-week-effort presales-compatible version, (b) hand off to teammate whose week isn’t presales-loaded, (c) formally de-prioritize until presales calms post-BuyCo close. Decision needed in this meeting — do not commit a 6th week of “Mon AM blocks.” Linear DAT-576.
  - Formally drop DAT-524 Fix excluding internal Zoho test accounts — 14-week carry-over. Fix scope is trivial — add const_zoho_internal_customers filter to stg_zoho__events (other Zoho staging models already apply it). Arden already confirmed Quinn US test + Holistics SGD test accounts are the missing ones. Owner: nobody since W7. Decision: do it now (~30 min) or drop formally. Linear DAT-524.
- Presales / Career
  - Career lane check-in — IC engineering vs solutions/presales hybrid vs tech lead. Performance review feedback (Mar) validated the hybrid direction. Anh Thanh (chief engineer) approaching me re: AI-AQL = solutions-engineering signal. BuyCo onboarding 4 solo = trust cashed. Want to confirm the current lane is intentional, not drift.
P2 – Should Discuss
- Presales
  - Showbie loss synthesis — first lost deal. Lost to Omni (HubSpot Closed Lost recorded, Erin reply). Erin cited “overall functionality within the tool” before message truncated. Action: re-pull full Slack thread, then chase Harsha for personal feedback (apply The Mom Test — ask about specific past PoC moments, not abstract pain points). Share 1-page learning note focused on Looker-migration moat + security risk perception. Owe this for the team’s next deal.
  - BuyCo onboarding 4 follow-ups owed by me (from May 19 debrief): share PBI migration documentation publicly, publish migration skill as customer-facing package, send HTML action button samples to Rodolphe. Decision timeline tight — Xairo + Luc evaluating next week, GoodData competing.
  - Power BI playbook → “presales-owned reusable artifact” template? BuyCo onboarding 4 used conceptual-differences.md + migration-overview.md. Reusable. Should it become the template for future migration-flavored deals (Tableau, Looker, Sigma)?
  - Presales team shared status board — me + anh Dong + Chukwudi + Mario have no shared customer-status surface. Context scattered across Slack threads + individual notes. Propose Notion DB or Linear project.
- Internal
  - Heuristics upstream to team docs — dbt deprecation 3-phase rule should land in holistics/dbt contributing guide. Customer-comms recipe pattern should land in presales/CS onboarding doc. Ask: is this welcome, or noise?
  - Backlog drop as standing 1-on-1 agenda item — “what’s the oldest item in my backlog, and should it still be there?” Process suggestion.
P3 – Nice to Discuss
- Personal
  - Health Rules + Principles pages — converted W17 sick week + W20 badminton signal into rules. Sharing the pattern in case useful for team retros.
  - Personal Finance RFC-0002 — used Personal Finance app to make data-driven house-move decision. Side-project ROI signal worth sharing.
- AI tooling
  - Harness Engineering (Mitchell Hashimoto) — built amp plugin for Holistics MCP error logging. Plan: monthly harness audit. Worth doing as team practice?

Decision-class items (manager input required)

Item	Question	Default if no decision
DAT-576 MRR	Re-scope, hand off, or de-prioritize?	Continue slipping — bad outcome
DAT-524 Zoho	Drop or assign?	Drop
Career lane	Confirm hybrid direction?	Continue current pattern
Heuristics upstream	Welcome or noise?	Keep personal

Focus topics if time permits
- Mon: DAT-576 + DAT-524 (decision-class items first)
- Career lane check-in (10 min)
- Showbie synthesis sharing (5 min)
- Heuristics upstream (5 min)
- Personal: Health Rules pattern (skip if rushed)

Carry-over watch (since last 1-on-1)

Item	Since	Weeks	Action
DAT-576 MRR exchange rate	W16 (Apr 13)	5	Escalate as prioritization question
DAT-524 exclude internal Zoho accounts	W7 (Feb 9)	14	Drop formally
Showbie loss synthesis	W19 (May 4)	2	Owed — close this week
H1 self-reflection + CV refresh	W19 (May 4)	2	Lock May 23–24
Wamly onboarding	W18 (Apr 27)	3	Customer-side block — Chukwudi re-engaging

Metrics to bring (period Apr 13 – May 20)
- Customer interactions: 8+ across BuyCo, Jonas Chorum, Basata, Bicycle Transit, Enhance Fitness, PatientsKnowBest, Showbie, Wamly
- PRs merged: Calendly dbt #853, internal-aml-project #78, dbt #854, dbt #858, prefect #400, dbt #860, dbt #864, dbt #867, internal-aml-project #77
- Carry-overs resolved: DAT-560 (Lead Funnel by Sales Motion, 5w), DAT-555 (fct_job_queue_performance, 4w), DAT-283 (Calendly, 8w)
- Carry-overs lingering: DAT-576 (5w), DAT-524 (14w), demo video for local dev (5w, now unblocked)
- New artifacts: [[Health Rules]], [[Principles]], Power BI playbook (conceptual-differences.md + migration-overview.md), holistics-embed-demo continuing
- Onboarding calls led: Jonas Chorum #2, BuyCo #4 (solo)
- Lost: Showbie → Omni

Accessories That Make My Life Better

Mon, 25 May 2026 00:00:00 +0000

Gears

Keyboard: MelGeek O2 or Nuphy Air75
Laptop: Macbook
Mouse: Attach Shark X3
Headphone: SkullCandy Hesh ANC
Reading & Note: Kindle Scribe 2022
Softwares
- Alcove
- Better Display
- AlDente
- CleanShot X
- Youtube Premium (+ Youtube Music)
- Gemini
Misc
- Sleep Fold

Add2Cart

Mon, 25 May 2026 00:00:00 +0000

Noticeable calls

https://copilot.clari.com/call/11644b50-8a66-4c36-a91b-e0ed635d3211
Metric Catalogue
- Base measures
  - Recommended Retail Price (or RRP; synonym - Manufacturer Suggested Retail Price, MSRP): The price suggested by the manufacturer for retailers to sell a product.
  - Total SKUs (or Total Products): Count of SKUs.
  - Total Features (or Total Ad Items): Count of Features.
  - Retailer Price (or Selling Price): The retailer’s non-promotional shelf price for a product (within that retailer).
  - Promotional Price: The temporary, reduced price offered by a retailer for a product in a promotion.
- Metrics (are built from measures)
  - Current Price: If promo applied, current_price = promotional_price, else current_price = rrp
    - Current Price must track the Shelf Price because in mature retail markets (like Australia/UK/US), the “Standard Shelf Price” is often lower than RRP. If you default to RRP when no promo exists, you will artificially inflate the “Was Price,” making discounts look deeper than they are. The current_price should always track the Shelf Price, not the RRP, unless they happen to be identical.
  - Was Price: retailer_price
  - Discount Percentage: Logic: 1 - (current_price / NULLIF(was_price, 0))
  - Discount Amount: was_price - current_price
  - Retailer Lowest Price: The lowest single price point detected for a Retailer within the specific Start Date and End Date of the selected Advertisement. Logic: MIN(current_price)
  - Average Discount Percentage: Logic: AVG(discount_pct)
  - Average RRP: AVG(rrp)
  - Average Promotional Price: AVG(promotional_price)

Backlog

Mon, 25 May 2026 00:00:00 +0000

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).
    - https://media.secondbrain.lelouvincx.com/2026/04/010ee2b4db27a9bc68da91d54a03a681.png
  - 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:

Backlog / Done

Mon, 25 May 2026 00:00:00 +0000

Done

DONE Unsub Contabo VPS due to unused
DONE Continue Cross-Model Calculation
- This may not be a good timing to do this. Should wait for the docs revamping project being in progress more than now (as of #2026-01-03 ).
DONE Review AI sharing dashboard for Aurora
- Timeline:
  - Aurora’s request came in via support. Phuong (AI team) looped in the data team.
  - Hieu investigated and found AI data lives in ClickHouse (logs + user_id only), NOT the production DB. This means user-friendly info (names, emails) and dashboard/dataset-level tracking aren’t directly available.
  - Tien (AI team) confirmed: user_id mapping is possible via prod DB, token usage exists in HOtel, but dashboard/dataset AI activity tracking is hard.
  - Triet advised: only answer what’s currently feasible, treat the rest as feature requests.
  - Hieu drafted a reply to Aurora listing what’s available (conversation ID, user ID, messages, token usage) and limitations (no usernames, no asset tracking, only MCP data).
  - Aurora accepted — said user_id is fine, they’ll map it themselves.
  - Hieu built a dashboard at https://us.holistics.io/dashboards/v4/1099511684352-aurora-ai-conversations and proposed Google Sheets delivery. Aurora also suggested S3 export as an alternative.
  - Nam asked Hieu to wait before sharing — he wanted to discuss commercially first.
  - Nam proposed turning this into a paid upsell package at $10,200/year (“Usage and AI Data Monitoring Transfer”).
  - Chinh (me) reviewed and said the data is feasible to share as spreadsheet, but noted Hieu’s dashboard is not ready to consume right now.
  - Chinh and Phuong questioned charging for AI usage data since the AI team is already building an in-app AI usage monitoring dashboard for all customers.
  - Vincent (CEO) clarified the monetization rationale: the in-app dashboard is free for all; what’s being sold is data sync/export to their own systems (S3/ETL). This targets enterprise needs: compliance, security auditing, long retention (7+ years), and custom analytics.
  - Triet and Vincent discussed delivery method — S3 vs Google Sheets vs ETL to their data warehouse. Vincent prefers S3 since Aurora mentioned it and it’s more scalable for a paid add-on.
- For myself (data team):
  - Data source: AI conversation data is in ClickHouse (not prod DB). It has: conversation timestamps, conversation IDs, user IDs, messages (prompts + replies), token usage. User info (email/name) requires joining with a production DB mapping table.
  - Dashboard exists: Hieu built a dashboard at us.holistics.io/dashboards/v4/1099511684352 but currently not ready to share now.
  - NOTE I need to review the data in dashboard. But not now. Let’s wait for Aurora’s response and the team initialize a project about this. Not sure who will be main owner btw.
  - Prior art: I did similar work for SweetSpot before: https://holistics.slack.com/archives/C09GURCKQV8/p1772181645114809?thread_ts=1770132838.858979&cid=C09GURCKQV8
  - Delivery format is undecided: The current preference is S3 export (Aurora offered to share an S3 bucket). Google Sheets with scheduled delivery was the original plan because we can reuse the Google Sheets Delivery feature. Final decision pending Nam’s email to Aurora.
  - This is now a paid add-on ($10,200/year) — so quality and reliability matter. It’s not ad-hoc anymore.
  - Scope boundaries: Only provide what’s currently available. Don’t try to solve missing data (dashboard/dataset AI activity, feature-specific breakdown beyond MCP). The AI team will build in-app monitoring separately.
  - Stakeholders: Nam (commercial timing), Chinh (me) (data review/quality), and Phuong/Tien/Dat (AI team).
((69bcb599-a91e-49ea-bc3d-6a5a651f03df))

Book - How To Solve It

Mon, 25 May 2026 00:00:00 +0000

Author: [[George Polya]]
I just bought the book. It’s $10. Not expensive. But the value it brings is huge. Worth it.
Key notes
- Chap 1
  - Problem solving is a muscle. The more we practice solving problems, the better we are.
  - Problem solving is like swimming. We learn by imitating and practicing.
  - The teacher who wishes to develop his students’ ability to do problems must instill some interest into their mind and give them plenty of opportunity for imitation and practice.
  - 4 steps of problem solving:
    - Understand the problem logseq.order-list-type:: number
      - What is the unknown? logseq.order-list-type:: number
    - Devise a plan - connect the data, the condition, the unknown logseq.order-list-type:: number
      - Have you solve a similar problem before? logseq.order-list-type:: number
    - Carry out the plan logseq.order-list-type:: number
      - Can you prove it’s correct? logseq.order-list-type:: number
    - Look back logseq.order-list-type:: number
      - What have you done good and bad? logseq.order-list-type:: number
      - Can you derive the result differently and extend this problem? logseq.order-list-type:: number
  - The teacher should be in his student’s shoe, to help him understand and devise the plan better.
  - Do by example.
  - Could you restate the problem?
Quotes
- “If you cannot solve a problem, there is an easier problem that you cannot solve.”
- “The main danger is that the student forgets his plan. This may easily happen if the student received this plan from outside, and accepted it on the authority of the teacher, but if he worked for it himself, even with some help, and conceived the final idea with satisfaction, he will not lose this idea easily.”
- “The teacher may ask: Can you see clearly that the triangle with sides x, y, c is a right triangle? To this question, the student may answer honestly “yes”, but he could be much embarrassed if the teacher be not satisfied with the intuitive conviction, then go on asking: But can you prove that this triangle is a right triangle? Thus, the teacher should suppress this question for now.”
  - Reflect on myself, sometimes I ask questions that dive very deep into one side of the problem, and it goes beyond my initial intention - just want to provide more knowledge to the student. Most cases it’s not good.
  - Because it kills the interest.
  - Don’t dive deep too much, just enough to get the student’s interest. This is more important.
- “It is better to solve one problem in five ways, rather than solve five problems in one way.”

Mon, 25 May 2026 00:00:00 +0000

Data Modeling

Mon, 25 May 2026 00:00:00 +0000

data-ops-bot

Mon, 25 May 2026 00:00:00 +0000

dblineage

Mon, 25 May 2026 00:00:00 +0000

Job To Be Done & Job Map

[[[dblineage] Gathering User Data]]
JTBD: Bridge the knowledge gap between business users and team data
- When I’m a data engineer work with business users to build a ETL pipeline
- I want to close the gap for business users who need to understand the fine-grained logic within those transformations.
- They’re left wondering, “Okay, I see this column came from that column or that table, but how was it calculated? If so, can I trust?”
- So that I and data team can brainstorm, design, discuss, and align on the same business logic
Job Map

DIKW Pyramid

Mon, 25 May 2026 00:00:00 +0000

https://media.secondbrain.lelouvincx.com/2026/02/7ba1920a32ca2377371db8243f9adbdc.png
A mental model from Data - Information - Knowledge - Wisdom. By always being curious (asking why) and actively seeking for answers, connecting the dots and understanding the core / foundation / concept of things.
Inspired by this article: https://campedersen.com/ownership-mindset

Dimensional Modeling

Mon, 25 May 2026 00:00:00 +0000

Keynotes

Dimensional modeling structures data in the way business people think about it, rather than how softwares store it

Docs

Mon, 25 May 2026 00:00:00 +0000

Resources

Figma: https://www.figma.com/design/1mU3qmVzCvjm2CXve978I0/Docs-Graphics

Down The Rabbit Hole

Mon, 25 May 2026 00:00:00 +0000

Gemini: https://gemini.google.com/app/786f401ad9ba4ae8
I realize when doing a task, I often become too over-engineer, lag, time-consuming and not focusing into the main task.
This happens very often.
Symtomps
- Over-engineering: Spending hours writing perfect things that could have been a simpler one.
- Yak shaving: When I want to fix a dashboard, but first I decide to update my dotfiles configuration, which leads to debugging neovim issue, and suddenly 3 hours have passed without touching the dashboard.

Economix

Mon, 25 May 2026 00:00:00 +0000

https://media.secondbrain.lelouvincx.com/2026/03/4c39491a1814c0e767c359321242ad2d.png
Lý thuyết bàn tay vô hình
- Giá của một mặt hàng đúng với giá hợp lý của xã hội đặt cho nó
Mình nhận ra lịch sử ảnh hưởng rất nhiều vào kinh tế của một nước
- Trong chương đầu, học về cách mạng Mỹ, cách mạng Pháp, Napoleon
Mối quan hệ giữa lợi nhuận và tiền lương là một trò chơi có tổng bằng không
- Nếu tỉ lệ lợi nhuận của chủ doanh nghiệp tăng lên thì phần dành cho tiền lương của người lao động tất yếu phải giảm xuống và ngược lại
Thị trường tự do là một assumption các nhà kinh tế học đặt ra để tính toán trên đó dễ dàng hơn
- Ngoài đời thì khác hơn nhiều, một thị trường khó có thể tự do vì tồn tại rất nhiều kinh doanh độc quyền

Gaps and Islands

Mon, 25 May 2026 00:00:00 +0000

Gemini: https://gemini.google.com/u/3/app/42485fec923a41e1

Google Data Portability API

Mon, 25 May 2026 00:00:00 +0000

Gemini: https://gemini.google.com/app/2f98df4376f23aeb
The service to get some personal data such as Maps, Youtube, Search, etc.
Which aligns with the goal at https://github.com/lelouvincx/personal-finance
- “In the future, be able to connect different data sources such as Logseq, Calendar, Maps to give me a more holistic view of my life and finances.”
Available services (https://developers.google.com/data-portability/user-guide/scopes):
- Chrome
- Discover (?)
- Maps
- My Activity
- Play
- Search
- Youtube
NOTE Unlike the manual Google Takeout process, this API supports one-time or time-based (ongoing for 30–180 days) data transfers directly between servers.

Health Rules

Mon, 25 May 2026 00:00:00 +0000

Health Rules
- A living set of personal rules for protecting energy, sleep, and overall well-being. Improve incrementally — add a new bullet whenever a friction point shows up.
Sleep & evenings
- No gaming after 6PM on weeknights. Late-night sessions always extend longer than planned and break sleep. Restrict gaming to morning / early afternoon, or weekends.
- Sleep > productivity. A “lost” hour of sleep typically costs more than the hour it appears to save.
Illness
- Treat illness as a hard stop, not a soft pause. If feeling off two days in a row → full stop on day 2. Don’t push to day 3 hoping it improves.
- Recovery cost compounds: a few days of forced rest is cheaper than a week of dragging through.
Movement & environment
- Walking / nature / no-signal time are real resets — schedule them deliberately, not only when sick.
- 3x short night jogs per week (post-work, lower-temp window). Morning slots conflict with deep work and high temperature; evening cools down and decompresses the day. Added W18 after the Sat May 3 badminton breathlessness signal.
- Eat before exercise. No empty-stomach badminton or jogging — Sat May 3 session degraded fast because no food since morning.
Weekend discipline
- Default to one full off-day per weekend — no Smartclass commits, no Holistics work. Two consecutive non-rest weekends is a yellow flag.
- When the weekend is booked for deep work (e.g., H1 self-reflection + CV refresh), keep at least the Saturday morning slow.
Notes
- Re-read this page during weekly planning (Friday wrap-up) and after any sick day or low-energy week.
- When a rule causes friction in practice, capture the friction here as a new bullet, then iterate.

How to do an internal data tracking project?

Mon, 25 May 2026 00:00:00 +0000

Process

Start with definitions logseq.order-list-type:: number
- Goal: Avoid 3 versions of MRR floating around everyone.
- Sit with stakeholders (finance, rev ops, product) and nail down the definitions.
- Common pitfalls:
  - (1) Entity Resolution issue:
    - Zoho Billing is the source of truth for Finance (MRR/Revenue). Salespeople often enter aspirational data in Hubspot (deal size $10k), but the actual invoice might be $9k due to a last-minute discount.
    - Hubspot is the source of truth for Dimensions. Zoho knows how much they paid, but Hubspot knows who they are (company, lead, customer/prospect)
    - Application DB is the source of truth for Engagement. This is the leading indicator of churn.
  - (2) Reconciliation issue:
    - Finance likely has a spreadsheet they use to report numbers to the board. If your SQL logic differs even by $10 from their manual sheet, they will trust the sheet, not your dashboard.
    - You must replicate their logic exactly before you can improve it.
    - Means, answer this question: “How can I trust the numbers?”.
- Deliverables:
  - Metric Glossary: an evergreen documentation defining business terms, processes, metrics
  - ERD shows how a Company in Hubspot maps to a Customer in Zoho and a Tenant in the app

Inmon - Data Warehousing

Mon, 25 May 2026 00:00:00 +0000

Keynote

Approach: top-down
The philosophy is having a centralized, high quality data warehouse
- By maintaining an EDW - Enterprise Data Warehouse, storing all data as 3NF, aim for data quality and intergrity
- Then so the star schema - dimensional modelling for each specific reporting topic (dataset)
2-step process
- 1. You model the data warehouse using 3NF to ensure truth, quality and consistency
- 1. Then feed that data into data marts which use dimensional modeling for the actual BI reporting to consume

input

Mon, 25 May 2026 00:00:00 +0000

Internal

Mon, 25 May 2026 00:00:00 +0000

If I had to start the core business metrics from scratch
- [[How to do an internal data tracking project?]]

Journals

Mon, 25 May 2026 00:00:00 +0000

Tasks

TODO Review hooli
Done

Just Enough Automation

Mon, 25 May 2026 00:00:00 +0000

https://bevel.work/blog/just-enough-automation/
A #Triet advice: https://www.explainxkcd.com/wiki/index.php/1205

Kimball - Data Warehousing

Mon, 25 May 2026 00:00:00 +0000

Keynotes

Fact: the verbs
Dimension: the nouns
Addictive facts: can sum them up across any dimensions

Lead Funnel by Sales Motion

Mon, 25 May 2026 00:00:00 +0000

Goal
- BizOps (Vincent, Sriram) is doing 2026 revenue planning: setting an MRR target ($330K) and working backwards to determine how many leads they need at each stage to hit it.
  - https://media.secondbrain.lelouvincx.com/2026/03/9b7d19a1a916c3868a43f25c1b3939c0.png
  - https://media.secondbrain.lelouvincx.com/2026/03/daf21e663f6916c8cec1a4c418167e6e.png
- Conversion Rate By Sales Motion: for won deals, what % went through sales-assisted (call first => trial) vs self-serve (trial first => call).
  - Sriram and Vincent intuitively feel call-first has a higher win rate but don’t have data to prove it.
  - https://media.secondbrain.lelouvincx.com/2026/03/233fc4decf6a75e71f71ef06780ce53e.png
- Why it matters: assess which entry point produces better outcomes => to invest more on.
- Decision-making questions:
  - Given we need ~59 raw leads/month to hit 330K MRR, how should we allocate between call-first or trial-first deals?
  - Should we consider removing self-serve trials if call-first converts significantly better?
Sales Motion Classification
- Leads are classified based on timestamp ordering of first demo call vs first trial submission:
  - call-first: first_call_at < submitted_at
  - trial-first: submitted_at <= first_call_at
  - trial-only: trial submitted, but first_call_at is NULL
  - call-only: call booked, but trial_submission_skey is NULL
- For same-day events, uses exact UTC timestamps to determine sequence.
Data Model
- Main working dataset: DTS106

Leap of Faith

Mon, 25 May 2026 00:00:00 +0000

{{video https://youtu.be/y7rWVhihlb8?si=3NL2Cnh4CQKxpk21}}
{{video https://youtu.be/F2c1ORtkmuU?si=uEE403a6bAhP0ZBH}}

Measuring Engineering Productivity

Mon, 25 May 2026 00:00:00 +0000

https://justoffbyone.com/posts/measuring-engineering-productivity/
The system should work for your engineers, not against them.
- If your measurement system makes engineers less productive, you’re failed.
- If it makes them feel surveilled and distrusted, you’re failed.
- If it becomes an end in itself rather than a mean to build better products, you’re failed.

Memory Decreasing

Mon, 25 May 2026 00:00:00 +0000

ngocyen99tb.lelouvincx.com

Mon, 25 May 2026 00:00:00 +0000

How does Olist work?
How does Olist make money?
Tasks
((691029d8-69c2-4627-b93c-7328fcebda27))

Oxygen Not Included

Mon, 25 May 2026 00:00:00 +0000

Written guide

P2

Mon, 25 May 2026 00:00:00 +0000

Parquet

Mon, 25 May 2026 00:00:00 +0000

https://public.lelouvincx.com/parquet-how-it-works.png
{{video https://youtu.be/1j8SdS7s_NY?si=mBplsyA4pzArccsj}}
[[Predicate Pushdown]]
Row Group
Column Chunk
Page
[[Parquet Zone Maps]]
And then there is Delta Lake, which is a storage layer sitting on top of parquet files. In short, we have Delta Lake to manage, provide database’s functionalities, and the files are stored as parquet.

Parquet Zone Maps

Mon, 25 May 2026 00:00:00 +0000

Gemini: https://gemini.google.com/app/c44f8c1670b8187a

Performance Review - 2025H2

Mon, 25 May 2026 00:00:00 +0000

Notes

Section 4, Result Delivery & Reporting, L2 - “Can create an effective story with data, maintaining objectivity in their analysis”
- It’s possible not doing inside Holistics but with my side projects for [[Data Journalism]], [[Data Visualization]]

Personal Context

Mon, 25 May 2026 00:00:00 +0000

User Context & Persona

Professional Profile
- The user is a Data Analytics Engineer and Educator. They maintain a technical site at lelouvincx.com.
- They are highly technical, preferring detailed, engineering-focused discussions over high-level overviews.
- They are working at holistics.io
Technical Stack & Expertise
- Data Engineering: Expert in SQL optimization, data warehousing (Kimball/Inmon), and ETL/ELT pipelines. Frequently uses dbt, Dagster, DuckDB, PostgreSQL (RDS), and Redshift.
- BI & Visualization: Experienced with Holistics, Metabase.
- Infrastructure: Proponent of self-hosting and cost-optimization. Uses low-cost VPS providers (Contabo), Docker, Cloudflare.
- Workflow: Uses MacOS with a keyboard-driven workflow. Preferred editor is Neovim (LazyVim config) and uses Logseq for knowledge management.
Active Projects (Current Context)
- 1. [Duty] Holistics Support
  - Role: Customer Duty Support / Data Analytics Engineer at Holistics.
  - Key Context: Focuses on troubleshooting and scaling solutions for clients.
  - Recent Work:
    - Client “Pencil”: Scaling customer dashboards and optimizing data models within the Holistics platform.
    - Workflow: Synthesizing support call transcripts and drafting technical follow-up communications.
- 2. [Add2Cart] Data Consultancy Service
  - Tech Stack: RDS (PostgreSQL), S3 (data lake), Redshift (data warehouse), Holistics (BI tool).
  - Current Status: configuring replication tasks and debugging connection/permission issues between the OLTP source and OLAP destination.
- 3. [Teaching] Data Analytics Educator
  - Role: Instructor for a junior analyst and a junior engineer.
  - Curriculum: Developing a gamified analytics course based on the Olist E-commerce dataset.
  - Resources: Creating a “Teacher’s Guide” and phased learning materials.
  - Infrastructure: Manages a self-hosted Metabase instance for students, powered by DuckDB and Neon.tech, exposed via Cloudflare Tunnels. Expose learning materials on public website at https://ngocyen99tb.lelouvincx.com, written in Docusaurus.
- 4. [Personal] Infrastructure & Tools
  - Blog/Docs: Revamping lelouvincx.com (formerly hugo blowfish) (focus on themes, search plugins, and sitemaps).
  - Self-Hosting: Personal infrastructure includes Contabo VPS
Cultural Context
- The user is interested in Vietnamese language, culture, and technology (e.g., local banking, esports).

Personal Finance Manager App

Mon, 25 May 2026 00:00:00 +0000

https://gemini.google.com/app/87b8d4ee12216e39
TODO Conceptual Design Priority: #P3
TODO Techstack Design (after conceptual designing) Priority: #P3

Predicate Pushdown

Mon, 25 May 2026 00:00:00 +0000

Category: [[Database Optimization]]
When filter some data, instead of loading all data into memory then filter, predicate pushdown allows filtering at the query execution layer/storage layer, in order to only load the filtered data into memory.
Benefit:
- Reduce I/O
- Reduce Time
How it works
- Before (without predicate pushdown)
  - Read: The engine read 100% data from storage. logseq.order-list-type:: number
  - Transfer: The engine transfers all data over the network to the compute engine. logseq.order-list-type:: number
  - Filter: The compute engine loads data into memory and applies WHERE. logseq.order-list-type:: number
- After
  - Read: The compute engine sends the query and the filter to the storage/metadata layer. logseq.order-list-type:: number
  - Filter: The storage/metadata layer uses statistics based on the WHERE to skip entire redundant blocks of data. logseq.order-list-type:: number
  - Transfer: Smaller data transfers over the network. logseq.order-list-type:: number
Pitfalls
- Casting: something like WHERE CAST(string_col AS INTEGER) > 5 will not work.
  - Because the compute engine has to read all data to do the cast before filtering (which Holistics usually use).
- Complex UDF.
- Unsorted: If data random across row partitions, the predicate pushdown won’t work effectively.

Presales

Mon, 25 May 2026 00:00:00 +0000

Principles

Mon, 25 May 2026 00:00:00 +0000

Principles
- A triage page for heuristics gained from experience. Not the final home — the inbox / staging area.
- Each entry: one-line trigger, one-line response, backlink to the journal where it was forged, and a status.
- Once a heuristic matures (fires a 2nd time and has a clear domain), route it out to a dedicated page or upstream to a team-owned doc. The triage page stays small on purpose.
How to use this page
- Capture freely. Anything I notice once gets dropped here. Low friction.
- Promote on second use. If a heuristic fires a 2nd time in real work, it has earned a spot on a dedicated page.
- Archive on neglect. If an entry sits in triage > 60 days without a 2nd use, archive it. The page is for active heuristics, not aspirations.
- Re-read during Friday wrap-up. Demote anything routed-out that hasn’t fired in 90 days.
Routing targets
- prioritization / scheduling → [[Priority Rules]]
- sleep / illness / movement / energy → [[Health Rules]]
- (future) work-craft pages may emerge:
  - communication → [[Communication Rules]] (TBD)
  - code review / on-call → [[Code Review Rules]] (TBD)
- Some heuristics belong outside the second-brain. Upstream to team-owned docs when the rule is not unique to me — it converts a private heuristic into team infrastructure, and the writing exercise itself is career-visible.
Status legend
- triage — just captured, awaiting a 2nd occurrence.
- routed → [[Page]] — promoted to a dedicated page; this entry kept as a stub for backlink.
- upstream → <team doc> — proposed / merged into a team-owned doc.
- archived — did not survive a 2nd use within 60 days, or superseded.
Entries
- Work craft
  - dbt deprecation 3-phase rule
    - trigger: deprecating a dbt model that other AML / BI assets reference.
    - response: phase 1 deprecate in code → phase 2 remove the .sql → phase 3 drop the BQ table. Don’t sit between phase 2 and 3 — AML references BQ physical names, so removing the .sql only stops refresh and leaves the table silently misleading consumers.
    - forged: [[Weekly Report - 2026-W17]] · Ampcode T-019da543
    - validated: W18 Calendly cleanup — 3 legacy models deleted in PR internal-aml-project#78 without re-deriving the reasoning.
    - status: upstream → holistics/dbt contributing guide (proposed). Team correctness rule, should outlive me.
  - Small P1 ships before big P2 context-switch
    - trigger: a P1 escalation lands while a small / cheap P1 task is still open.
    - response: ship the 30-min item first, then context-switch. The cheapest item is the one most at risk of slipping when escalations arrive.
    - forged: [[Weekly Report - 2026-W18]] (dbt PR #858 round 1 review slipped when BuyCo + Wamly P1 escalations landed Wed).
    - status: triage. Candidate for a future on-call / escalation handling note.
- Communication
  - Customer comms reframe — recipe, not IOU
    - trigger: a customer asks for help with a workflow / configuration.
    - response: frame as “here is the recipe, happy to pair if helpful” instead of “I’ll do it for you”. Volunteering hands-on work tends to get silence in return.
    - forged: [[2026-04-27]] · validated against W17 Showbie + Basata silence pattern.
    - validated: W18 BuyCo 14-thread triage — replies were structured as workarounds + screen-recording asks, not “I’ll log in and fix it for you”.
    - status: upstream → presales comms playbook / CS onboarding doc (proposed). Pattern is not unique to my threads.
  - Ask for no, don’t ask for yes (Mooreds)
    - trigger: needing a small decision from a busy stakeholder (manager, peer).
    - response: replace “can we do X?” with “I’m going to do X to solve Y, will take care of it Monday unless I hear differently.” Shifts cognitive load to opt-out and unblocks progress while keeping ownership.
    - forged: [[Weekly Report - 2026-W17]] · mooreds.com
    - status: triage. Tone needs to be calibrated per person — practice on smaller decisions first.
  - Concision — what is the most important thing to say? (Wes Kao)
    - trigger: writing a status update, PR description, Slack message, or stakeholder note.
    - response: lead with the most important sentence. Cut anything that doesn’t change the reader’s decision or action.
    - forged: [[Weekly Report - 2026-W18]] · Wes Kao — How to Be Concise
    - status: triage. Pair with Levels of detail in communication once read.
- Decision-making / scheduling
  - Vague task → time-block + decompose to smallest concrete next step
    - trigger: a task feels blocking / overwhelming and keeps getting deferred.
    - response: time-block a slot, then force decomposition into the smallest concrete next step. Long carry-overs often have a procrastination root, not a priority root.
    - forged: [[2026-04-30]] · Wait But Why — How to Beat Procrastination
    - validated: same-day BuyCo 14-item Notion page → 14 micro Slack threads in #holistics-buyco-external, all shipped in one Wed afternoon.
    - status: triage. Candidate for promotion to [[Priority Rules]] (pairs with the 3+ week carry-over forcing function) on next occurrence.
  - Highest-leverage triage on low-energy weeks → routed → [[Priority Rules]]
  - 3+ week carry-over forcing function → routed → [[Priority Rules]]
- Reflection / craft hygiene
  - Writing is thinking — daily journals are 100% me
    - trigger: temptation to outsource a journal entry / reflection draft to an LLM.
    - response: don’t. LLM is fair game for boilerplate / first drafts only. The reflection muscle is the differentiator.
    - forged: [[Weekly Report - 2026-W18]] · HN thread
    - status: triage.
  - Cultivate non-LLM reading sources
    - trigger: defaulting to LLM search inside Logseq for ideas / craft inspiration.
    - response: deliberately seek out blogs / RSS / newsletters from individual senior writers (e.g., mooreds.com, Wes Kao, benn.substack). Signal/noise from a curated human writer is different from an aggregated answer.
    - forged: [[Weekly Report - 2026-W17]]
    - status: triage.
Routed (kept as stubs for backlink)
- Sleep > productivity → routed → [[Health Rules]]
- Illness = hard stop on day 2 → routed → [[Health Rules]]
- No gaming after 18:00 on weeknights → routed → [[Health Rules]]
- Eat before exercise → routed → [[Health Rules]]
- Weekend discipline (1 full off-day default) → routed → [[Health Rules]]
Notes
- Re-read this page during Friday wrap-up alongside [[Priority Rules]] and [[Health Rules]].
- When the same heuristic shows up in 2 separate weekly reports, that’s the promotion signal — move it out.
- Upstreaming to team docs is higher leverage than keeping a heuristic personal. Ask: “would Thuan / a new hire benefit from this being in the team’s docs?” If yes, draft the upstream PR.

Priority Rules

Mon, 25 May 2026 00:00:00 +0000

Priority Rules
- A living set of personal rules for prioritizing tasks. Improve incrementally.
Working principles
- Choose the highest-leverage tasks even when the week’s workload is low (e.g., sick, leave, traveling). A low-energy week shouldn’t slide into a low-leverage week — pick fewer items, but pick the most important ones.
- 3+ week carry-over rule — any item carried over 3 or more weeks gets a forcing function:
  - either elevate its priority and schedule it on a specific day, OR
  - formally move it to backlog / waiting (with the reason).
  - Goal: avoid the “always-on but never-done” zone.
Priority tiers
- P0 — Urgent
  - Must do immediately.
  - Usually customer-facing tasks that need a response or mitigation ASAP (e.g., production incident, enterprise customer escalation, data outage).
  - Drop other work to handle these.
- P1 — High
  - Should prioritize doing because some stakeholders are blocking.
  - Includes manager-elevated items and teammate-blocking reviews.
- P2 — Normal
  - Important but not urgent.
  - Picked up when no P1 tasks are active.
  - Most internal data work / improvements live here.
- P3 — Personal / Teaching / Free time
  - Personal projects, teaching, learning, exploration.
  - Can be done in free time, or delegated to others when possible.
Notes
- Re-read this page during weekly planning (Friday wrap-up).
- When a rule causes friction in practice, capture the friction here as a new bullet, then iterate.

Product-Led Growth

Mon, 25 May 2026 00:00:00 +0000

Resources

1. The Foundational “Bible” of PLG
- ProductLed.org: Run by Wes Bush. This is the gold standard for understanding the why.
- Amplitude’s Mastering Retention & Growth Guides: While they sell a product, their playbooks on “Behavioral Cohorting” are essential for learning how to model user actions into “States” (e.g., Active, At-Risk, Power User).
- Book - Product-Led Growth
1. Technical Modeling
- dbt Labs Blog - Modeling for PLG: Search for their articles on “Modeling the Customer Journey.” They have excellent deep-dives on how to handle the many-to-many relationship between Users and Accounts in SQL.
- The Hightouch or Census Blogs (Data Activation): These companies pioneered Reverse ETL. Their blogs are specifically geared toward engineers building the “HubSpot + Product Data” loop. Look for “How to build a PQL scoring model in Snowflake/BigQuery”.
- Hacking Data (Newsletter/Blog): Often covers the technical debt involved in stitching together SaaS tools like HubSpot and Stripe (similar to your Zoho setup).
1. Industry Voices
- Benn Stancil’s Substack: Benn (founder of Mode) writes deeply about the intersection of BI tools and data modeling. Since you are building a BI-related product, his insights on how users “consume” data are highly relevant.
- Locally Optimistic Slack: A community for data leaders and engineers. There is often a lot of discussion about “GTM (Go-To-Market) Data Modeling.”

Projects

Mon, 25 May 2026 00:00:00 +0000

List of projects

[[Add2Cart]] — Cross-functional project for the Add2Cart professional service: data pipeline, performance optimization, dynamic markdown, and S3 setup
[[AI]] — Holistics AI squad work: test suites, AI feature trials, squad coordination with Dat/Tram
[[Docs]] — Holistics documentation improvements and revamping
[[Duty Support]] — Rotating on-call data support for Holistics customers (Zendesk tickets, impersonation, troubleshooting)
[[Freetime]] — Low-priority reading and exploration done in spare time
[[Internal]] — Holistics internal data team work: dbt, MRR reporting, CI, tracking
[[Logseq]] — Improvements to this second-brain system: automation, backlog structure, weekly reports
[[Misc]] — One-off tasks that don’t fit other projects
[[Personal]] — Personal tooling, side projects, migration, self-hosting, learning
[[Personal Productivity Analysis]] — Personal productivity monitoring: ingest weekly reports + journals into DuckDB (consistent schema with [[Personal Finance]] for later consolidation), build dashboard to track throughput, carry-overs, project mix, priority hit-rate, presales W/L, tooling ROI — drive data-driven planning and 1-on-1 decisions
[[Presales]] — Holistics presales support: customer demos, solution proposals, competitive analysis
[[Read]] — Reading and studying: articles, books, courses, youtube
[[Smartclass]] — Personal side project: an ed-tech app with frontend (shadcn/ui) and releases
[[Teaching]] — Mentoring and teaching data/SQL: composing projects (Olist), visualization, set-based thinking

Self-Serve Analytics

Mon, 25 May 2026 00:00:00 +0000

Source: https://www.holistics.io/blog/self-service-analytics-comic/
Comments (Reddit Link)

Semantic Layer

Mon, 25 May 2026 00:00:00 +0000

https://gemini.google.com/u/0/app/d7c56a75abd0fa3d

Set-based thinking

Mon, 25 May 2026 00:00:00 +0000

https://chatgpt.com/g/g-p-68c64703caf48191b0583c8a6857f08c-chinh/c/69100b0f-d6c4-8323-8b01-de7b169cf129

Slowly Changing Dimension

Mon, 25 May 2026 00:00:00 +0000

https://gemini.google.com/app/dabc4a0a978845c1
Keynotes
- Slowly Changing Dimensions (SCD) refer to how you store historical changes in data
- Type 0: retain original
- Type 1: overwrite data
- Type 2: add new row for historical record
- Type 3: add new column stand for previous value and current value
- Type 4: keep the main dimension table for current data, while moving all historical changes to a separate history table
- Type 6 (1+2+3=6): create new row but also overwrite current state column

stakeholders

Mon, 25 May 2026 00:00:00 +0000

Triangle of Talent

Mon, 25 May 2026 00:00:00 +0000

https://gemini.google.com/share/f5ebbad97a43

Trip - Bàu Sấu 04 / 2026

Mon, 25 May 2026 00:00:00 +0000

Không hiểu sao quan cảnh rất giống trong Ghibli, nhìn rất thơ mà nét nào ra nét nấy.
Vài bức ảnh chụp được
- Con chuồn chuồn màu đỏ xinh ghê
- https://media.secondbrain.lelouvincx.com/2026/04/d974844edd7e3ca2f6766202a3dd18e7.png
- https://media.secondbrain.lelouvincx.com/2026/04/66bef276e3dfdc62379611575bad9974.png
Nhìn căn nhà giống trong truyện tranh
- https://media.secondbrain.lelouvincx.com/2026/04/bec3a65711ad14207108b4f84056d418.png
- https://media.secondbrain.lelouvincx.com/2026/04/4f8a777db7397ec4a53df316e565323d.png
Cái cây này giống trong truyện của Nguyễn Nhật Ánh
- https://media.secondbrain.lelouvincx.com/2026/04/d8070c4a0a490404e1e2fa0339a649a7.png
Quả chò rơi xuống từ mái nhà
- https://media.secondbrain.lelouvincx.com/2026/04/94b4d09b2f00191ea46de9b28c26e878.mp4
Ấn tượng rất tốt về nơi này, giống như vừa lạc 1 chuyến vào thế giới Ghibli vậy. Sẽ quay lại vào năm sau, vì tầm này được lợi thế là đi rừng không có muỗi/côn trùng, khô ráo (hơi nóng ẩm tí) và không mưa ngập.

Weekly Planning - 2026-W10

Mon, 25 May 2026 00:00:00 +0000

Plan for week 10 (Ampcode)

P1
- Add2Cart
  - ((69a2a14f-91e8-49be-be93-da1c506869aa)) (carry-over from friday, push Anurag).
  - ((69a2a1cc-94ff-4e02-972e-3b4d720b63ce))
- Internal
  - ((69a42ffd-22c7-4b43-8b34-0f663743abcf))
  - ((69a2a1cc-fc1f-4802-ba56-48183fa9e9a5))
P2
- Internal
  - ((697889da-2e31-4c43-9676-81a898db1ea6))
- Presales
  - ((69841d05-88ea-4209-82ca-30b11b26e91c))
P3
- Duty Support
  - Document MedEnterprises performance use case on metrics sheet.
- Personal
  - Learn logseq’s internal query, and potentially build a skill to query tasks faster.
  - Estimate timeline for teacher Thanh.

Weekly Planning - 2026-W11

Mon, 25 May 2026 00:00:00 +0000

P1
- Internal
  - Review MRR PR holistics/dbt#812 — awaiting author’s remaining fixes.
  - DE-202 trial-first vs call-first — share POC with Vincent/Sriram.
P2 – Should Do
- Internal
  - DE-201 PR Workflow enhancement — continue commenting.
  - Fix excluding internal testing Zoho accounts (DAT-524) — lingering since week 7.
  - Continue Cross-Model Calculation — timing may still be premature (docs revamping not far enough).
P3 – Nice to Have
- Presales
  - Read Modeling Patterns docs; watch Taxdome onboarding call; learn embedded analytics use case; compare ChatGPT solutions Omni vs Holistics.
- Teaching
  - Figure out set-based thinking curriculum; find football dataset for Duc Anh; checkout pudding.cool resources; research visualization resources.
- Personal
  - Consider a Flashcard app for learning English words.

Weekly Planning - 2026-W13

Mon, 25 May 2026 00:00:00 +0000

Plan for week 13 (Mar 23 – Mar 29, 2026)

P1 – Must Do
- Presales
  - ~~Onboarding call 3 with Basata~~ — DONE. Shared Date Drill use case, reported Auto Mapping Filter issue.
  - Share the embedded dashboards document for different customers — carry-over from call 3. Excalidraw
- Internal
  - Review what Hieu wrote on MRR, help him communicate with growth team (2 items: dashboard alignment + currency exchange rate).
  - Create an agent skill for fixing data pipelines (dbt) for #data-ops-bot.
  - ~~Investigate failed dbt assets in #data-ops-bot~~ — DONE. Root cause identified (scheduling order + LEFT JOIN bug), SQL refactored, Notion doc written, DAT-569 created.
  - ~~Create a new GitHub account for work~~ — DONE. Next: update Logseq automation to switch between credentials.
P2 – Should Do
- Internal
  - Review Thuan’s PR #845 on DE-208 / mart_product__dataset_datamodel_dimensions — open, feedback shared, needs final approval.
  - Revise phase 2 of MRR problem — PR #812 merged, 2.1 fixed. Remaining: static exchange rate (1.1/1.2), domain mapping (2.2), duplicated companies (2.3).
  - Ingest Calendly data into warehouse (DAT-283) — ongoing. Calendly vs ReadAI assessed as complementary. Pending: standardize source pipeline + unified dbt models.
  - Check back Census usage estimate to confirm free tier — due Mar 26.
  - DAT-555 resolution — decide whether to remove fct_job_queue_performance; write Notion doc for team review.
  - Fix excluding internal testing Zoho accounts — DAT-524, lingering since W7.
- Add2Cart
  - Waiting for Anurag to ingest 6 countries’ Retailer tables into Redshift (airbyte_schema_*). Then fix “history-only 589 retailers” issue.
- Teaching
  - Brazilian dashboard Dash 2 (Shipping Overview) + demo video for Yen — carry-over.
- Docs
  - ~~Fix markdown files missing for index pages~~ — DONE. PR #1443 merged.
P3 – Nice to Have
- Internal
  - ~~Run first AI-for-data-ops-bot cycle~~ — partially done (investigated DAT-569 with agent, documented for Thuan). Next: formalize as reusable agent skill.
- Presales
  - Read Modeling Patterns docs.
- Personal
  - Change to a more professional work avatar.
  - Consider a Flashcard app for learning English words.
Focus days suggestion
- ~~Block Tue–Wed for Calendly ingestion + MRR phase 2 planning.~~ Adjusted: Wed–Thu for MRR review + growth team alignment.
- Fri: wrap up PR #845 review, Calendly pipeline coding.

Weekly Planning - 2026-W14

Mon, 25 May 2026 00:00:00 +0000

Plan for week 14 (Mar 30 – Apr 4, 2026)

P1 – Must Do
- Add2Cart
  - Ingest countries data into Retailers table — carry-over from W13 Friday. Complete Redshift SP/table audit (unused SPs + orphan tables identified). Schedule this Monday morning when fresh.
- Internal
  - Create an agent skill for fixing data pipelines (dbt) for #data-ops-bot — carry-over from W13. Build on DAT-569 investigation + Thuan’s debugging process doc.
  - Final approval on Thuan’s PR #845 (DE-208 / mart_product__dataset_datamodel_dimensions) — changes requested in W13, needs follow-up review.
- Presales
  - Prepare and attend onboarding call 2 with [[Showbie]].
  - Follow up with Basata on next onboarding session.
  - Polish embedding documentation — reduce friction for prospects setting up embed portals. Increasing lead volume makes this urgent.
P2 – Should Do
- Internal
  - Visualize schedule of all data lineage (airbyte, data import, prefect sync, dbt table-level, census/fivetran activations) — new backlog item from W13.
  - Continue Calendly data pipeline (DAT-283) — standardize source pipeline, build unified dbt models.
  - Fix excluding internal testing Zoho accounts (DAT-524) — lingering since W7. Timebox: max 2h or explicitly deprioritize.
  - Review Hieu’s exchange rate document when ready — waiting from W13.
- Presales
  - Investigate Showbie performance concern — raised with Huy in W13, wait for next call then investigate if needed.
- Add2Cart
  - Document project and guide setup for other countries.
  - Project retro with team (Dong).
- Teaching
  - Brazilian dashboard Dash 2 (Shipping Overview) + demo video for Yen — carry-over from W12.
P3 – Nice to Have
- Internal
  - DAT-555 resolution — decide whether to remove fct_job_queue_performance; write Notion doc.
  - Upgrade dbt-core of repo dbt to the same version as prefect (compatible).
- Presales
  - Read Modeling Patterns docs.
- Personal
  - Self reflection and update CV.
  - Read Levels of Detail in Communication — from W13 recommended resources.
Focus days suggestion
- Mon: Add2Cart Redshift ingestion (deep work, fresh Ampcode tokens). Thuan’s PR #845 final review.
- Tue–Wed: Calendly pipeline + agent skill for dbt ops bot (minimize context switches).
- Thu: Presales calls (Innerspace, Basata follow-up). Polish embedding docs.
- Fri: Zoho accounts fix (timeboxed), backlog grooming, weekly report.

Weekly Planning - 2026-W15

Mon, 25 May 2026 00:00:00 +0000

Plan for week 15 (Apr 6 – Apr 10, 2026)

P1 – Must Do
- Internal
  - Calendly data pipeline (DAT-283) — elevated to P1 from W14. Currently only demo/onboarding calls ingested; need all 50+ event types. Growth team needs this for sales rep performance and Lead Funnel sales motion enrichment.
  - ~~Zendesk debug~~ → pivoted to upgrade plan (3 options written, WAITING review).
- Presales
  - ~~Onboarding call 1 with Jonas Chorum~~ — moved to Apr 9. Continue dynamic data source demo prep.
- Add2Cart
  - ~~Project retro with anh Dong~~ — carry forward to W16.
P2 – Should Do
- Internal
  - Create agent skill for fixing dbt data pipelines in #data-ops-bot — carry-over from W13.
  - Fix excluding internal testing Zoho accounts (DAT-524) — lingering since W7. Timebox: max 2h.
  - DAT-571 Zendesk upgrade plan — get review and decide on option (Fivetran vs Prefect orgs-only vs Airbyte upgrade).
  - DAT-555 — get PR reviews for dbt #849 and internal-aml-project #69 (remove fct_job_queue_performance).
  - Contribute to Holistics skills and internal-skills repos.
- Docs
  - Polish embedding documentation — ask anh Tai and anh Huy to clarify scope.
- Add2Cart
  - Get anh Huy’s review on D4 countries guidance document (WAITING).
P3 – Nice to Have
- Presales
  - Read Modeling Patterns docs.
- Internal
  - Lead Funnel by Sales Motion (DAT-560) — review and make a plan; context page created.
  - Upgrade dbt-core of repo dbt to match prefect version.
- Personal
  - Self reflection and update CV.
Progress vs plan (as of Tue)
- DONE: DAT-569 snowplow fix (PRs merged, deployed, backfill success).
- DONE: Add2Cart countries ingestion.
- DONE: DAT-555 downstream models written (waiting PR review).
- DONE: Lead Funnel context page consolidation.
- DONE: Zendesk upgrade plan written (3 options).
- NOT STARTED: Calendly pipeline, agent skill, DAT-524, embedding docs.
- MOVED: Jonas Chorum call → Apr 9. Add2Cart retro → W16.
Focus days suggestion (updated)
- Tue (today): Data sync meeting. Follow up on DAT-555 PR reviews. Lead Funnel planning.
- Wed: Calendly pipeline deep work (P1). DAT-524 timeboxed 2h morning. Embedding docs scope with anh Tai/Huy.
- Thu: Jonas Chorum demo prep. Holistics skills repo contribution. D4 review follow-up with anh Huy.
- Fri: Calendly pipeline continued. Backlog grooming. Agent skill for dbt ops bot.

Weekly Planning - 2026-W16

Mon, 25 May 2026 00:00:00 +0000

Plan for week W16 (Apr 14 – Apr 18, 2026)

P1 – Must Do (aligned with manager’s priorities from 1-on-1)
- Internal
  - ~~Transfer MRR project with anh Hieu~~ — DONE Apr 14. Next: build dim_exchange_rates, implement dual MRR metrics.
  - ~~Write 1-on-1 report~~ — DONE. Meeting held Apr 15.
  - Calendly data pipeline (DAT-283) — answer anh Dong’s review comments on PR dbt #853. Once merged, run models and validate data.
  - fct_job_queue_performance (DAT-555) — follow up on PR dbt #854 review. Once merged, start ~26 weekly backfill chunks.
  - Data quality focus (manager priority #1): MRR identity resolution + exchange rates.
P2 – Should Do
- Internal
  - Increase data freshness — explore making impersonation lookup more frequent than daily (DAT-499). Manager priority #3.
- Add2Cart
  - ~~Project retro with anh Dong~~ — WAITING on deal outcome (Simon). Vincent followed up Apr 14. Deprioritize until deal progresses.
- Teaching
  - Find a football dataset for Duc Anh.
P3 – Nice to Have
- Internal
  - Lead Funnel by Sales Motion (DAT-560) — review and plan after Calendly pipeline stabilizes.
  - Contribute to Holistics skills and internal-skills repos.
- Presales
  - ~~Polish embedding documentation~~ — deprioritized per 1-on-1 (not the right timing). Maintain informally.
  - Read Modeling Patterns docs.
- Personal
  - Self reflection and update CV.
Focus days suggestion
- Mon: (done) Weekly planning, read DE-187, MRR transfer with anh Hieu (DONE).
- Tue: Answer Calendly PR reviews (DAT-283). Data sync meeting. 1-on-1 report.
- Wed: Calendly pipeline — run models if PR merged. Embedding doc proposal for anh Huy/Tai.
- Thu: DAT-555 follow-up. Teaching dataset search. MRR exchange rate next steps.
- Fri: Wrap-up, backlog grooming, weekly report friday prep.

Carry-over watch

Item	Since	Weeks	Action
DAT-524 Fix excluding internal Zoho accounts	W7	9	Deprioritize formally or timebox 2h this week
Agent skill for dbt #data-ops-bot	W13	3	Timebox 2h or defer to W17
Add2Cart retro with anh Dong	W15	1	Schedule this week
DAT-283 Calendly pipeline PR review	W15	1	Follow up with anh Dong
DAT-555 fct_job_queue_performance PR review	W14	2	Follow up with reviewer

Weekly Planning - 2026-W17

Mon, 25 May 2026 00:00:00 +0000

Plan for week W17 (Apr 20 – Apr 25, 2026)

P1 – Must Do
- Duty Support
  - Review AI sharing dashboard for Aurora (enterprise customer) — Slack. Monday priority.
- Presales
  - Basata follow up on light/dark theme (enterprise customer) — Slack. Monday priority.
- Internal
  - Merge Calendly PR dbt #853 (approved, mergeable). Run dbt models, validate data in Holistics BI. Then fix downstream fct_sales_leads join. DAT-283.
  - Review anh Dong’s CircleCI PR prefect #397 (DAT-579) — expand test metadata ingestion + backfill flow.
  - Start MRR exchange rate work (DAT-576) — build dim_exchange_rates with live rate ingestion (Google Finance/ECB). Manager priority #1.
- Docs
  - Add demo video for local development docs — draft scenario, discuss with anh Huy Vu/Dat. Elevated to P1 per presales sync.
P2 – Should Do
- Internal
  - Clean up BI layer for job queue dashboards: delete [WIP] Job Queue Performance 3.0, migrate v2 and Report Monitoring to 4.0.
  - Increase data freshness — explore making impersonation lookup more frequent than daily (DAT-499). Manager priority #3.
  - Lead Funnel by Sales Motion (DAT-560) — review and plan after Calendly pipeline stabilizes.
- Teaching
  - Find a football dataset for Duc Anh.
P3 – Nice to Have
- Internal
  - Contribute to Holistics skills and internal-skills repos.
- Presales
  - Read Modeling Patterns docs.
- Personal
  - Self reflection and update CV.
  - Consider downgrading Google One plan.
Backlog (deprioritized, pick up after MRR/Calendly)
- Internal: DAT-524 Fix excluding internal Zoho accounts — small task, 10 weeks carry-over. Not urgent.
Focus days suggestion
- Mon: Aurora AI dashboard review + Basata light/dark theme follow-up (enterprise customers first). Merge Calendly PR, run models.
- Tue: Validate Calendly data in Holistics BI. Fix downstream fct_sales_leads. Review CircleCI PR for anh Dong.
- Wed: Start dim_exchange_rates design. Demo video scenario drafting.
- Thu: MRR exchange rate deep work continued. BI layer cleanup (job queue dashboards). Teaching dataset search.
- Fri: Wrap-up, backlog grooming, weekly report.

Carry-over watch

Item	Since	Weeks	Action
DAT-560 Lead Funnel by Sales Motion	W14	3	Unblocked once Calendly merges
DAT-283 Calendly pipeline (approved, not merged)	W15	2	Merge Monday
Demo video for local dev docs	W15	2	Elevated to P1 this week

Weekly Planning - 2026-W18

Mon, 25 May 2026 00:00:00 +0000

Plan for week W18 (Apr 27 – May 3, 2026)

Holiday note: Thu Apr 30 (Reunification Day) and Fri May 1 (Labour Day) are public holidays in Vietnam. Effective workdays = Mon, Tue, Wed.

Progress vs plan (as of Tue Apr 28)
- DONE: DAT-283 Calendly BI rollout (PR #78 merged Apr 28); DAT-585 Tenant Lookup User List fix (PR #77 merged Apr 27); CircleCI prefect PR #397 round-1 review.
- IN PROGRESS: DAT-584 deploy_dbdocs fix (PR #860) — round 1 done, raised concern on relationships.dbml exposure; CircleCI dbt PR #858 — pending round 1.
- NEW (incoming P1): BuyCo ticket triage — anh Huy escalated as urgent active prospect; watch demo call first.
- NEW (incoming P1): Wamly onboarding call Wed Apr 29 18:00 — support Wudi as note-taker / follow-up / product feedback. SCS plan, drill-down on pivot is make-or-break. Slack.
- NEW (P2): 1Win case clarification per Quinn (Slack DM Apr 28).
- NOT STARTED: DAT-576 MRR exchange rate kickoff (target Wed Apr 29); DAT-555 follow-up; DAT-556 dbt test fix.
- MOVED: Demo video scoping — still waiting on Khai To’s MCP demo (no movement).
P1 – Must Do

Weekly Planning - 2026-W19

Mon, 25 May 2026 00:00:00 +0000

Plan for week W19 (May 4 – May 10, 2026)

First full 5-workday week after the W18 holidays. Use the energy. Mon AM is the forcing-function slot for MRR exchange rate (3-week carry-over).

Progress vs plan (as of Tue May 5)
- DONE: Set up GitHub App for bi.holistics.io (Mon); 1Win Zoho check (Mon); Review DAT-584 round 1 (Mon); Prep for anh Nam’s call with Bicycle Transit (Tue, P1 added mid-week); Align Data Import schedules / DAT-587 (Tue, P2 added mid-week).
- IN-PROGRESS: CircleCI dbt PR #858 review for anh Dong — debugged failing CI tests, cherry-picked into dbt#861, waiting for next review request.
- WAITING: BuyCo triage follow-through — 14-thread sweep continues; chasing PMs (Vy, Hien, Di) + BuyCo screen recording on item 10. Wamly — Farren on paternal leave, Chukwudi reaches out ~May 11–15 (now in backlog).
- MOVED / NEW: Showbie deal lost to Omni — feedback synthesis added for Wed (May 6). Auto-export dashboard PNG feedback to Khai To drafted (P2, Docs/feedback). Onboarding call 4 with [[Basata]] scheduled May 19.
- NOT STARTED (slipped Mon): MRR exchange rate (DAT-576) — Mon AM hard-block consumed by GitHub App + carry-overs; Tue went to Bicycle Transit prep. Forcing function: take Wed AM 09:00–12:00 slot, otherwise escalate to anh Triet for re-scoping. DAT-555 follow-up; DAT-556 dbt test fix; BI cleanup; DAT-560 unblock-or-backlog pass; H1 self-reflection + CV.
P1 – Must Do
- Internal
  - MRR exchange rate kickoff (DAT-576) — 3-week carry-over (W16 → W18). Mon AM (09:00–12:00 hard block): design dim_exchange_rates (rate source = ECB or Google Finance), Tue: write Linear scoping comment + small POC. If still blocked by Wed EOD, escalate to anh Triet for re-scoping. Manager priority #P1.
  - Resolve DAT-555 follow-up — captured in [[2026-04-27]]. Carry-over.
  - Resolve DAT-556 dbt test failure — root cause analysed Apr 22 (Ampcode). Apply the fix. Carry-over.
  - Close out CircleCI dbt PR #858 review round 1 for anh Dong (Ampcode). Carry-over from W18 — slipped because of BuyCo + Wamly. Mid-week update: round 1 done, CI debug done, cherry-picked into dbt#861 — IN-PROGRESS, waiting for next review request.
- Presales
  - BuyCo triage follow-through ([[BuyCo]]) — added Mon May 4. Continue checking the 14 threads in #holistics-buyco-external; chase PM replies on items 1, 2, 4, 11 (Vy Huynh, Hien Nguyen, Di Hoang) and BuyCo screen recording on item 10. Daily 15-min check.
P2 – Should Do
- Personal
  - Self-reflection + CV update for 2026 H1 performance review — elevated from P3. PR cycle is coming up; need a reflection draft + refreshed CV before manager check-in. Block out next weekend (Sat May 9 + Sun May 10) for deep-work session.
- Internal
  - ~~1Win duplicate-customer check in Zoho billing per Quinn’s DM. Timebox 1h. Carry-over from W18.~~ — DONE Mon May 4.
  - Lead Funnel by Sales Motion (DAT-560) — 5-week carry-over (since W14). Now that Calendly BI layer is live, do a 30-min “is this still blocked?” pass. If yes, formally backlog with a date; if no, schedule a slot. Do not let this drift again.
  - Increase data freshness — impersonation lookup more frequent than daily (DAT-499). Manager priority #P3.
  - BI cleanup: delete [WIP] Job Queue Performance 3.0; migrate v2 + Report Job Queue Performance Monitoring to 4.0. Carry-over.
  - ~~Review DAT-584 round 2~~ — round 1 closed Mon May 4 (dbt#860, Ampcode). Awaiting author for round 2.
  - ~~Set up GitHub App for bi.holistics.io (new in [[2026-05-25]]). Scope first — 30-min design pass.~~ — DONE Mon May 4 (Ampcode).
  - NEW (Tue) — Align Data Import schedules (DAT-587) — DONE May 5 via Slack.
- Presales
  - Basata catch-up call — Tue May 5 (thread). Sync with Taha on the dual-dashboard plan during this call — replaces the W18 “soft check-in” follow-up.
  - ~~Soft check-in to Showbie (Harsha)~~ — DONE. Update May 4: lost the deal to Omni (1). Action Wed May 6: synthesize Holistics-vs-Omni learning + chase Harsha for personal feedback.
  - NEW (Tue) — Bicycle Transit prep for anh Nam’s call — DONE May 5 (Slack, Ampcode prep). Mock-demo workflow ran end-to-end.
- Wamly — WAITING (was P1 in earlier draft). Farren cancelled Apr 29 call (urgent matter), now on 10-day paternal leave from May 1; Chukwudi will reach out in ~2 weeks per the reschedule thread. No action this week — re-pick around May 11–15. Trial-expires-May-6 panic moot since customer is unavailable; will need a trial extension request when Farren returns.
P3 – Nice to Have
- Docs
  - Add demo video for local dev — WAITING on Khai To (PM lead, squad modeling) to release the 2-way sync tool in holistics CLI. Demo should land after that ships so we lead with the new flow. 3-week carry-over (W15) — keep on watch but not actionable this week; revisit weekly until Khai’s release ships.
- Personal
  - Review and update [[Personal Context]] (new in backlog this week).
  - Research 1Long alternatives for emergency savings (decide if migration is worth it).
  - Continue Obsidian → Logseq notes migration.
- Teaching
  - Find a football dataset for Duc Anh. Carry-over.
- Read
  - Wes Kao — Levels of detail in communication.
  - Modeling Patterns docs (Presales).
Backlog (deprioritized, do not pull unless P1/P2 slate is clear)
- Internal: DAT-524 Fix excluding internal Zoho accounts — 12 weeks carry-over. Action this week: raise in next 1-on-1 to formally drop or assign owner.
Focus days suggestion
- Mon (May 4): GitHub App for bi.holistics.io (quick win, scope first). BuyCo Slack sweep + thread chases. PR reviews: CircleCI dbt #858 + dbdocs #860 round 2. 1Win Zoho check (1h timebox)
- Tue (May 5): DAT-555 + DAT-556 small wins. Basata catch-up call (sync with Taha on dual-dashboard plan). 15-min BuyCo sweep.
- Wed (May 6): MRR exchange rate continued. 15-min BuyCo sweep.
- Thu (May 7): BI cleanup. MRR exchange rate deep work — design dim_exchange_rates, pick rate source, write Linear scoping comment + small POC.
- Fri (May 8): Wrap-up + W19 weekly report.
- Sat–Sun (May 9–10): H1 self-reflection draft + CV refresh for the upcoming 2026 H1 performance review. Skip Smartclass commits. Keep at least Sat morning slow.

Carry-over watch

Item	Since	Weeks	Action
DAT-524 Fix excluding internal Zoho accounts	W7	12	Raise in 1-on-1 — formally drop or assign owner
DAT-560 Lead Funnel by Sales Motion	W14	5	30-min unblock-or-backlog pass; do not let drift
Demo video for local dev docs	W15	4	WAITING on Khai To 2-way sync CLI release; revisit weekly
DAT-576 MRR exchange rate	W16	3	Forcing function: Mon AM hard block
DAT-555 follow-up	W18	1	Mon PM
DAT-556 dbt test fix	W17	2	Mon PM
Wamly onboarding call	W18	1	WAITING — Farren on 10-day paternal leave; Chukwudi reaches out ~May 11–15
1Win Zoho check	W18	1	Wed 1h timebox
BuyCo triage follow-through	W19	1	Daily 15-min Slack sweep + chase PM replies

Health rules (continuing from W17 LEARNING)
- No gaming after 18:00 on weeknights (W17 commitment — verify it held this week).
- 3x short night jogs this week (post-work, lower-temp window) — direct response to W18 badminton breathlessness signal.
- Eat before exercise. No empty-stomach badminton.
- Weekend booked for H1 self-reflection + CV refresh — skip Smartclass commits to avoid two-in-a-row non-rest weekends.
Principles to apply this week (from W18 LEARNING)
- Vague task → time-block + decompose to smallest concrete next step (Wait But Why).
- Customer ask → frame as “here is the recipe, happy to pair if helpful” rather than “I’ll do it for you”.
- Small P1 ships before big P2 context-switch (do not let cheap items slip when escalations land).
- Daily journals are 100% me. LLM only for boilerplate.

Weekly Planning - 2026-W20

Mon, 25 May 2026 00:00:00 +0000

Plan for week W20 (May 11 – May 17, 2026)

Big W19 wins: DAT-560 Lead Funnel by Sales Motion (5-week carry-over) + DAT-555 follow-up both closed. Big risk W20: DAT-576 MRR exchange rate now 4-week carry-over — Hieu left, treat as restart. Mon = context recovery, not implementation. Showbie synthesis owed. Wamly back mid-week (Chukwudi ~May 11–15). [[Basata]] onboarding call 4 Tue May 19 (W21 — prep Fri).

P1 – Must Do
- Internal
  - MRR exchange rate restart (DAT-576) — 4-week carry-over, manager priority. Treat as restart — Hieu left, implementation context lost. Mon AM = context recovery pass (re-read [[[Internal] Customers’ MRR (Exchange Rate)]], DAT-177, Notion docs; trace fct_daily_mrr.exchange_rate_to_sgd upstream in dbt). Mon PM = 30-min sync w/ anh Triet (recover his earlier experiment, decide rate source, decide backfill stance). Tue = draft dim_exchange_rates schema + ECB approach in Linear (no code). Wed = POC ingest if scoping signed off. Escalate to anh Triet by Wed EOD if blocked.
  - Close out CircleCI dbt PR #858 review for anh Dong — IN-PROGRESS, awaiting next review request (Ampcode). Respond same-day.
- Presales
  - Showbie loss synthesis + chase Harsha for personal feedback — slipped from W19 Wed. Block 2h Wed AM. Output: 1-page Holistics-vs-Omni learning note (focus on Looker-migration moat + security risk perception) + outreach to Harsha. Apply The Mom Test questioning style.
  - Bicycle Transit follow-through — relay Microsoft Fabric DW question to anh Huy Vu (modeling). Confirm SSH algo (RSA only, no Ed25519) for Azure DevOps catch.
- Docs
  - Add demo video for local development docs — P1 in [[Backlog]]. Still WAITING on Khai To’s 2-way sync CLI; do scenario draft + discuss with anh Huy Vu/Dat. Set scoping by Wed.
P2 – Should Do
- Personal
  - H1 self-reflection draft + CV refresh for 2026 H1 performance review — block Sat May 16 + Sun May 17 for deep work (slid from W19 weekend due to DAT-560 push).
- Internal
  - DAT-499 — Increase impersonation-lookup data freshness. Manager-elevated context.
  - Continue Cross-Model Calculation (DAT-504, [[Backlog]]). Re-evaluate timing post-DAT-576 kickoff.
  - Upgrade dbt-core of repo dbt to match prefect.
- Presales
  - Wamly onboarding call — re-pick around May 11–15 per the reschedule thread. When Chukwudi reaches out, schedule + send trial-extension request (Farren’s trial expired May 6).
  - Prep for [[Basata]] onboarding call 4 (Tue May 19) — sync with Taha on dual-dashboard plan + dark-mode follow-up. Block 2h Fri.
- Docs
  - Send the auto-export dashboard PNG feedback to Khai To (currently draft in [[Backlog]]). Send once 2-way sync CLI ships, otherwise polish + hold.
P3 – Nice to Have
- Personal
  - Auto-format execute_aql JSON → markdown amp plugin — queued IDEA from W19 (Ampcode). 1-day timebox.
  - Daily Slack ingest cronjob POC — see W19 IDEA. Use slack-cli activity. Read-only first, no transform.
  - Migrate journal notes from Obsidian (in-progress).
- Teaching
  - Set-based vs row-based thinking exploration; visualization resources research.
Backlog (deprioritized, do not pull unless P1/P2 slate is clear)
- Internal: DAT-524 Fix excluding internal Zoho test accounts — 13-week carry-over. Action this week: raise in next 1-on-1 to formally drop or assign owner.
Focus days suggestion
- Mon (May 11): MRR context recovery (09:00–12:00 hard block) — re-read MRR knowledge page + DAT-177 + Notion docs; trace fct_daily_mrr.exchange_rate_to_sgd upstream. PM: 30-min sync w/ anh Triet on rate source + backfill. BuyCo daily sweep.
- Tue (May 12): MRR — draft dim_exchange_rates schema + ECB approach in Linear comment, tag Sriram + Vincent. Bicycle Transit follow-through (Fabric DW Q to anh Huy Vu, SSH algo confirm). Address CircleCI dbt #858 if review lands.
- Wed (May 13): MRR POC (1-month ECB ingest) if scoping signed off OR escalate to anh Triet. Showbie synthesis (2h AM). DAT-499 design pass.
- Thu (May 14): DAT-504 re-evaluation. Demo video scenario draft (Docs). 1-on-1 — raise DAT-524 backlog drop.
- Fri (May 15): [[Basata]] call 4 prep (2h). Wrap-up + W20 weekly report. Auto-format AQL plugin (P3) if time.
- Sat–Sun (May 16–17): H1 self-reflection draft + CV refresh for 2026 H1 performance review. Skip Smartclass commits.

Carry-over watch

Item	Since	Weeks	Action
DAT-576 MRR exchange rate	W16 (Apr 13)	4	Restart — Hieu left, context lost. Mon AM = recovery pass. Wed EOD = decision point: POC or escalate to anh Triet.
CircleCI dbt PR #858 review	W18 (Apr 27)	2	IN-PROGRESS — respond same-day to next review request.
Wamly onboarding	W18 (Apr 27)	2	Customer-side block (paternal leave). Re-pick May 11–15.
Add demo video for local dev docs	W17 (Apr 20)	3	Scenario draft this week regardless of CLI ship.
DAT-524 exclude internal Zoho accounts	W7 (Feb 9)	13	Raise in 1-on-1 to formally drop or reassign.
Showbie loss synthesis	W19 (May 4)	1	Block Wed AM.

Weekly Planning - 2026-W21

Mon, 25 May 2026 00:00:00 +0000

Plan for week W21 (May 18 – May 24, 2026)

Progress vs plan (as of Tue May 19)
- DONE:
  - Power BI playbook — published to docs (conceptual-differences, migrating-to-holistics). POC end-to-end migration via Claude Code + custom skill.
  - BuyCo onboarding call (Tue May 19) — closed. Tech onboarding checklist in Notion. Hide-confidential-data POC kicked off.
  - Basata onboarding call 4 — closed.
  - Enhance Fitness call watched + RFP assessed.
  - Cross-metric calculation doc review (carry-back, #P2).
- IN PROGRESS / WAITING:
  - migrate-power-bi AI skill PR (holistics/skills#10) — awaiting anh Khai review.
  - BuyCo SLA / response-time data pull (new TODO from call) — P1, scheduled Thu.
- NOT STARTED:
  - DAT-576 MRR exchange rate — escalation Wed 1-on-1 (as planned).
  - DAT-524 Zoho test accounts — escalation Wed 1-on-1.
  - Local-dev demo video (Docs P1) — Thu.
  - Auto-export PNG feedback to Khai To — Thu.
  - Wamly check — Wed.
  - H1 self-reflection + CV — locked Sat/Sun.
  - Soạn roadmap Spark cho Yên — Sat AM.
  - Lead Funnel retro — Fri.
- NEW (added mid-week):
  - TODO Discuss narrative demo for Power BI migration (Slack) — P2, Wed.
  - TODO Write 1-on-1 report — P1, Wed (paired with 1-on-1).
  - IDEA Support other coding agents for logseq automation ([[Logseq]]).
  - NOTE Identity Resolution TOGA case — captured under [Internal] Identity Resolution.

Big W20 wins: CircleCI PR review marathon closed (3-week carry-over cleared); BuyCo theme rolled out; Khai To’s 2-way sync CLI shipped → local-dev demo video unblocked (was 5-week WAITING). Big risk W21: BuyCo onboarding call Tue May 19 — Power BI playbook must be review-ready Mon EOD. Bigger risk: DAT-576 MRR exchange rate now 5-week carry-over — stop scheduling, start escalating. 1-on-1 has two backlog drops to make (DAT-576 re-scope, DAT-524 formal drop). H1 self-reflection + CV 2-week slipped — lock the weekend.

Weekly Planning - 2026-W22

Mon, 25 May 2026 00:00:00 +0000

Plan for week W22 (May 25 – May 31, 2026)

W21 closed strong: PBI playbook + skill (v0.1 → #12 fix → v0.1.1), BuyCo/Basata onboarding, EF RFP assessed, SLA pull, 3 Docs PRs. W22 slate lighter — 4 presales items demoted to Monitor (sales already followed up OR customer says not critical). Focus shifts to: (1) DAT-576 written-decision memo Mon AM → unblocks DAT-524, (2) Showbie loss synthesis (3rd re-commitment), (3) H1 self-reflection (3-week slip, PR cycle), (4) RFC-0004 PARA W22 batch (forcing-function test on DAT-576/DAT-524).

Weekly Planning Rules

Mon, 25 May 2026 00:00:00 +0000

Weekly Planning Rules

Living rules for pages/Weekly Planning - YYYY-WNN.md. Pairs w/ [[Priority Rules]] (P0–P3 tiers). Re-read every Fri wrap-up. When a rule causes friction, capture friction below + iterate.

1. Principles (apply every week)
Decisions in writing beat decisions in conversation — meeting w/o written outcome = no outcome. Same-day Linear/Notion/Project-page update.
Sales-led customer touches → my action only when trial/onboarding booked — if sales (Nam, Chukwudi, etc.) already followed up, don’t manufacture parallel work. Move to Monitor.

Weekly Report - 2026-W09

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Feb 25 – Mar 1, 2026

Work

Presales

Highlight: Trust Wallet win story — won over from Looker/Tableau. Trust Wallet (crypto wallet, Databricks stack) subscribed on Standard plan (Feb 4). High-touch onboarding was the key differentiator: live enablement on Model → Dataset → Dashboard flow, tackling struct fields, typing, and caching/pre-aggregation for Databricks cost concerns. Strong proof point for the high-touch onboarding initiative.

Internal

DONE Setup BigQuery CLI skills — enables querying BigQuery datasets directly from the terminal.

Teaching

Weekly Report - 2026-W10

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Mar 4 – Mar 7, 2026

Pull Request: #6

Friday comprehensive report for 2026-W10. Activity concentrated Feb 25 – Mar 3 (journal entries), with PR review follow-ups continuing Mar 4–6.

Work

Add2Cart
(done) Fix the temp bridge table — eliminated bridge_product_retailer by adding retailer_id directly to atc_price_history via slug normalization. Reduced join path from 4 tables to 2–3 for price queries. Backfilled 30M+ rows: 23/40 retailers matched cleanly (40% of rows), 6 near-misses identified for follow-up. Stored procedures updated; sp_run_all reordered. Holistics AML dataset relationships updated to use direct retailer_current_pricing_skey join. (Notion)

Weekly Report - 2026-W11

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Mar 9 – Mar 13, 2026 (friday mode)

Pull Request: #7 and #8

Work

Internal
(done) Code review MRR PR #812 — completed 4 review rounds on customer identity resolution refactor (DAT-471). Decomposition of itg_mappings__customer_identities into 5 sub-models. Identified critical issues: Zoho-only rows silently dropped by WHERE clause, NULL domain NOT IN semantics, Zendesk fan-out risk. PR merged Mar 10. (PR #812)
(done) Continue commenting DE-201 (PR Workflow enhancement) — completed review and documentation of CI/CD gaps in internal-aml-project repo. Proposed tiered roadmap: quick wins (PR templates, CODEOWNERS), expanded test coverage, new automation (lineage diff, impact analysis). (Notion)

Weekly Report - 2026-W12

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Mar 16 – Mar 22, 2026 (friday mode)

Work

Internal

DONE Migrate Census to Fivetran — Completed migration of reverse-ETL syncs (BigQuery → HubSpot) from Census to Fivetran Activations before the April 1 deadline. Two syncs migrated: dim_contacts → HubSpot Contact and fct_customer_stats → HubSpot Company. Validated MAR stays within free tier limits (~1,215 records/month vs 3,500 limit). Follow-up noted for next week: check Census usage estimate to confirm free tier eligibility.
- Slack · Notion
DONE Review monitoring dashboard DE-187 — Reviewed PR #60: “Add subscription monitoring dataset and dashboard for customer identity tracking” (merged).
DONE Check #data-ops-bot on viz_settings from PR #842 — Fixed duplicate snapshot names for viz_settings (PR merged Mar 17).
- Slack
DONE Continue commenting the project DE-201 (PR Workflow enhancement) — Finished laying comments on the PR Workflow spec. Focus was on things needed during PR preview to facilitate reviewing; anything that doesn’t help confidence in approving a PR is out of scope.
- Notion
DONE 1-on-1 meeting with manager (anh Triet) — Key concerns discussed: (1) integrating AI into the data team’s development experience, (2) current data infra/pipeline complexity and trust issues, (3) PR Workflow adoption. Wrote up 1-on-1 report.
DONE Understand the MRR data flow — Clarified that the revenue planning logic is produced from DTS100 and DTS106. Confirmed it is adequate to reproduce these sheets inside Holistics, but will temporarily defer in favor of adding a sales motion dimension first. Next step: ingest Calendly data into the warehouse.
- Slack · Linear DAT-560
IN-PROGRESS Check failed dbt tests & create Linear issues — DAT-554 fixed (Elementary dbt test n_records column missing, PR #841). DAT-555 still open: fct_job_queue_performance model is stale and likely to be removed; mart_product__dataset_datamodel_dimensions also under review. Several skipped downstream models identified: itg_customer_support__organizations, mart_customer_support__organizations, mart_product__activities, and others.
IN-PROGRESS Think about applying AI into resolving #data-ops-bot issues — Drafted an approach: pick a task → resolve manually → write detailed guide → let agent attempt → iterate. Then materialize as a reusable skill. Delegation strategy: routine dbt test fixes can go to juniors (Thuan) or agents.
- Notion RFC
TODO Prepare for phase 2 MRR problem — Upcoming. First step: ingest Calendly data.
TODO Ingest Calendly data — New task, supports the MRR analysis.
TODO Think about how a normal data team would adopt a BI chatbot — Exploring candidates (e.g., nao).

Presales

DONE Onboarding call with Showbie — Completed Mar 13.
DONE Debrief the last call with Showbie — Key learnings: try out Calculation Builder for immediate use in calls; identified need to improve call quality by studying past calls led by Huy/Vincent.
- Slack · ReadAI
DONE Showbie use case — embedded dashboard QA — Scoped requirements: Showbie PM needs a staging/approval workflow for embedded dashboards. Discussed with team (anh Tai / Huy) and decided on the approach: PM previews via Development → Embed Portal link; dashboard changes on a branch reflect in the embed preview without needing a second tenant (saves ~50% cost). Solution documented and shared.
- Slack discussion · Slack output
TODO Onboarding call 3 with Basata — Scheduled.
- Slack

Duty Support

TODO Support Sasha mybacs — New support request.

Personal / Tooling

DONE Smartclass v0.2.4 release — Fixed 6 bugs from code review: non-contiguous question ID validation, missing FK cascades, non-atomic exercise writes, test isolation (isolatedStorage: true), R2 stream consumption, and schema docs. (Release)
DONE Add shadcn/ui skills — Integrated shadcn/ui skill from the official repo into the agent-skills system. Synced remote skill files and created symlink. (PR #13)
DONE Add 1-on-1 automation report in Logseq — Set up the 1on1-report.sh automation for generating retrospective reports from Logseq notes.
IN-PROGRESS Complete Brazilian dashboard on Metabase for Yen — Dash 1 (Sales Overview) done; Dash 2 (Shipping Overview) and demo video still TODO.

Learning & Notes

Risk-based testing in dbt — Read Vinted Engineering article on tagging dbt models with high/low risk and frequency, then running tests selectively based on those tags.
Claude Skill Building Guide — Read Anthropic’s guide. Key takeaway: skill description should cover what it does, when to use, when not to use.
AI and labor — Reflected on the Oxygen Not Included DLC analogy: bionic dupes (robots) consume less oxygen and survive harsh environments but require lots of power. Like AI in our era — not ideal for early/simple work, but excellent for extending reach. When AI handles its strengths well, humans should double down on theirs.
1-on-1 meetings — Read notes from The Manager’s Path: 1-on-1s are a chance to nurture the team/organization’s human resource.
Work ownership — “Làm việc bằng cái tâm” — treating company work as your own leads to better responsibility, empathy, and quality in everything.
Presales self-reflection — Calls are not yet at expected quality. Plan: replay past calls led by Huy/Vincent, pause at prospect questions, answer first, then watch how they handled it, and take learning points.

Next Week

P1 Onboarding call 3 with Basata — Presales, scheduled.
P1 Support Sasha mybacs — Duty Support, new request.
P2 Ingest Calendly data — Internal, prerequisite for phase 2 MRR analysis.
P2 Prepare for phase 2 MRR problem — Internal, depends on Calendly ingestion.
P2 Review and make a plan for MRR lead funnel / sales motion dimension — Internal, carry-over.
P2 Check back Census usage estimate (free tier confirmation) — Internal, noted for Mar 26.
P2 DAT-555 resolution — Internal, carry-over. Decide whether to remove fct_job_queue_performance and write Notion doc for team review.
P2 Fix excluding internal testing Zoho accounts — Internal, backlog item (DAT-524).
P2 Document Medenterprises performance use case — Duty Support, backlog (was due Feb 5).
P2 Brazilian dashboard Dash 2 + demo video for Yen — Teaching, carry-over.
P3 Search for a YouTube summarizer tool — Personal, backlog.

Career & Personal Consulting

High output on infrastructure and process work: Census migration, PR #842 fix, dbt test triage, PR Workflow comments, and 1-on-1 report automation — all completed this week. This is solid foundational work, but it’s predominantly maintenance/infra. The MRR analysis (the higher-leverage, revenue-impacting project) progressed only on understanding the data flow. Next week, carve out focused time for the Calendly ingestion and phase 2 planning.
Presales is growing: You handled the Showbie embedded dashboard QA use case end-to-end — from scoping requirements to discussing with the team and arriving at a cost-effective solution. That’s a full presales cycle for a technical use case. Keep building this muscle.
Delegation thinking is maturing: The AI-for-data-ops-bot idea and the explicit framework (pick task → resolve → document → let agent/junior try → iterate) shows good leadership instinct. Follow through by picking one DAT issue next week and running the first cycle with Thuan or an agent skill.
Self-awareness on call quality: Identifying that your presales calls aren’t at expected quality and devising a concrete practice plan (replay + pause + compare) is a strong move. Prioritize doing this for at least one past call before the Basata onboarding.
Context switches remain high: This week touched Internal, Presales, Duty Support, Personal, Teaching, and Smartclass. The 1-on-1 with anh Triet also surfaced concerns about pipeline complexity and PR Workflow adoption — both requiring sustained attention. Consider limiting to 2–3 project contexts per day next week.

Weekly Report - 2026-W13

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Mar 23 – Mar 28, 2026 (friday mode)
Work
Internal
DONE Investigate failed dbt assets in #data-ops-bot (DAT-569)
- Triggered by bot alert in #data-ops-bot: 4 not-null tests failing (24 + 9 null rows across mart_event__drill_down and mart_event__view_underlying_data).
- Root cause: dbt Mart Snowplow Events job ran before dbt Mart Product (which builds dim_users), causing null tenant/user IDs. Secondary bug: LEFT JOIN to internal_tenants incorrectly passed internal events when user was missing from dim_users.
- Fix: refactored SQL to pre-extract IDs from Snowplow event properties with coalesce fallback. Wrote Notion investigation doc (DE-207) with debugging guide for juniors.
- LEARNING 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).
DONE Review Thuan’s work on DE-208 / mart_product__dataset_datamodel_dimensions (PR #845 — OPEN)

Weekly Report - 2026-W14

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Mar 30 – Apr 5, 2026 (friday mode)

Work

Add2Cart

DONE Eliminate bridge table (bridge_product_retailer) from Redshift pipeline and Holistics AML layer
- Completed all 5 phases of the migration plan (Slack thread):
  - Phase 0: Snapshot baseline tables (_migration_baseline, _bridge_backup) created on Redshift.
  - Phase 1: Added retailer_id + retailer_current_pricing_skey columns to atc_price_history, backfilled ~27M rows (75.7% coverage). Known gap: 8,713 keys from Chemist Discount Center slug mismatch — documented.
  - Phase 2: Deployed 5 updated SPs (sp_refresh_daily_prices, sp_refresh_atc_price_history_enrich, sp_run_all, sp_refresh_price_history_from_s3, sp_validate). Ran sp_run_all() — enriched table validated at 12.1M rows, join path works without bridge.
  - Phase 3: 7 commits on feat/eliminate-bridge-aml — removed bridge from all 4 datasets + market_price_rank model, added direct rcp_skey relationships, deleted agg_retailer_product_price model. Pushed to Holistics, dashboards verified.
  - Phase 4 (soak): Monitored dashboards end-to-end through bridgeless path — no issues.
  - Phase 5 (cleanup): Dropped bridge/agg tables + SPs, deleted bridge AML model, cleaned up migration artifacts. PR #2 merged. Shared completion summary with Anurag in Slack. Bridge kept as _bridge_product_retailer_backup (frozen, 222K rows) for reference. Remaining data quality items (near-miss slugs, missing retailers, history-only) handed off to Anurag.
- Impact: Simplified join path from master_product → retailer_current_pricing → bridge → atc_price_history to master_product → retailer_current_pricing → atc_price_history (one fewer hop), improving query performance.
WAITING Guidance for countries-level data ingestion (Notion D4 doc)
- Investigated multi-country retailer ingestion from 6 RDS databases (airbyte_schema_*). Found critical price_history_skey collision: 2,774 keys collide across countries (39,710 rows), mainly Watsons across SG/ID/MY.
- Decision: Holistics will not implement the ingestion. Created D4 guidance document with two approaches evaluated: (1) Dynamic Schema (separate Redshift schemas per country, switch via User Attributes) — recommended for Add2Cart; (2) Consolidated Schema (UNION ALL + RLP). Added Mermaid diagrams, comparison table, collision detection SQL, SP impact matrix, and AML examples.
- Feedback: initial version was too detailed on implementation. Rewrote to lead with “what needs to be done” and high-level approaches first. Waiting for anh Huy to review.
- Aligned with Anurag on Slack: he ingested retailers for all countries into Redshift.

Presales

DONE Study Jonas Chorum onboarding call 1 (Notion prep note)
- Hotel PMS company (~1,000 properties), non-multi-tenant (each customer = separate DB on self-hosted SQL Server). Key use cases: natural language querying over reservations, embedded analytics as paid add-on, dynamic data source for per-hotel routing.
- Answered tunnel/bastion server question in Slack — they ran Windows script instead of Linux, connection error escalated to support team (Tien).
- anh Huy led the call, I sat aside to assist. Decision from team review: known limitation on cross-database aggregation, need to clarify further with customer.
DONE Refactor Erin (Showbie) dashboard — Chukwudi had a fever, asked for help via Slack to refactor from query models to decoupled AQL metrics. Huddled with anh Dong, then handed over to him for the call.
DONE Onboarding call 2 with Basata (Taha) (ReadAI transcript, Slack debrief)
- Good sentiment with Taha. Key feedback: creating single dashboard + embed portal flow isn’t seamless, needs to be easier to understand. Question: “any best practices to make the embedded dataset easier for business users to use?” — introduced Custom View feature. Embed Portal vs Single Dashboard distinction remains a point of confusion.
- Embed portal tutorial already delivered: Notion guide, shared in #presales-sa Slack. Taha’s backend colleague to begin portal embedding.
TODO Onboarding call 1 with Jonas Chorum — vibe-coding a dynamic data source demo. Built POC showing data_source_name in AML routing per-hotel queries via JWT user attributes. Limitation identified: cross-database aggregation (50-60 DBs) requires a data mart. Moved to Apr 6.
TODO Polish embedding documentation — formalized as P2 backlog item. Will ask anh Tai and anh Huy next week to clarify scope and whether to own this. Friction observed across Showbie, Superbexperience, Basata, and Jonas Chorum.
NOTE Presales capacity: anh Huy is deliberately stepping back from leading calls, delegating to team (me, anh Dong, Chukwudi, Mario) to build team capacity. The expectation is thorough preparation before every call.
NOTE Presales load continues to increase: Jonas Chorum, Showbie, Basata active this week. The embedding use case is becoming the dominant pattern — 4 of last 5 customers need embedded analytics.

Internal

DONE Thuan’s PR #845 (DE-208 / mart_product__dataset_datamodel_dimensions) — MERGED. Fix for PARSE_JSON syntax error. All CI checks passed after review rounds in W13.
DONE Review DE-206 for anh Hieu — exchange rate document review completed. Notion doc and Slack thread.
DONE Visualize schedule of all data lineage (Notion: Data Pipelines Schedules)
- Created full Mermaid flowchart of the entire pipeline: Extract & Load (21:30–23:55 VNT) → Domain Transforms (00:20–00:55) → Mart Transforms (00:15–01:35) → Post-Transform (01:35–08:00). Mapped all cron schedules from prefect.yaml, dbt model dependencies via ref() calls, and Airbyte sync frequencies.
- Key finding: mart_event depends on mart_product (specifically mart_product__users and mart_product__dashboard_widgets), but runs weekly on Monday 00:15 before the daily product mart at 01:10. Safe because mart_event doesn’t use the + prefix (reads existing BigQuery data, no upstream rebuild).
DONE Check Zendesk tenant Inovonics (DAT-571)
- Investigated why tenant US-1099511640417 wasn’t mapped to Zendesk org in analytics. Traced through itg_mappings__zendesk_tenant → HubSpot domain mapping → Zendesk organizations table.
- Root cause: Airbyte Zendesk source connector (source-zendesk-support:0.2.6) has a pagination bug capping ingestion at 10,000 records. The raw organizations table had exactly 10,000 rows; 680 of 911 org IDs in tickets were missing.
- Recommendation: Upgrade Airbyte Zendesk connector to fix pagination.
DONE Add CI to validate Holistics AML project (PR #67 — MERGED)
- Triggered by a silent semantic conflict: PR #63 (Hieu) added a dashboard depending on domain_hubspot_companies, and PR #64 (Thuan) deleted that model. Git didn’t flag it because they touched different files.
- Implemented GitHub Actions workflow using Holistics Validation API to validate AML syntax and references on every push.
DONE Attended Product Office Hours P1 and P2 (Notion newsletter)
- Noted: AI theme builder tool at holistics.h-theme-builder.pages.dev/theme-builder — will try with more prospects.
- New dataset exploration UI looks promising.
- Data team should contribute to Holistics skills and internal-skills repos.
TODO Create agent skill for fixing dbt data pipelines for #data-ops-bot — carry-over from W13, not started.
TODO Fix excluding internal testing Zoho accounts (DAT-524) — carry-over since W7, not started.
TODO Calendly data pipeline (DAT-283) — carry-over, not started.

Docs

TODO Polish embedding documentation — increasing embedding leads make this urgent. Same item tracked under Presales.
WAITING Add demo video for local development docs — waiting for team to trigger.

Logseq

DONE Add project glossary (PR #13) — created canonical project list in pages/Projects.md.
DONE Improve backlog structure and automation query pre-processing (PR #12).

Personal / Tooling

DONE Changed to a more professional work avatar.
DONE Edit video last Hue Trip — completed on Saturday.
DONE Sao kê (personal finance task).
DONE Settled on mochi.cards as Flashcard app for learning English words.
Installed Annotate — free on-screen annotation tool for customer demos and screen recordings. Lightweight alternative to paid tools.
Discovered Pebble Index 01 — smart ring for quick voice notes. Interesting for capturing ideas on the go.
Found Vietnam Real Estate Dataset on HuggingFace — potential hobby data analysis project.
Note: Logseq automation is compounding — helps retain historical context across projects, improving performance in sync calls and connecting dots. The second reason for feeling productive this week.

Learning & Notes

Watched How to Present a MIND-BLOWING Software Demo — key takeaways: recap slides (fact → problems → criteria → new findings), speak customer’s language (airline = passengers, SaaS = users), confirm what they care about before demo, use cases > features, have an assist person, send personalized recap to each audience member. Applied learning to Jonas Chorum call prep.
Read How to teach technical concepts with cartoons by Julia Evans — guide on visual teaching. Potential application for Kindle Scribe. Follow-up from W13 recommended resource on “implementation challenges.”
Read Details aren’t the problem. The problem is too many of the wrong details by Wes Kao — levels of detail in communication. Completed from W13 recommended resources backlog.
LEARNING Single-tenant vs Multi-tenant architecture patterns — relevant context for Jonas Chorum (single-tenant: infra duplicated per tenant) vs most other customers (multi-tenant: shared infra, logical isolation). Understanding this distinction is critical for presales scoping.
LEARNING Country names follow a people + land pattern: Iceland, Greenland, England, Switzerland, Finland, Kazakhstan, Uzbekistan (stan = land).
NOTE Good observation from anh Huy: “If I just stay in the call, everyone can’t improve. The only thing that makes sense now is to force the team to prepare very well before the call.” Leadership by stepping back.
NOTE Increase Calendly pipeline task to top priority next week — noted on Thu.

Next Week

P1 — Add2Cart: Project retro with anh Dong — review the full bridge elimination + countries guidance work.
P1 — Presales: Onboarding call 1 with Jonas Chorum — finalize dynamic data source demo, address cross-database aggregation limitation.
P1 — Internal: Calendly data pipeline (DAT-283) — elevated to P1 per Thu note. Standardize source pipeline and build unified dbt models.
P2 — Internal: Create agent skill for fixing dbt data pipelines in #data-ops-bot — carry-over from W13.
P2 — Internal: Fix excluding internal testing Zoho accounts (DAT-524) — lingering since W7. Timebox 2h or explicitly deprioritize.
P2 — Internal: Follow up on DAT-571 (Zendesk Airbyte connector upgrade) — ensure pagination fix is scheduled.
P2 — Docs: Polish embedding documentation — ask anh Tai and anh Huy to clarify scope. Write step-by-step embed portal setup guide.
P2 — Add2Cart: Get anh Huy’s review on the D4 countries guidance document.
P3 — Presales: Read Modeling Patterns docs.
P3 — Personal: Self reflection and update CV.

Career & Personal Consulting

Progress Review (Start/Stop/Keep):

Weekly Report - 2026-W15

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Apr 6 – Apr 12, 2026 (friday mode)
Work
Internal
DONE Fix failed dbt tests — snowplow events (DAT-569)
- Both PRs merged and deployed: dbt #848 and prefect #393.
- Ran backfill and snowplow pipeline — all runs successful. Confirmed via Prefect flow runs (snowplow, backfill).
DONE Check Zendesk — Tenant Inovonics (DAT-571)
- Triggered by Vincent’s Slack message: Zendesk Customer Support dashboard showed 0 for Inovonics. Traced full lineage from fct_zendesk_tickets → itg_mappings__zendesk_tenant → stg_zendesk__organizations → _airbyte_raw_organizations and found org 13430326317849 missing entirely.
- Root cause: Airbyte Zendesk connector v0.2.6 uses offset-based pagination capped at 10K records by Zendesk API. Raw table had exactly 10,000 rows; 680 of 911 org IDs in tickets were missing. Entire downstream lineage from staging to mart was broken.
- Wrote upgrade plan evaluating 3 options: (1) Upgrade Airbyte platform v0.35 → v2.0 (fixes root cause for all connectors, but high DevOps effort + risk to HubSpot syncs during migration), (2) Rebuild in Prefect (data-team-only, orgs-only ≈ 2–3 days), (3) Use Fivetran (managed SaaS, ≈ 2–3 days, requires refactoring all stg_zendesk__*.sql models). Waiting for review.
- Interim fix applied: manually upgraded connector in Airbyte UI to v2.6.6. Vincent confirmed dashboard now shows data. Long-term Airbyte upgrade tracked as a Linear project.
WAITING DAT-555 — Fix fct_job_queue_performance BigQuery resource limit (DAT-565)

Weekly Report - 2026-W16

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Apr 13 – Apr 19, 2026 (friday mode)
Work
Internal
DONE Transfer MRR and exchange rate project with anh Hieu — completed Apr 14
- Walked through DE-187. Two main blockers: (1) customer identity resolution — dbt logic refactored but domain mapping remains unreliable; (2) exchange rates — Zoho uses static rates set at plan creation time, finance team pivoting to bi.holistics.io as MRR source of truth.
- Decision: use USD as reporting currency with live exchange rates (Option 2). Recommendation to move toward period-average constant currency (Option 3) for trend analysis.
- Created dedicated knowledge page [[[Internal] Customers’ MRR (Exchange Rate)]] with data architecture diagram, ER diagram (dbdiagram.io), 9 identified problems, edge cases (Datacubed multi-tenant, Kognity multi-region, Vector AI domain mismatch), and technical fixes (PR #812, PR #852).
- Next steps: build dim_exchange_rates table (DAT-576), implement dual metrics (constant_currency_mrr + reported_mrr), implement canonical customer_skey for long-term identity resolution.
- Related: dbt monitoring flow DE-176 suspended (low priority), impersonation lookup frequency increase (DAT-499) pending.
DONE Investigate Zoho Events sync 403 failure (DAT-574) — completed Apr 14
- Prefect flow Sync Zoho Events failed Apr 12 with HTTP 403 (Zoho error code 104003) — OAuth token lacked ZohoSubscriptions.events.READ scope after Finance (Vincent, Sriram) adjusted admin permissions for Janice’s account.
- Root cause: permission/scope issue, not a code bug. Coordinated with Quinn (Growth) who updated read permission. Flow re-ran and backfilled successfully.
DONE Write 1-on-1 report — completed Apr 15, PR #16. 1-on-1 meeting held Apr 15.
- Manager’s priorities for Internal (in order): (1) data quality/reliability — MRR identity + exchange rates; (2) bi.holistics.io cleanup; (3) increase data freshness (e.g., impersonation lookup); (4) product tracking; (5) development workflow.
- Embed demo app proposal: not the right timing. Mentoring Thuan: ask open questions, force him to think.
DONE Fix fct_job_queue_performance BigQuery resource limit (DAT-555)
- PR dbt #854 approved by marcusle02 and merged Apr 15. Capped incremental lookback to 7 days.
- PR review done. Backfill completed. Now proceed to clean up BI layer.
- Dashboard cleanup decision: delete [WIP] Job Queue Performance 3.0 (unused), keep v2 and Report Job Queue Performance Monitoring (migrate to 4.0).
- Related sub-tasks DAT-567 (delegated to Thuan, done) and DAT-575 also completed.
IN-PROGRESS Calendly data pipeline (DAT-283)
- PR dbt #853 approved by marcusle02 on Apr 17 after multiple review rounds. PR is mergeable, awaiting final merge.
- Answered all review comments from anh Dong (marcusle02). Key feedback addressed: enable deprecated wrapper models for transition, avoid SELECT * in CTEs, fix tracking_utm_content data type.
- Re-modeled into fact bookings and dim event, with grain = event × invitee × rep.
- Lineage analysis completed: 2 domain + 3 redundant mart models consolidated into 1 domain (dom_calendly__events) + 1 mart (fct_calendly_events). Source migrated from Google Sheets to Fivetran. Bug fix: fct_sales_leads was dropping 88% of call-booking leads due to NULL UUIDs in Google Sheets — now joining on invitee_email_domain from Fivetran source. Impacts 10+ downstream dashboards (Leads Analytics, Sales Performance, Deal Activity, etc.).
- Next: merge PR, run dbt models, validate data in Holistics BI, then fix downstream fct_sales_leads join.
DONE Guidance for countries level data (Add2Cart) — closed Apr 17
- Add2Cart won’t engage further. Closed task per Slack thread update.
TODO Handle multi-currency exchange rates for MRR (DAT-576) — new backlog item from MRR transfer. P2. Scope per Linear: ingest live exchange rates (source TBD: ECB, Google Finance, or Zoho live rates), replace static rate logic in fct_mrr, handle FX noise in historical growth metrics (pin to end-of-month rate), validate against Zoho totals. Notion doc: MRR discrepancy ~30,000 SGD between Zoho (340K SGD) and bi.h (243K USD × 1.28 = 311K SGD).
TODO Lead Funnel by Sales Motion (DAT-560) — blocked on Calendly pipeline completion. Carry-over.
WAITING Create agent skill for fixing dbt data pipelines in #data-ops-bot — demoted to P3 per anh Triet’s direction to let Thuan handle data-ops-bot for training. Revisit in 3-6 months.
BACKLOG Fix excluding internal testing Zoho accounts (DAT-524) — carry-over since W7 (10 weeks). Deprioritized: waiting for more important tasks (MRR exchange rate, Calendly) to be done first. Small task, will pick up later.
TODO Review PR Circle CI for anh Dong (DAT-579) — new. PR prefect #397: expand CircleCI test metadata ingestion (success + failed jobs), add branch fallback logic, add 60-day backfill flow. Part of DAT-578 (CircleCI pipeline revamp). Notion: DE-214 — current state uses a bash script → SQLite → report; this PR moves it to Prefect + BigQuery.
TODO Review AI sharing dashboard for Aurora — new. Enterprise customer, high priority. Slack.
- Context from Slack: Nam (Account Manager) proposed upselling Aurora a “Usage and AI Data Monitoring Transfer” package at $10,200/year. Internal debate: Phuong (Product) argued basic AI usage monitoring should be free (AI squad is building in-app dashboard); Vincent (Growth) clarified the upsell is for data sync to customer’s own systems (not in-app viewing), targeting enterprise compliance needs (e.g., 7-year log retention). Triet agreed — put it behind SCS paywall.
- Data from ClickHouse: conversation time/ID, user ID, messages (prompts + replies), token usage per user. Dashboard created by Hieu: Aurora AI Conversations.
- My action: review the dashboard quality before sharing. Confirm delivery format (Google Sheets or S3) and daily schedule.
Presales
TODO Basata follow up on light/dark theme — new. Enterprise customer, high priority. Slack.
- Context from Slack: Basata (Taha) has dark mode in their app and needs embedded dashboards to match. Current Holistics limitation: theme is set globally, not per-embed payload. Anh Huy proposed adding theme: 'light_theme' | 'dark_theme' to the embed payload. Also, Sankey chart labels don’t convert to light colors in dark theme (color palette not tied to theme). Basata says this is urgent — already rolled out embed to 3 clients, wants dark mode by end of next week.
- I told them we’ll reach out Monday with an internal plan.
DONE Onboarding call 2 with Jonas Chorum — completed Apr 17
- Feedback: (1) need Select All & Clear All in dataset; (2) make dashboard interactivity features (VUD, DD, BD) available for Explore too.
- Debriefed the call, brought feedbacks to the team.
- EAV lookup table pattern discussed during call: Tony’s one_letter_codes table is a multi-purpose lookup where same code means different things per category (e.g., ‘C’ = ‘Cancelled’ for StayStatus, ‘City’ for Ledger). Proposed 3 approaches; decided on Approach 1 (SQL Query Models with inline joins) — most reliable, avoids bloating diagram view.
DONE Presales sync — completed Apr 16
- Pivot prioritization to tutorial videos for local development docs.
WAITING Polish embedding documentation — deprioritized per 1-on-1. Not the right timing. Continue maintaining holistics-embed-demo informally.
Add2Cart
CLOSED All Add2Cart tasks closed — customer won’t engage.
- Guidance for countries level data — closed Apr 17.
- Project retro with anh Dong — canceled. Deal not progressing. Per Slack: Vincent reached out multiple times but Simon has not responded. Vincent suggests stopping service and treating remaining 50% unrecovered sprint work as an internal lesson on scoping and early commitment.
Docs
TODO Add demo video for local development docs — elevated to P1 per presales sync. Draft scenario, discuss with anh Huy Vu/Dat.
NOTE DataHub integration (holistics/datahub-holistics) — built for customer MoneySmart. Anh Triet flagged concern: data team needs to be prepared for support if customer reports an issue.
Personal / Tooling
Explored ReactFlow for vibe-coding data lineage with high-quality canvas. Also applicable for knowledge graph visualization from Logseq.
Found docglow as dbt docs alternative — prettier UI, supports column-level lineage.
Found meta-sql — data lineage graph with dependency visualization, useful inspiration for [[dblineage]].
Read articles on dbt incremental models (lookback windows, _dbt_max_partition gaps), dbt Cloud Canvas, and data ingestion tool comparison.
Considered downgrading Google One (no longer using Gemini chatbot regularly).
Reflected on context-switching cost across projects (Internal, Presales, Docs, Personal, Teaching). Considering Focus Days approach to reduce overhead.
Learning & Notes
Read “Protect Your Shed” — personal projects keep you an engineer while enterprise work teaches scale. Resonated with how side projects (like Logseq automation) maintain motivation.
Read “My AI Adoption Journey” by Mitchell Hashimoto (co-founder of HashiCorp, creator of Ghostty).
- Key concept: Harness Engineering — design better feedback loops so AI agents know when they’re wrong. The simplest form is adding rules to AGENTS.md. Already practicing this with Logseq automation.
- 6-step framework: (1) drop the chatbot, use agents; (2) reproduce your own work to learn edges; (3) end-of-day agents for warm starts; (4) outsource slam dunks while doing deep work; (5) engineer the harness; (6) always have an agent running.
- Key insight: “Turn off desktop notifications. Context switching is expensive.” Validates experience with multi-project context overhead.
- On skill formation: “discovering it yourself resulted in a stronger fundamental understanding” — applies beyond AI.
Read dbt incremental model articles: strategies (merge, insert_overwrite, append), lookback windows for late-arriving data, _dbt_max_partition gaps. Directly applied to DAT-555 fix.
Next Week
P1 — Must Do
- Duty Support: Review AI sharing dashboard for Aurora (enterprise customer). Slack. Monday priority.
- Presales: Basata follow up on light/dark theme (enterprise customer). Slack. Monday priority.
- Internal: Merge Calendly PR #853 (approved, ready to merge), run dbt models, validate data in Holistics BI. Then fix downstream fct_sales_leads join.
- Internal: Review anh Dong’s CircleCI PR prefect #397 (DAT-579).
- Internal: Start MRR exchange rate work (DAT-576) — build dim_exchange_rates with live rate ingestion. Manager priority #1.
- Docs: Add demo video for local development docs — draft scenario, discuss with anh Huy Vu/Dat.
P2 — Should Do
- Internal: Clean up BI layer for job queue dashboards (delete WIP 3.0, migrate v2 to 4.0).
- Internal: Increase data freshness — impersonation lookup more frequent than daily (DAT-499). Manager priority #3.
- Internal: Lead Funnel by Sales Motion (DAT-560) — review and plan after Calendly pipeline stabilizes.
- Teaching: Find a football dataset for Duc Anh.
P3 — Nice to Have
- Internal: Contribute to Holistics skills and internal-skills repos.
- Presales: Read Modeling Patterns docs.
- Personal: Self reflection and update CV.
Backlog (deprioritized, pick up after MRR/Calendly)
- Internal: DAT-524 Fix excluding internal Zoho accounts — small task, 10 weeks carry-over.
Career & Personal Consulting
Progress Review (Start/Stop/Keep)
- Keep: Thorough knowledge transfer documentation (MRR page with architecture diagrams, ER diagrams, problem taxonomy). This is a strong practice that makes handoffs durable. Also keep the pattern of debriefing presales calls and bringing structured feedback to the team.
- Start: Decisively backlogging low-impact carry-over items. DAT-524 formally backlogged — small task that doesn’t warrant 10 weeks of cognitive overhead. Good precedent.
- Stop: Holding onto tasks that external parties have deprioritized. Good move closing all Add2Cart tasks when it became clear the customer won’t engage. Apply this pattern to other WAITING items proactively.
Workload Observations: This week was well-balanced between deep work (MRR transfer, Calendly PR reviews) and collaborative work (presales calls, 1-on-1). The MRR knowledge page creation shows growing ownership of a complex domain. DAT-555 being merged is a solid win — one fewer carry-over.
Skill Development: The intersection of data engineering and presales (e.g., Jonas Chorum call with EAV lookup tables) is a differentiating skill. Few people in the industry can both design data models and demo them to customers. This is worth leaning into.
Harness Engineering observation: You’re already practicing what Mitchell Hashimoto describes — iterating on AGENTS.md, building automation scripts that learn from mistakes. This is a genuine competitive advantage in the AI-first era. Continue investing in it.
Context switching: You flagged this yourself — many projects are “always on” (Internal, Presales, Docs, Personal, Teaching). The Focus Days approach is worth a trial run next week: e.g., Mon/Wed = deep Internal work, Tue/Thu = presales + reviews, Fri = wrap-up.
Recommended resources to learn
Mitchell Hashimoto’s “My AI Adoption Journey” — already read, but worth revisiting Step 5 (Harness Engineering) as you build more automation. Share with team?
dbt discourse: Multi-currency reporting patterns — search for “exchange rate” and “multi-currency” threads. Community patterns for dim_exchange_rates and constant-currency MRR will shortcut your DAT-576 implementation.
Ghostty AGENTS.md example — referenced in Hashimoto’s article. Good reference for structuring AGENTS.md for different subdirectories.
YouTube: Analytics Engineering with dbt — Incremental Models Deep Dive — reinforces the lookback window patterns you applied to DAT-555.
Book: “The Staff Engineer’s Path” by Tanya Reilly — relevant for your growing ownership of cross-team projects (MRR, Calendly, presales tooling). Good framework for “glue work” and technical leadership.

Weekly Report - 2026-W17

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Apr 20 – Apr 26, 2026 (friday mode)
Work
Internal
DONE Calendly data pipeline reporting layer scoped (DAT-283)
- Following the merge of dbt #853 (approved last week), captured the full reporting-layer plan in journals/2026_03_19.md covering Source / Staging / Domain / Mart / Deprecated / Fixed layers.
- New canonical mart: mart_growth__calendly_bookings (view → fct_calendly_bookings, grain = event × attendee × rep) and mart_growth__calendly_events (table → dim_calendly_events).
- Deprecated (enabled: false): mart_growth__demo_calls, mart_growth__onboarding_calls, mart_core_business__demo_call_bookings, dom_calendly__demo_call_bookings, dom_calendly__onboarding_call_bookings.
- Fixed: mart_core_business__sales_leads now joins dom_calendly__bookings directly on attendee_email_domain (resolves the 88% drop in call-booking leads found last week).
- Next: update Holistics BI Model / Dataset / Dashboard to align with the new layer (Ampcode thread).
WAITING Review PR CircleCI for anh Dong (prefect #397 / DAT-579 — sub-task of DAT-578 CircleCI pipeline revamp)
- Round 1 review done. Used Ampcode (code review) and Ampcode (PR 858) to scaffold review.
- Now waiting on anh Dong’s response. Notion DE-214.
NOTE DAT-556 dbt test failure root cause analysis (Ampcode)
- Failing test: unique_map_identities_zendesk_hubspot_zendesk_organization_id. Zendesk org 900032617243 (1win.pro) maps to 2 HubSpot companies because 1win.pro appears in all_domain_names of both HubSpot 5855457913 and 18891852445.
- Root cause: IN UNNEST(all_domain_names) join in itg_mappings__zendesk_tenant.sql (and similar integration-layer joins) creates fan-out whenever a domain appears in multiple HubSpot companies. Originated from DE-187 phase 1 (PR #812).
- Impact: 16 tenants across ~10 companies; affected customers: Correlation Risk Partners, Cruisebound, 1win.
- Decision: leave the test failing for now and address as part of the broader DE-187 resolution (canonical customer_skey work). Not yet actioned due to sick leave.
NOTE dbt deprecation policy clarified (Ampcode thread)
- Phase 1: deprecate in code. Phase 2: remove the .sql file. Phase 3: drop the table.
- Don’t sit between phase 2 and 3 — AML models reference BQ physical names; removing the .sql only stops refresh, leaving the table with stale data and silently misleading consumers. Either keep the wrapper alive or drop the table entirely.
NOT STARTED (carry-over) MRR exchange rate work (DAT-576) — manager P1 from W16 1-on-1; not started due to sick leave + holiday week. Will pick up next week.
NOT STARTED (carry-over) Lead Funnel by Sales Motion (DAT-560) — added Ampcode (Holistics PR) reference; still blocked on Calendly BI rollout.
Presales
DONE Basata follow up on light/dark theme — completed Apr 21 (Slack, Ampcode)
- anh Huy posted the consolidated workaround to Taha (Basata) on Apr 21:
  - Gap 1 (no theme context in embed payload): Basata duplicates the dashboard into 2 versions (light + dark); Basata app reads the user’s theme preference and renders the matching embed.
  - Gap 2 (Sankey + dynamic markdown don’t adapt): standard charts via per-theme color palettes; Sankey via custom CSS; dynamic markdown gets per-theme CSS in each dashboard. anh Huy offered to impersonate and apply the Sankey fix.
- Caveat communicated: dashboard header + zoom section can’t be customized via CSS yet (rendered at the Holistics layer); use case forwarded to PMs for the longer-term embed-payload theme support.
NOTE Communication observation: in two recent enterprise conversations I offered to do hands-on work and got silence in return.
- Showbie (Slack thread): Harsha asked about parent-child filtering, Param Fields, and pivot-by-question for a Looker → Holistics rebuild. I confirmed all three are supported, sent doc links, and offered to log in and build the pivot example for him. No reply.
- Basata (Slack thread): anh Huy proposed the dual-dashboard workaround and offered to apply the Sankey CSS fix via impersonation. No reply yet.
- I don’t know how to best communicate with these kinds of users — possibly the offer of “I’ll do it for you” reads as too forward, or they need time to absorb. Worth raising in next 1-on-1.
Duty Support
DONE Review AI sharing dashboard for Aurora — completed Apr 23 (moved to Backlog/Done)
- Confirmed Hieu’s dashboard is feasible to share as spreadsheet but not yet ready to consume — needs polishing before delivery.
- Aligned with the commercial decision: Vincent (CEO) clarified the in-app AI usage dashboard is free for all customers; what’s being sold is data sync/export to Aurora’s own systems (S3 preferred, Google Sheets secondary). Targeting enterprise compliance, security auditing, 7+ year retention.
- Final delivery format pending Nam’s email to Aurora. AI team (Phuong/Tien/Dat) owns separate in-app monitoring; data team scope is bounded to current ClickHouse data.
- Prior art: SweetSpot Slack thread — same pattern.
- UPDATE — deal deferred Email thread between Nam (Holistics) and Weiping (Aurora), Apr 20–23 (Slack file):
  - Nam pitched the $10,200/year “Usage and AI Data Monitoring Transfer Sync” (S3 delivery, scope: conversation time/ID, user ID, prompts + AI replies, token usage per user).
  - Aurora pushed back: hard to justify $10,200/year given the in-app AI usage analytics is on the Holistics roadmap for the next 1–2 quarters. Counter-proposals: monthly manual data dumps OR a read-only user on a read-only replica of the backend DB.
  - Both sides agreed to revisit when Holistics has more concrete AI usage data.
  - Implication for data team: no immediate delivery work needed. The Aurora-specific AI conversation dashboard (Hieu’s) can stay on hold; focus shifts to AI team’s in-app analytics rollout. Keep the dashboard ready in case the conversation reopens.
Docs
NOT STARTED (carry-over) Add demo video for local development docs — moved to journals/2026_05_25.md (will scope after the holiday). Slack 1, Slack 2.
- NOTE Follow-up DM with Khai To on Apr 23–24 (Slack DM):
  - Demo direction: lead with the outcome demo (like lightdash does — show power first); push step-by-step setup into the docs.
  - Khai’s MCP for local metric queries is on staging13, not yet prod. He’ll demo it (skill + MCP combo) once I’m back from holiday.
  - Estimated cadence: “probably 2 weeks after holiday” — aligns with the demo-video scoping push to mid-May.
Personal / Tooling
DONE Set up Drata and remove Vanta — Apr 23 (Slack, Notion guide).
- Triet announced the Vanta → Drata migration to all engineering on Apr 23. Required steps: acknowledge all policies, install + register Drata agent, complete Security Awareness Training and HIPAA Training. Keep Vanta installed until further notice. Two-week deadline.
DONE Tax checking — Apr 23 (Slack).
- HR (Nhu Nhu) asked everyone to install Etax Mobile and check 2025 PIT finalization status before her leave. Verified own status: single-source income at Holistics → finalization successful, no follow-up needed.
DONE Set up CLI client for Cloudflare R2 upload — Apr 27 (Ampcode). Closes the loop on the auto-upload-to-R2 setup for Logseq media.
NOTE Considering migrating emergency savings out of 1Long — no longer trust its reliability for emergency funds.
DECIDED Google One downgrade: keep current plan. Linh and my younger brother still rely on it, so the per-user value justifies the cost. Closes the W16 open question.
Learning & Notes
LEARNING Don’t play games at night after 6PM — they always extend into late-night sessions. Restrict to morning / early afternoon. Caused the cold that wiped out Mon–Wed.
READ “Ask for no, don’t ask for yes”
- Instead of “Hey boss, can we install action X?”, say “Hey boss, I’m going to install action X to solve XYZ. Will take care of it Monday unless I hear differently.”
- Shifts cognitive load: gives the manager an opt-out window without blocking your progress, while you still own the framing of the problem and the solution.
- Tone matters — needs to be calibrated to the person and what they actually want to know (e.g., size of the problem, downstream risks). Worth practicing on smaller decisions first.
- The tips category on mooreds.com reads like a senior engineer sharing small craft-level tips that LLM searches don’t surface — reminder to keep cultivating non-LLM reading sources.
NOTE Need to deliberately seek out blogs / RSS feeds rather than defaulting to LLM search inside Logseq. The signal/noise from a curated human writer is different from an aggregated answer.
NOTE Trip to [[Trip - Bàu Sấu 04/2026]] — Ghibli-like landscape, dry-season trail (no mosquitoes/floods), good leg training (~6km/day) and digital detox (no signal). Will return next year, possibly during rainy season for a different experience.
Next Week
P1 — Must Do
- Internal: Start MRR exchange rate work (DAT-576) — build dim_exchange_rates with live rate ingestion. Carry-over, manager P1.
- Internal: Pick up DAT-555 follow-up captured in journals/2026_04_27.md.
- Internal: Update Holistics BI Model / Dataset / Dashboard for the new Calendly mart layer (DAT-283).
- Internal: Resolve DAT-556 dbt test failure (root cause already analysed Apr 22).
- Internal: Close out CircleCI PR review feedback loop with anh Dong (prefect #397 / DAT-579).
P2 — Should Do
- Internal: Lead Funnel by Sales Motion (DAT-560) — unblock once Calendly BI layer is rolled out. Carry-over since W14 (4 weeks).
- Internal: Clean up BI layer for job queue dashboards (delete WIP 3.0, migrate v2 / Report Monitoring to 4.0).
- Internal: Increase data freshness — impersonation lookup more frequent than daily (DAT-499). Manager P3.
- Docs: Draft scenario for local development demo video, then sync with anh Huy Vu / Dat. Carry-over.
- Teaching: Find a football dataset for Duc Anh.
P3 — Nice to Have
- Internal: Contribute to Holistics skills and internal-skills repos.
- Presales: Read Modeling Patterns docs.
- Personal: Self-reflection + CV update. Research alternatives to 1Long for emergency savings.
Holiday note: Thu Apr 30 and Fri May 1 are public holidays in Vietnam (Reunification Day + Labour Day) — plan light work Mon–Wed and rest/play Thu–Fri.
Career & Personal Consulting
Progress Review (Start / Stop / Keep)
- Keep: When energy was low, you still chose the highest-leverage tasks (Basata follow-up, Aurora dashboard review, CircleCI review round 1) and let the rest slip rather than dragging everything to half-done. That’s healthy triage.
- Keep: Capturing the dbt deprecation policy as a reusable note (3-phase rule). These small principles compound — they prevent future “stale table” landmines and give you something concrete to teach Thuan / juniors.
- Start: Treat illness as a hard stop, not a soft pause. You felt off from Monday and pushed until Wednesday before resting. Sleep + early stop on Mon would likely have salvaged Tue/Wed. Build a rule: if you feel off two days in a row, stop on day two.
- Stop: Late-night gaming on weeknights — you already self-identified this as the root cause. The LEARNING note is good; pair it with a concrete trigger (e.g., laptop closes at 22:00 on weeknights).
Workload observations
- This was a low-output work week by design (illness + trip), and that’s fine. The bigger risk is that two of last week’s manager-priority items (MRR exchange rate, BI cleanup) are now zero-progress carry-overs. Next week is also short (2 holidays); be realistic about scope.
- The “Ask for no, don’t ask for yes” article is timely — your carry-over list is growing, and proactive framing (“I’ll start MRR Mon, will course-correct based on Friday review”) would reduce review-cycle latency.
Personal well-being
- Trip to Bàu Sấu was a real reset — physical movement (6km/day) + no signal + nature is the right antidote to context-switching fatigue you flagged in W16.
- Health: the cold is a signal. Sleep > productivity. Seven days of recovery cost roughly the same time as four nights of better sleep would have prevented.
Career development
- Carry-over is becoming a pattern (MRR, Demo video, DAT-560, DAT-524). Consider a hard rule next week: any item carried over 3+ weeks gets a forcing function — either start it on a specific day, or formally backlog it. Avoid the “always-on but never-done” zone.
Customer communication signal (Showbie + Basata)
- Both threads end with us volunteering hands-on work (“I can build the example”, “we’ll apply the CSS via impersonation”) and the customer going quiet. Two non-mutually-exclusive hypotheses worth testing:
  - (a) Decision delay — they need time to socialize internally; silence is “not yet”, not “no”. Action: send a soft check-in 3–5 days later instead of waiting indefinitely.
  - (b) Perceived push — “I’ll do it for you” can feel like over-reach for users who want autonomy. Action: try framing as a self-serve doc + offer (“here’s the recipe; happy to pair if helpful”) rather than “I’ll do it”.
- Either way, a follow-up cadence rule (e.g., 3-day silent → ping; 7-day silent → close loop with PM) prevents these from becoming permanent open loops.
Recommended resources to learn
Maximize Your Recovery: Sleep, Stress, and Illness — Huberman Lab episodes on sleep and recovery. Useful given this week’s illness pattern; pair with the gaming-curfew commitment.
How to Write a One Pager — Wes Kao. Good companion to “Ask for no, don’t ask for yes” — both are about framing decisions for busy stakeholders. Applies to your MRR / Calendly status updates.
dbt deprecation patterns discussion — search “deprecate model” / “remove model”; community patterns confirm the 3-phase rule you derived this week.
Atomic Habits — environment design chapters — relevant for the no-late-night-gaming rule. Behaviour change is easier with environment changes (e.g., move console out of bedroom) than willpower.
Cal Newport — Deep Work / time-blocking — supports the Focus Days experiment from W16. With 3 effective workdays next week (Mon–Wed before holiday), time-blocking matters more than usual.
“Never Split the Difference” by Chris Voss — relevant for the Showbie/Basata “silence after offer” pattern. Specifically chapter on calibrated questions and the “no” answer bias (links nicely with the “Ask for no, don’t ask for yes” article).
Wait But Why — “How to do battle with the procrastination monster” — pair with the carry-over forcing-function rule. Long carry-overs often have a procrastination root, not a priority root.

Weekly Report - 2026-W18

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Apr 27 – May 3, 2026 (friday mode)

Two-holiday short week (Thu Apr 30 Reunification Day + Fri May 1 Labour Day). Effective workdays = Mon/Tue/Wed for Holistics work; Sat/Sun spent on Smartclass releases and reading. Net: shipped Calendly BI rollout + tenant-lookup fix on the Holistics side, and two Smartclass releases (v0.4, v0.4.5) on personal side. Next week’s MRR exchange-rate work is still zero-progress (3-week carry-over).

Weekly Report - 2026-W19

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — Apr 29 – May 8, 2026 (friday mode)

First full 5-workday week after W18 holidays. Big internal closure: Lead Funnel by Sales Motion (DAT-560) shipped — DAT-561/562/563/564 all closed May 8, ending a 5-week carry-over that had been blocked on Calendly. Big presales loss: [[Showbie]] went to Omni; learning synthesis captured. MRR exchange rate (DAT-576) still NOT STARTED — now 4-week carry-over and being treated as a restart in W20: Hieu left and most implementation context is gone, so W20 Mon AM is recovery + scoping (not implementation), with a Wed-EOD escalation gate to anh Triet. CircleCI dbt PR #858 still open (cherry-pick dbt#861 merged). DAT-555 closed for real this week. Tooling week was strong: Holistics MCP, amp plugin for MCP error logging, slackcli, caveman skill, RTK install.

Weekly Report - 2026-W20

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — May 11 – May 17, 2026 (friday mode)

Steady throughput week. Big wins: CircleCI PR review marathon finished (rounds 2–4, prefect#400 + dbt#858 closed), [[BuyCo]] custom theme rolled out on Volumes dashboard, Power BI playbook draft started for BuyCo onboarding (Tue May 19). Khai To’s 2-way sync CLI shipped — unblocks the local-dev demo video (4-week WAITING cleared). MRR exchange rate (DAT-576) still NOT STARTED — now 5-week carry-over: Mon AM recovery slot lost again to CircleCI close-out, week absorbed by BuyCo theme + Datacubed dashboard fix + Power BI prep. Honest call: needs hard escalation in next 1-on-1. Tooling: rg/grep + rtk fix, personal finance app rental-affordability simulation. Weekend = VCT Pacific watching + travel (no H1 self-reflection done — sliding W21).

Weekly Report - 2026-W21

Mon, 25 May 2026 00:00:00 +0000

Weekly Report — May 18 – May 23, 2026 (friday mode)

W21 (full week). Power BI migration theme dominated: (1) playbook published Mon → docs/conceptual-differences + docs/migrating-to-holistics; (2) end-to-end AW-Sales POC w/ value parity to the cent; (3) migrate-power-bi agent plugin shipped via holistics/skills#10, then bug-fix follow-up #12, then bumped to 0.1.1. Mid-week: BuyCo + Basata onboarding calls closed, Enhance Fitness RFP assessed ($4.6K/mo proposal in flight), SLA data pull delivered to Xairo, 1-on-1 report written. Late week: 2 Docs PRs (docs#1639 OAuth+MCP, docs#1640 from-others landing), PatientsKnowBest answered, Datacubed embed user tracking delivered. New WAITING: TerryWhite Chemmart data question (pending anh Tan Huynh). DAT-576 MRR exchange rate still NOT STARTED — 5-week carry-over remains the open wound; 1-on-1 escalation done but no resolution yet captured.

Write - Audit - Publish

Mon, 25 May 2026 00:00:00 +0000

https://chatgpt.com/c/6924828b-1524-8329-9f0d-5227092010d2
Difference from Dev/Prod
- Dev/Prod: where code runs
- WAP = how each run of that code introduces new data into prod
Still inside the Prod environment, only different in schema, not separate environment

Page on lelouvincx's second brain

[dblineage] Gathering User Data

[Internal] Customers' MRR (Exchange Rate)

Goal

MRR Definition

Data Architecture

Data Sources

dbt Pipeline Flow

Identity Resolution

ER Diagram

Key Datasets & Dashboards

Exchange Rate Decision

Identified Problems & Root Causes

Edge Cases

Technical Fixes

Progress

References

[Internal] Identity Resolution

1-on-1 Planning - 2026-04-13

Plan for Next 1-on-1

Key topics to discuss with manager

1-on-1 Planning - 2026-Apr 13, 2026 – May 20, 2026

Plan for Next 1-on-1 (covering Apr 13 – May 20, 2026)

Accessories That Make My Life Better

Gears

Softwares

Misc

Add2Cart

Noticeable calls

Metric Catalogue

Backlog

A. Work

Internal

Backlog / Done

Done

Book - How To Solve It

Key notes

Chap 1

Quotes

contents

Data Modeling

data-ops-bot

dblineage

Job To Be Done & Job Map

DIKW Pyramid

Dimensional Modeling

Keynotes

Docs

Resources

Down The Rabbit Hole

Economix

Gaps and Islands

Google Data Portability API

Health Rules

Health Rules

Sleep & evenings

Illness

Movement & environment

Weekend discipline

Notes

How to do an internal data tracking project?

Process

Inmon - Data Warehousing

Keynote

input

Internal

Journals

Tasks

Done

Just Enough Automation

Kimball - Data Warehousing

Keynotes

Lead Funnel by Sales Motion

Goal

Sales Motion Classification

Data Model

Leap of Faith

Measuring Engineering Productivity

Memory Decreasing

ngocyen99tb.lelouvincx.com