Avatar
🧠

Organizations

  • Notes

    • How to Present a MIND-BLOWING Software Demo That Closes Sales {{video https://www.youtube.com/watch?v=EZbIx94dMeU}}

      • Continue from: ((69c75aaa-9b56-4118-8b94-0e168d9ad82c))
      • Transcript: https://media.secondbrain.lelouvincx.com/2026/03/yt-EZbIx94dMeU.txt
      • A recap slide in or after the call, layouts:
        • Fact.
        • Problems that challenge.
        • Key evaluation criteria.
        • New finding didn’t appear in past calls.
      • A thing that I learnt last time is also mentioned again: If I’m an airline, I want to hear about passengers. If I’m a SaaS, I want to hear about users. If I’m a lawyer, I want to hear about clients. => have to speak their language.
      • If one person joined a long time before everyone else, it can be a little awkward if you have nothing to talk during that time. So do research first. Find them on linkedin, social media, personal blogs, find something interesting about themself.
      • Important: confirming what they care about.
      • Prepare what we are going to demo first, according to their filled information in the call, their past calls.
        • At the beginning of the call, show them the notion document technical onboarding call containing that recap.
        • Ask them: “would you like to make any changes before we start?”, “is it okay if I spend the demonstration talking about how those things could be addressed using our product?”
        • Make them feel like: “okay, this person is clearly informed about my business, they’ve clearly done research, they know who’s involved in the conversation, and they’re gonna address things that we care about”.
      • At the end of the day, it’s very easy to talk features, but the use cases and the explanation how it relates to my business.
      • During the call, constantly ask them:
        • What is it that you care about?
        • Is this what you’re looking for or was it something different?
      • Silent is gold. So we can just stop when we’re talking too much to bring their attention back.
      • Having someone to sit aside to assist:
        • They will look that the crowd’s faces while you are looking at the screen.
        • Introduce them in a different role. For example: Chukwudi - he’s an account manager who can help you with commercial questions; or Marcus - he’s a technical person from data team who can help you with engineering/data questions.
      • Last step: send each audience or at least mention them in the recap email.
    • How to teach technical concepts with cartoons

    journal Created Sun, 29 Mar 2026 00:00:00 +0000
  • Notes

    • LEARNING Holistics workers and objects, what do they mean?

    • Recent 1-2 weeks, after Tet 2026, I feel even more productive in work than the whole last year.

      • Dont know the exact reason. In my opinion, I am gradually used to the work culture / habits / context. Gaining more confidence in delegating tasks, use company’s resources and communicate to people (both internal and external customers).
      • If it’s 80/20, I think the biggest change here is communication confidence.
      • I realize I’m not bad at speaking, but just need some time to ice-breaking it. All of them start from the call with Showbie.
      • In that call, I suddenly become the person leading the call. I was not really smooth, but gained the confidence based on their understanding and responses.
      • It felt really good.
      • The second reason why I am feeling productive is the logseq automation helps me remember the whole historical context => makes me feel better in sync calls => remember things and connect the dots.
    • Installed Annotate

    journal Created Sat, 28 Mar 2026 00:00:00 +0000
  • Notes

    • Performance of Showbie is what I’m concerning. Should raise this first to the team and ask for approach.

    • Tried Zed IDE, not supporting ampcode, and I’m more familiar with terminal-based IDE like neovim. Not suitable for me.

    journal Created Fri, 27 Mar 2026 00:00:00 +0000
  • Notes

    • A long day with a lot of tasks. Still productive!

    • Tasks

    • Partly today

    • Done

      • DONE Showbie - embedding question

      • Update document: to add FAQ about why row-level permissions are bypassed if you are admin.

    • DONE Call with Adam from superb

      • To prepare: a demo4 local react app (backend + frontend), similar to what I demo to [[Basata]]
      • Note down some feedbacks for embed team:
        • User Attribute:
          • The UI/flow for User Attributes is counterintuitive.
          • Why do internal attribute configurations impact the embedded environment?
          • Ownership Misconception: Adam assumed User Attributes were tied to his personal account/dataset ownership. He questioned if he needed to change the “Dataset Owner” to make attributes function correctly for other users.
        • Embedded Analytics page is difficult to find within the top header navigation.
        • Permission-as-Code: Since permissions are defined via code, there was significant friction regarding where to place the code, the specific syntax required, and what values to input, what do they mean, presentation in List tab.
    • ((69c2a77c-8eb1-4a4b-b87d-ea26d378c713))

    journal Created Thu, 26 Mar 2026 00:00:00 +0000
  • Notes

    • Tasks

    • Partly today

      • DONE Share the document for the embedded dashboards for different customers

        • My typical workflow:
          • Tell gemini to design a basic UI based on customer’s branding guide.
          • Tell ampcode implements it, using basic backend/frontend architecture: App.jsx (react) for frontend and server.js (express) for backend.
          • Holistics sets frame-ancestors ‘self’ https: on its portal, which blocks iframes loaded from http://localhost because it only allows HTTPS origins. The browser refused to render the Holistics iframe with the error: “Framing ‘https://us.holistics.io/' violates the following Content Security Policy directive”.
          • The solution was to serve the local dev server over HTTPS using @vitejs/plugin-basic-ssl, so https://localhost:5173 satisfies the CSP policy.
        • How to I present how to set up embed portals to customers?
          • Explain high-level mechanism logseq.order-list-type:: number
          • In Holistics, show: logseq.order-list-type:: number
            • Embed portal in development and how to add dataset/dashboard objects. logseq.order-list-type:: number
              • Firstly just develop model/dataset/dashboard as usual. logseq.order-list-type:: number
              • Then put whichever object they want to externally embed into their app. logseq.order-list-type:: number
            • Credentials location. logseq.order-list-type:: number
          • Backend side: logseq.order-list-type:: number
            • Step 1, generate payload, which is basically a JSON object to configure how and which each customer will see. logseq.order-list-type:: number
            • Present parameter reference. logseq.order-list-type:: number
            • Sign payload with JWT token using the secret. logseq.order-list-type:: number
          • Frontend side: logseq.order-list-type:: number
            • Render iframe based on the signed JWT token. logseq.order-list-type:: number
        • Then ask the question: how to restrict data access for each customer? Answer: we come to row-level permission
          • High-level mechanism logseq.order-list-type:: number
          • Add user attributes. logseq.order-list-type:: number
          • Add permission as code into dataset. logseq.order-list-type:: number
            • Explain the single entry point for row-level permission is dataset. Once add into dataset, every widgets of a dashboard query from that dataset will be restricted by RLP. logseq.order-list-type:: number
            • If a dashboard is not restricted, it’s because that dashboard is using another dataset. logseq.order-list-type:: number
          • See preview in development embed portal. logseq.order-list-type:: number
          • Configure payload to include that user attribute. logseq.order-list-type:: number
    • Done

      • DONE Ask squad modeling why the user 112390 does not exist

    journal Created Wed, 25 Mar 2026 00:00:00 +0000
  • Notes

    • IDEA synthesize tone and writing style of the everyone in Holistics (resource: notion) and extract key insights from it, then materialize into an agent skill for better notion skill’s output

    • Tasks

    • Partly today

      • ((69bcb599-a91e-49ea-bc3d-6a5a651f03df))
      • ((69c2a77c-2f5b-4c6e-851b-4d8425fbc122))
      • {{embed ((69c1f832-a120-4831-94a4-d7ef9eecbc59))}}
      • DONE Review Thuan’s work on DE-208
    • DONE Round 1

    • DONE Round 2

    • Done

      • DONE Onboarding call 3 with Basata

      • Shared use case of Date Drill

      • Report issue for Auto mapping filter between viz and field

    journal Created Tue, 24 Mar 2026 00:00:00 +0000
  • Notes

    • Good timing does matter

      • Context: when I want to propose an idea to dbx team about setting up a Claude connector to interact with dbdiagram right inside claude desktop: Ampcode
      • I can read it from each team’s sync to quickly decide whether to propose an idea
      • For example, when I want to propose ((69c10475-619d-42df-b63e-1884b27ce548)), read the dbx team sync to find out whether they are having some similar key words in mind
    • dbt fails debugging process (collected from Thuan)

    journal Created Mon, 23 Mar 2026 00:00:00 +0000
  • Notes

    • [[Economix]]
    • Context switching remains high: consider limiting 2-3 projects per day next week.
    • Tasks

    • Partly today

    • Done

    journal Created Sun, 22 Mar 2026 00:00:00 +0000
  • Notes

    • Nghỉ ngơi và coi one piece rất vui
      • Coi lại đoạn gặp nhau sau 2 năm timeskip, ông già nấu ăn ở Water Seven (rất chill), arc người cá.
      • Câu chuyện của băng hải tặc mặt trời rất cảm động.
      • Tác giả xây dựng cái bất công của phân biệt chủng tộc. Trong truyện là con người và người cá.
      • Mỗi lần người cá quyết định tin, thì con người lại làm họ thất vọng.
      • Nhưng nhiều khi nguyên do cốt lõi chỉ đến từ “do chúng tôi không biết gì về các bạn”.
    • Mình đã đi khám mắt
      • Độ vẫn giữ như cũ, chỉ có đục thuỷ tinh thể trong mắt làm mình thấy mờ đi.
      • Sẽ thay cái kính mới để chống ánh sáng mặt trời lúc ra đường.
      • LEARNING nhớ nhỏ mắt thường xuyên, tránh để mắt khô.
    • Tasks

    • Partly today

    • Done

    journal Created Sat, 21 Mar 2026 00:00:00 +0000
  • Notes

    • Tasks

    • Partly today

      • ((69b3d030-98dd-450d-88d8-e00c1c322c59))
      • ((69abeee3-b624-4e96-bd98-696afff2a17b))
    • Done

      • ((69bcd2d3-e4f6-4661-95e4-80337127ac28))

      • DONE Call with Add2Cart

      • Remaining items:

        • How to refresh data (anh Dong handled).
        • How to set up other countries?
        • Prepare a PDF documentation to hand over.
        • Missing retailers in public.retailer. To do: follow up with Anurag.
    • DONE Update holistics-query skill with auto publishing and install holistics CLI
    journal Created Fri, 20 Mar 2026 00:00:00 +0000