Avatar
🧠

Organizations

386 results for Journal
  • journal Created Thu, 22 Jan 2026 00:00:00 +0000
  • Notes

    • Small setting in MacOS but makes me happy: change color of highlighting to yellow, to make it more like a normal highlighter (default is blue).

    • Tasks

    • Done

      • {{embed ((696e1a3b-3474-49a3-9604-c3a3eaf04c61))}}
      • DONE Write peer review for colleagues
    • {{embed ((694b5e14-1dff-4e10-b325-ed0dae46e467))}}

    • DONE Colobbo’s use case

      • “It may not be a good fit, it may not be a strong fit, whatever. But the point is, if you can’t support this guy, I don’t know if other tools can do it.”
        • Most standard BI tools (Tableau, Power BI, Looker) are built on the assumption that 1 field = 1 database column. When you break the rule by storing columns into rows, tools fail because they cannot see the fields to filter or group by them without massive performance penalties.
      • The best option is to make it hybrid, like headless BI. Because the UI is very difficult to replicate.
      • Understanding
        • Based on requirements there are 3 main parts:
            1. Users can add many filters (default/custom) simultaneously
            1. Run a query (can be either AQL - our internal query language or SQL)
            1. Grab the returned results and render table, with additional custom columns.
        • 1st assessment: Holistics dashboard cannot allow users to add as many filters as they want -> this is known limitation -> the Embedding approach isn’t suitable now -> we can try to assess the Headless BI approach.
        • Headless BI: The app render UI on its own, then post an API request to Holistics and receive resuilt, after receiving result it can render data table.
        • Sample request payload (in AQL - internal query language):
          • explore {
              dimensions {
                sites.id,
                field_values.field_key,
                ...
              }
              filters {
                // No direct subquery, so use aggregation logic
                // Approach: For each site, count how many of the required key/value pairs exist
                (
                  count_distinct(
                    case(
                      when: (field_values.field_key == 'A1' and field_values.value == '123') or
                      (field_values.field_key == 'A2' and field_values.value == '456') or ...,
                      then: field_values.field_key
                    )
                  ) == 2
                )
              }
            }
            
        • Practicing this approach gains no beneficial value compared with running a normal SQL query against database:
          • SELECT 
                wp.id,
                wp.name
            FROM tblWorkPackage wp
            JOIN tblCustomFieldValues cfv ON wp.id = cfv.entity_id
            JOIN tblCustomFieldDefs cfd ON cfv.field_def_id = cfd.id
            WHERE 
                -- 1. List ALL conditions in an OR block
                (cfd.field_key = 'A1' AND cfv.value_number = 1) OR
                (cfd.field_key = 'A2' AND cfv.value_number = 2) OR
                (cfd.field_key = 'A3' AND cfv.value_number = 3)
            GROUP BY 
                wp.id, wp.name
            HAVING 
                -- Ensure the site matched exactly 3 distinct criteria
                COUNT(DISTINCT cfd.field_key) = 3;
            
        • Also, the BI tool does not support multi-tenancy on custom columns (while expectation is avoid flattening too many custom fields in a single table, maintain multi-tenancy and security standard).
        • So the final assessment is Holistics may not be suitable for your use case. Because BI tools build on the assumption that the database column should be explicitly visible. In EAV, the columns are hidden as rows in Fields and Values tables.
    • DONE Write a note to #sales-demo to consolidate drill-through dashboards into one.

    journal Created Wed, 21 Jan 2026 00:00:00 +0000
  • Notes

    • Joyful morning, new favorite sit at the cups coffee

    • Tasks

      • {{embed ((696e1a3b-3474-49a3-9604-c3a3eaf04c61))}}
    • Done

      • DONE (?) Watch superb’s call
    • DONE Load dbdocs tables into BigQuery

    • DONE Respond Tricia & Clark

    • DONE Call - requirements gathering Colobbo

      • Use case
        • They have some flaterned tables that need to be modeling before exposing to users.
        • Pivoting column keys and values at multi-tenant/multi-project level.
    • DONE Teach Duc Anh

    • DONE CS Call with Aarki

    journal Created Tue, 20 Jan 2026 00:00:00 +0000
  • Notes

    journal Created Mon, 19 Jan 2026 00:00:00 +0000
  • Notes

    • https://gemini.google.com/app/2eb89c1d79f22e0d
      • When someone says something impacted his style/choice/taste in the early years of career, that means, right now he has seen a bigger picture and has compared himself with fellows who has the same background as him but went a different route.
      • With an increasing number of “indie hackers” (observed it via Build In Public facebook group), there is an opportunity to sell bootstrapped-style spirit and related data content.
        • For example, write content about doing data analysis for solo product apps.
    • How to use AI without becoming stupid
      • “DO NOT outsource your subjective value judgements to an AI, unless you have a good reason to, in which case make sure the reason is explicitly stated.”
    • Tasks

    • Done

    journal Created Sun, 18 Jan 2026 00:00:00 +0000
  • Notes

    • Tasks

    • Done

      • {{embed ((69670f76-e398-42cb-9763-e56dbcc4f404))}}
      • {{embed ((695e13a2-4937-40df-8f61-7b1af0981cbb))}}
      • DONE UI/UX feedback for AI team after my trial yesterday
    • DONE Weekly sync #2026-01-16

    journal Created Fri, 16 Jan 2026 00:00:00 +0000
  • Notes

    • https://www.1keydata.com/datawarehousing/processes.html

      • Very good reference data warehousing’s terms & processes.
      • Mentioned once in [[Data Modeling]]
    • https://www.ssp.sh/blog/diary-of-a-data-engineer/

      • Now bro emphasizes on the importance of [[Data Modeling]]
    • Tasks

    • Done

      • {{embed ((69671001-f0b8-41c0-9f99-f9706404e7cb))}}
      • {{embed ((694b5e14-1dff-4e10-b325-ed0dae46e467))}}
      • {{embed ((695e13a2-4937-40df-8f61-7b1af0981cbb))}}
      • DONE Write a quick update for Simon about the dashboard progress
    • DONE Help a Thi with the dbx proposal on dblineage

    journal Created Thu, 15 Jan 2026 00:00:00 +0000
  • Notes

    journal Created Wed, 14 Jan 2026 00:00:00 +0000
  • Notes

    • Add2Cart Dashboard Implementation Process

      • This is a 5-step process designed to translate dashboard prototype into performance Holistics assets.
      • Metric first, structure second.
      • Start by attempting to define logic in the metric layer (AQL). Only push logic upstream to the AML when you hit hard limitations (like filter conflicts or complex nested aggregations).
        1. Prototype Deconstruction
        • Before coding, map the dashboard inputs to outputs.
        • Inputs: What are filters (Date, Primary Retailer)?
        • Outputs: What dimensions are shown (Competitor Retailers)?
        • Check:
          • If I filter by Input A (Coles), does Output B (Woolworths) disappear? If conflict, need a scope pattern (step 3), but define your metrics first to see exactly what they need.
    • Tasks

    • Done

      • {{embed ((695f172d-3b9f-447f-a5fe-d76f67fa0d00))}}
      • {{embed ((6923d401-6764-4172-90e9-3ff64a3b7a9b))}}
    journal Created Tue, 13 Jan 2026 00:00:00 +0000
  • Tasks

    • Done

      • DONE Remove duplicated dashboard in hooli embed portal
    • DONE Answer Anurag

    journal Created Mon, 12 Jan 2026 00:00:00 +0000