
We care about doing things right and having a bit of fun along the way. Our new video pipeline is built to help us tell better stories, faster. Whether it’s a deep tech explainer or a meme with bite, every piece now flows through a system that keeps us sharp and in sync.

## Why build a video pipeline?

Because we want our videos to sound like us: clear, clever, and just the right amount of weird. Instead of cobbling things together every time, we built a flow. So the team can focus on the good stuff like ideas, stories, and the occasional perfectly timed troll without getting bogged down.

![](assets/compose-video-pipeline.png)

## Long form video workflow: detailed steps and tools

**Target channels:** YouTube, LinkedIn

**Use case:**  Explainers, dev logs, research stories, design walkthroughs

### Draft the script

*Tool: Notion*

We start with a clear requirement:

- What are we trying to explain and the message?
- Who’s it for?
- Any references we admire?

This becomes the draft script. Everyone chimes in until the script hits the right tone: smart, simple, not boring, aligned with how we talk as engineers.

### Generate the script

*Tool: Generative AI*

We write or co-write the video script using LLMs to help reshape ideas from memos, meetings, or chat threads into a clear voiceover-ready script. The goal is to make the message clear and structured, keeping it aligned with how we’d speak as builders. Think of this as refactoring written insight into spoken form. 

### Choose the reader voice

*Tool: ElevenLabs, Google AI Studio or a Dwarves voice*

Sometimes it’s a Dwarves teammate. Sometimes it’s AI from Elevenlabs. Either way, the voice should match the vibe: grounded, calm, witty, a little smug (in a good way), never robotic.

![](assets/compose-video-elevenlabs.png)

### Add transcript

*Tool: Capcut*

We pull a clean transcript for captions. Captions help with clarity, accessibility, repurposing and easier to clip down later. Makes sure keep it clean and time-synced.

### Gather visuals

*Tools: Figma, Google, Meme Kitchen, Giphy, Reddit community*

We source or create visuals to match the story, diagrams, code snippets, product screenshots, doodles, or memes. Rule of thumb: visuals should add clarity, not just decoration.

![](assets/compose-video-capcut.png)

### Edit and output production video

*Tool: Capcut desktop*

Capcut handles most of our editing from syncing visuals and audio to adding subtitles, transitions, and some flair. Final output: 1080p, platform-ready title and description.

## Short video workflow

Shorts are where we get to mess around. Memes, quick hits, highlights whatever gets the point across in under a minute.

**Target channels:** YouTube shorts, Instagram reels, Facebook reels

**Use case:** 1-minute tips, memes, or repurposed long-form content

- **Script**: Notion & Generative AI
- **Visuals**: Giphy, Canva, Reddit community, Google
- **Edit**: Capcut (desktop or phone)
- **Post**: Native apps (YouTube shorts, IG reels, Facebook reels)

### Two ways to make Shorts

**Scripted short formats**

- “Dad, how do I?” explainer style
- “1-Minute Crafts” for dev/design tools
- Quick intros to internal tools or team practices

**Cut from long-form**

- Pull 1–3 highlights from a longer video
- Add captions or transcript overlay
- Export as Shorts-ready clip

## Support layer (behind the scenes)

- **Where do we store things?**
    - All assets (scripts, audio, visuals, exports) go into Google Drive.
    - Organized by episode or series folder.
    - Notion Content calendar is used for asset tracking and version control.
- **How do we notify the team?**
    - Use Dwarves discord when the draft is ready.
    - Feedback and final review tracked at internal channel.
    - Tag stakeholders for final sign-off.
- **How are credentials managed?**
    - Platform credentials (YouTube, LinkedIn) are managed by the content lead.
    - Access is shared only with designated team members.
    - Credential list reviewed and rotated quarterly.

## Script for short teel: “AI-agent explained” example

[Opening image: Three stacked icons labeled 1, 2, 3 with “AI Levels”]

Voiceover:
Let’s talk AI agents. Not every AI is created equal. Most people call everything “AI” but there are three levels, and only one of them is actually doing your job for you.

[Cut to: LLM icon, chat bubble]
Level one: Large language models. These are your classic ChatGPTs. They wait for your prompt, spit out text, and never touch your stuff unless you say so. Basically, a smart parrot with a keyboard.

[Cut to: Workflow diagram, gears turning]
Level two: AI workflows. Now you’ve got automation. You design the steps, AI follows your recipe, and everything is nice and predictable. If you want a robot intern who never goes off-script, this is your stop.

[Cut to: Agent icon, branching paths, goal flag]
Level three: AI agents. Here’s where the magic (and chaos) happens. The AI decides what to do, judges its own work, and keeps trying until it gets the result. It’s like hiring a junior dev who never sleeps and sometimes invents whole new bugs.

[Cut to: Meme “I let the agent handle it, now I have no idea what’s running in prod”]
Sure, it feels like the future. But if you’re still making all the decisions, you’re not using an agent, you’re just automating.

[Closing image: Giphy sticky note “Let the agent vibe, but check the logs”]
So, want to level up? Let the AI make the calls, but don’t blame us when it starts refactoring your life.

## Final notes

This pipeline is how we turn working knowledge into visual stories. It’s how we build our public memory, just like our memo.

Stick to the system. Improve where needed. And ship it when it’s clear, not when it’s perfect.

A behind-the-scenes look at how we built our video pipeline for long-form explainers and short-form content, from script to screen, with AI in the loop.

Composing the Dwarves video pipeline


AI visibility tracking is no longer optional if you want your content to stay seen. But with new tools popping up every month, picking the right one can feel like a maze. Here’s how to navigate the options, what to look for, and how to avoid getting stuck with a tool that doesn’t fit your workflow.

## Start with your real use case

Before you look at dashboards or pricing, get clear on what you need. Are you tracking brand mentions, content citations, or competitor visibility? Do you want daily alerts or monthly reports? The right tool will match your actual workflow, not just look good in a demo.

## Vet the data: Where does it come from?

Not all AI visibility tools pull data the same way. Some use direct API access, others scrape model outputs, and a few rely on third-party panels. Ask these questions:

- Which AI platforms are tracked (ChatGPT, Gemini, Perplexity, Google AI Overviews, etc.)?
- How fresh is the data? Is it real-time, daily, or weekly?
- Can you see the raw outputs or just summaries?

If the tool can’t answer these, keep looking.


## Popular AI visibility tools

- Profound: Strong for enterprise teams, detailed tracking, and competitor analysis.
- AthenaHQ: GEO-focused, with daily tracking and actionable insights.
- Semrush: Expanding into AI tracking with its established SEO toolkit.
- AI Visibility, Peec AI, Rankscale, Otterly.AI: Each offers a slightly different spin—compare features, pricing, and ease of use.

![](assets/profound-answer-engine-insights.webp)

## Test with your own content

Most tools look slick in a sales pitch. The real test is running your own prompts and checking if the results match what you see in live AI answers. Try a trial or demo with your actual memos or brand terms. If the tool’s numbers don’t line up with reality, that’s a red flag.

## How to test before you commit

- Always ask for a demo or trial. Don’t sign a long contract without hands-on testing.
- Run your own prompts and check if the tool’s results match what you see in live AI answers.
- Get feedback from both writers and engineers. Everyone needs to be able to use the tool, not just the analytics team.

## Don’t ignore the basics

- Is the pricing clear, or are there hidden fees?
- Does it fit your budget and scale as your needs grow?
- Can your whole team use it, or is it locked down to a few seats?

## Consider support and adaptability

AI search moves fast. You want a tool that updates quickly and has support you can reach when things break or change. Ask about update cycles, new feature rollouts, and how fast they adapt to new AI platforms.

## What if you’re a solo writer or small team?

You don’t need the biggest tool on the market. Look for platforms with clear dashboards and no-code setup. Even basic tracking is better than flying blind

</aside>

**FAQ**

**Do I need to track every platform?**

Start with the ones your audience uses most. Expand as you grow.

**What if my tool’s data doesn’t match what I see in ChatGPT?**

No tool is perfect. Use tracking as a guide, but always double-check with manual prompts now and then.

## Bottom line

Choosing the right AI visibility tool is like picking a compass for the new search landscape. Take your time, test with your real content, and pick the one that helps your team move fast and stay seen.

Choosing an AI visibility tool can be overwhelming. Get practical advice on what to look for, how to test platforms, and how to make sure your GEO tracking fits your workflow.

How to choose the best AI visibility tool


*Leverage the platforms LLMs love so your memos get quoted and drive AI-first discovery.*

![](assets/seeding-content-for-ai.png)

## Why "seeding" matters in GEO

Seeding means placing your memo’s key ideas or summaries on platforms like Reddit, YouTube, and Quora, places that large language models crawl for fresh, trustworthy content. If you want your work to show up in AI-generated answers, you can’t just publish on your own site and hope for the best. You need to meet the models where they are.

You don’t have to do everything at once. Even posting a strong summary on one platform can boost your memo’s chances of being cited.

## Reddit tactics

Reddit is a goldmine for LLMs. Perplexity, ChatGPT, and others reference Reddit threads heavily—often more than standalone blogs.

**Where to Post**

- r/Programming, r/Golang, r/AI, r/LearnProgramming
- Pick subreddits with 50K+ members and active daily threads

**Thread format**

- Title (max 60 characters):
`Memo Highlights: Building a Deep-Search Pipeline in 3 Steps`
- Body (100–150 words):
    - Opening hook: State the problem in one sentence
    - Three key points: Bullet out your memo’s takeaways
    - Link: Full memo URL at the end
- Call to action: “Questions? Share your challenges below!”

**Engagement tips**

- Reply within 1 hour to every comment to keep your thread visible.
- Upvote insightful replies to encourage quality discussion.
- Use flair if the subreddit allows (like “Article” or “Discussion”).

## YouTube clip playbook

Google AI Overviews often parse and quote video transcripts. A short, direct video can get your message into the AI ecosystem.

**Script template (30–60 seconds)**

- 0–5s: Hook
 
  “Struggling to track AI citations? Here’s how in three steps.”
- 5–20s: Bullet 1

  “Define representative prompts questions that mirror real reader queries.”
- 20–35s: Bullet 2

  “Automate nightly API calls to record citations.”
- 35–50s: Bullet 3

  “Chart weekly reference rates in Grafana and set alerts.”
- 50–60s: Outro CTA

  “Full guide at memo.d.foundation/deep-search-pipeline. Link below!”

**Production tips**

- On-screen text: Display each bullet as it appears in the memo. This helps with transcript parsing.
- Description & pinned comment: Include the full memo URL and a one-sentence summary.
- Tags & title: Use “Deep-search pipeline” and “GEO” in your video title and tags.

## Quora answer format

Quora’s Q&A structure maps directly to how LLMs organize knowledge.

**Identify questions**

- Search for topics like “How to track AI citations” or “What is reference rate?”.
- Pick questions with 1K+ followers or recent activity.

**Answer template (75–100 words)**

1. Direct answer (2–3 sentences):
“Reference rate is the percentage of questions in which an LLM cites your page.”
2. Brief rationale (1–2 sentences):
“High reference rates signal to AI that your content is authoritative and structured.”
3. Read more link:
“Learn more in our memo: memo.d.foundation/guides/reference-rate”.

**Best practices**

- Use a neutral tone, focus on insight, not marketing.
- Paste the full URL, not a link shortener.
- Engage commenters and answer follow-up questions to boost visibility.

## Measuring seeding success

| **Platform** | **What to watch** | **Tools to use** |
| --- | --- | --- |
| Reddit | Upvotes, comments, new AI citations for that memo | Profound, manual prompts |
| YouTube | Views, watch-through rate, transcript hits | YouTube Analytics, Profound |
| Quora | Views, upvotes, “linked source” clicks | Quora stats, Profound |

- Record metrics before posting.
- Re-run your 20-prompt batch 24–48 hours later to gauge citation change.
- Share a before/after snapshot in your team chat.

**Pre-posting checklist**

- Title matches memo heading for semantic alignment.
- Body uses “In summary” hooks and clear bullets.
- Full memo URL is correct and visible.
- Three discussion prompts ready for replies.

<aside>

**FAQ**

**What if I’m not comfortable posting on Reddit or Quora?**

Start with the platform you know best. Even one well-placed summary can make a difference. Or team up with someone who’s active in those communities.

**How do I know if my seeding worked?**

Check if your memo gets cited more often in your GEO tracking tool or batch prompts. Look for increases in upvotes, comments, or clicks on your memo link.

</aside>

*Seeding is how you get your memo in front of both people and AI. Start small, use the templates, and watch your reference rates climb.*

This guide shows writers practical tactics for sharing content on platforms like Reddit, YouTube, and Quora to boost citations and stay visible in AI-generated answers.

Seeding your content for AI: a writer’s guide


It’s easy to talk about GEO like it’s a checklist: optimize your memo, track your reference rate, celebrate when an AI finally quotes you. But the reality is messier. Staying visible in the age of generative engines is a grind. It’s not a one-time win, it’s a cycle of writing, tracking, editing, and adapting. Here’s what the work really looks like behind the scenes.

## The never-ending update loop

You publish a guide. Maybe it gets picked up by AI models for a few days. Feels good. But then a model update rolls out, or a competitor rewrites their page, and suddenly your memo drops off the citation radar. What do you do? You go back in. You tweak the summary. You sharpen the bullets. You check if your FAQ still matches the questions people actually ask.

GEO is not set-and-forget. It’s a constant race against entropy. The web shifts, the models shift, and you have to shift with them.

## Tracking takes grit

Manual tracking is tedious. Automated dashboards break. Reference rates dip for no clear reason. You find yourself running batch prompts at midnight or scanning Discord alerts before your morning coffee. Sometimes you spend hours chasing a 2 percent lift that nobody outside your team will ever notice.

But the grind is the point. Anyone can optimize once. The teams that win are the ones who keep watching, keep iterating, and never let their memos slip into obscurity.

## Editing without ego

In the GEO world, your favorite turn of phrase might never get quoted. That clever intro? Cut if it doesn’t help your reference rate. The best GEO writers learn to kill their darlings, rewrite for clarity, and structure for the machine as much as for the human. It’s not about showing off. It’s about being useful, being clear, and being the answer the AI needs.

## The invisible work

Most of what makes GEO work is invisible. Readers see the polished memo, not the ten drafts that came before. They don’t see the Discord threads, the “why did our FAQ drop to 5 percent?” debates, or the late-night fixes after a model update. But this is where the real craft lives. It’s in the details, the persistence, and the willingness to keep pushing even when the numbers don’t move.

## Why it’s worth it

GEO is not glamorous. It’s not always fun. But when your memo gets cited by an AI, when your niche topic finally shows up in a generative answer, you know you’ve earned it. You didn’t just chase the algorithm. You put in the work to make sure your knowledge survives.

That’s the grind behind GEO. It’s not for everyone. But if you want your work to matter in the age of AI, it’s the only way to stay seen.

Discover the real work behind staying visible in the age of AI search. This guide breaks down the habits, tracking, and edits that keep your memos in the game.

The grind behind GEO: what it really takes to stay seen


*Measure what matters, iterate with confidence.*

![](assets/geo-tracking-tools.png)

## Why we must track GEO

GEO tracking is about knowing if your content is showing up in AI-generated answers. If you can’t see which memos are being cited, you’re guessing about what works.

- It tells you which articles get picked by AI and which don’t.
- You can see if your updates make a difference.
- You get proof that your work matters when the numbers go up.

## What we need to watch

You don’t need to build dashboards or write code. Focus on these three things:

| **Metric** | **Plain-english meaning** | **Why writers care** |
| --- | --- | --- |
| **Reference rate** | How often does an AI mention your memo when asked relevant questions? | This tells you if your content is visible. |
| **Paragraph winner** | Which part of your memo does the AI quote?  | This helps you see what structure or section works best. |
| **Clicks on surfaced link** | Do people actually click through when your memo is cited?  | This shows if AI citations bring real readers. |

## How to track without coding

You don’t have to build a DIY stack. Here’s what you can do:

- Use a commercial tool like Profound or Semrush AI Toolkit. These are built for non-technical folks. You just sign up, add your main prompts (the questions you want your memo to answer), and run a batch test. The tool shows which memos get cited.
- If you don’t want to use a tool, you can search for your memo’s title or main points in ChatGPT or Gemini and see if it appears in the answer. Keep a simple checklist in Notion or Google Sheets to track which ones show up.

## Tooling paths at a glance

| **Path** | **Set-up time** | **Cost** | **Pros** | **Cons** |
| --- | --- | --- | --- | --- |
| **Commercial pilot**(Profound, Semrush AI Toolkit) | 1–2 h | \$ -- \$\$ | No code, dashboards out of the box | Ongoing fees, fewer custom prompts |
| **DIY stack**(LangChain + Google Sheet + Grafana) | 4–8 h | \$ (API only) | Full control, free to run | Needs a few engineering hours |
| **Hybrid** | 1 h + 4 h | \$\$ | Start fast with SaaS, fall back on DIY | Two systems to watch |

*If you’re not technical, use the commercial pilot path. You can get started in about an hour.

## Example: How to track and improve a Memo

Memo: “How to build a deep-search pipeline”

URL slug: /guides/deep-search-pipeline

**Baseline test (Writer, about one hour):**

1. Sign up for a Profound trial.
2. Paste your 20 GEO test prompts, for example, “According to memo.d.foundation, how do I set up a deep-search pipeline?”
3. Click Run.
4. Export the CSV.
5. See that /guides/deep-search-pipeline is cited in only 4 of 20 prompts (20 percent), below the 10 percent threshold.

**Retrofit the memo (Writer, about two hours):**

- Add a “What you’ll learn” summary at the top.
- Insert “Key takeaways” bullets.
- Wrap steps in a HowTo block and add a short FAQ at the bottom.

**Verification (Writer, about five minutes):**

- Wait 24 hours, then check results.
- Today’s citation count: 12 of 20 prompts (60 percent).
- Celebrate: “Our retrofit raised reference rate from 20 percent to 60 percent in one day”.
- Share screenshot in your team chat as proof.

**Continuous improvement:**

- Repeat for the next low-performing memo.
- Keep an eye on your checklist or dashboard and tweak content if citations dip again.

## The bottom line

You don’t have to be an engineer to track GEO success. Focus on what you can see: is your memo being cited, which part is quoted, and do people click through? Use simple tools or manual checks. The goal is to write content that AI engines want to cite and to know when your work is paying off.

Not sure if your content is showing up in AI search? This guide walks you through simple GEO tracking methods so you can see what works and keep your memos in play.

Stand up GEO tracking tools: a simple guide


## Snapshot view

**Core mechanism:** LLMs do not crawl like search engines; they generate answers from their “memory” (model parameters). GEO optimizes content to be **semantically rich**, **contextually relevant**, and **easy for LLMs to parse**, so it gets **quoted inside AI answers**, not just listed on a results page.

## TL;DR

- **Visibility = reference rate**: Track how often ChatGPT, Gemini, Claude cite you, not where you rank.
- **Semantic richness & granularity**: Treat each paragraph as a standalone answer. Use summaries, bullet points, “In summary” hooks.
- **E-E-A-T matters**: Demonstrate Expertise, Experience, Authoritativeness and Trustworthiness with bylines, case studies, data.
- **Rapid iteration**: Major model updates can change extraction patterns overnight. Review weekly.
- **Platform-specific seeding**: Reddit, YouTube, Quora dominate AI citations. Plant content where LLMs fish for answers.

![](assets/geo-key-concepts.png)

## What is generative engine optimization?

- **Search is shifting from links to language models**
    
    Traditional SEO optimized for keyword-driven, link-based rankings. GEO optimizes for being cited inside AI answers, your content becomes part of the model’s “response,” not just an entry on a results page.
    
- **Visibility = reference rate, not page rank**
    
    Instead of chasing high positions, GEO measures how often an LLM (ChatGPT/Gemini/Claude) references your content. In an AI-first world, will the model remember you?
    
- **Longer, conversational queries**
    
    Users ask 20–30 word prompts; sessions span multiple turns and context carries over. Your content must be structured and semantically clear so the AI can lift it out as a standalone answer.
    
- **E-E-A-T & trustworthiness matter**
    
    Models favor content demonstrating Expertise, Experience, Authoritativeness and Trustworthiness. Back up your points with author credentials, case studies or real-world data.
    (E.g: Showcase Dwarves Foundation’s expertise by highlighting author credentials)
- **Business-model shift: Influence over impressions**
   
   Unlike ad-driven search engines, subscription-based LLMs only surface third-party content when it truly adds value. GEO becomes a game of influencing the model’s memory, not just earning clicks.
- **Emerging GEO platforms & API-driven workflows**
   
   A new ecosystem (Profound, Goodie, Daydream, Semrush AI Toolkit) centralizes prompt testing, citation tracking, and dashboards integrate these via APIs to automate your deep-search experiments.
- **How GEO differs from traditional SEO:**
    
   | **SEO (Traditional)** | **GEO (Generative)** |
  | --- | --- |
   | Ranking within a list of organic search results | Having AI models incorporate your brand/content into their final answer | 
   | Focus on keywords, backlinks, page rank, click-throughs | Focus on language, content structure, semantic clarity, and reference rates |
   | Users click to visit websites | Users get answers directly, may not visit sites |
  | Keyword-based optimization | Language and context-based optimization |


![](assets/geo-key-concepts-claude-result.png)

## Core GEO signals & metrics

**Reference rate**

- % of representative AI queries that cite memo.d.foundation.

**Structured content density**

- Well-organized pages (headings, bullet lists, tables) packed with concise facts.

**Outbound click volume**

- When the AI answer links back, measuring those clicks shows real engagement beyond the model bubble.

## What should we do?

### For content writers

1. **Restructure every page**
    - Write a clear **“What you’ll learn”** 2–3 sentence summary at the top.
    - Break each topic into focused **bullet points** or **Q&A blocks,** treat each as its own answer.
    - Label key sections with headings like **Key takeaways, hot take** or **in summary.**
2. **Use semantic markup**
- Ensure every tutorial or FAQ section is flagged for AI:
    - Wrap your steps in a “HowTo” block.
    - Wrap Q&A pairs in an “FAQ” block.

### For engineers / Technical team

1. **Build a deep-search pipeline**
    - **Query simulator**: Automate sending real-world prompts to LLM APIs (ChatGPT, Gemini, etc.) and record which pages or paragraphs are cited.
    - **Dashboard & alerts**: Feed those results into a monitoring dashboard (e.g., Grafana). Set alerts if a page’s reference rate falls below 10%.
2. **Enforce CI/CD guardrails**
    - **GEO linting checks**: In your build pipeline, run automated checks (e.g., GitHub Actions) to ensure every new page includes summaries, takeaways, and FAQ sections before it goes live.
    - **LLM preview tests**: On each content merge, trigger a quick API call with a standard prompt to confirm the new page surfaces correctly in the model response.
3. **Prompt engineering & fine-tuning**
    - **Prompt templates**: Provide a shared library of example prompts (e.g., “According to memo.d.foundation…”) for your LLM integration.
    - **Light fine-tuning**: If you run an internal LLM, periodically retrain it on your memo content so it more reliably surfaces your branding and phrasing.
4. **Optional edge-Lvel geo-targeting**
    - Deploy a small edge function (e.g., Cloudflare Worker) that reads visitor locale and injects localized snippets (“In Vietnam, best practice is…”) on memo pages to boost regional relevance.

## Why this matters

- **AI-first discovery**: As LLMs become the primary research interface, being in the answer wins direct mindshare, no click required.
- **Competitive moat**: Brands encoded into the AI layer gain lasting recall and preference. Raw impressions alone will not suffice.
- **Inbound engine**: High reference rates drive organic traffic, community growth, and lead generation without relying on Google rankings.
- **Business-model shift**: In subscription-driven LLM ecosystems, content surfaces only when it adds real value. GEO is about influencing model memory, not chasing clicks.
- **Emerging GEO tooling**: Platforms like Profou, Goodie, Daydream, and Semrush AI Toolkit centralize prompt testing, citation tracking, and dashboards. Integrate them via APIs to automate deep-search experiments.

*Source insight from: https://a16z.com/geo-over-seo/*

Learn the essential principles of Generative Engine Optimization (GEO): structure content for AI, boost your reference rate, and get LLMs to quote your pages directly in their answers

Generative engine optimization


> **TL;DR**: As generative AI engines take the wheel in deciding what we see, read, and remember, the question isn’t just about how to optimize for algorithms. The real question is whose stories survive the next wave of digital memory and whose fade away.

## When AI becomes the librarian

AI models like ChatGPT and Gemini are the new librarians of the web. They decide which facts are surfaced, which sources get cited, and which voices echo across the digital landscape. But AI doesn’t make these choices in a vacuum. They learn from what’s already online, what’s popular, and what’s easy to parse.

This means the loudest, most-linked, and most-optimized content rises to the top. Niche expertise, local knowledge, or unconventional perspectives risk getting buried. If you’re not in the training data, you’re not in the answer.

## The power and the problem of citation

Reference rate is the new currency. If your work is cited by AI, you get noticed. If not, you might as well not exist. This changes the game for everyone: big publishers, indie creators, and communities working on the margins.

When a user asks an AI a question, the model pulls from its training data and the live web. But not all sources are equal. Well-optimized, frequently cited content rises to the top. Smaller voices, niche communities, and non-mainstream perspectives risk fading into the background.

But here’s the catch. AI models are trained on what’s available and visible. If your content isn’t structured for AI, or if you don’t play by the rules of GEO, your knowledge could slip through the cracks. The danger isn’t just being ignored. It’s being forgotten.

## Whose knowledge gets preserved?

The web was supposed to democratize information. Now, we’re at risk of letting algorithms decide whose knowledge gets preserved and whose gets left out. Smaller voices, niche communities, and non-mainstream perspectives have always had to fight for visibility. With generative AI, the stakes are even higher.

If a local historian’s blog isn’t cited by generative searching, does that knowledge survive? If a community’s lived experience never gets summarized in an AI answer, does it fade from collective memory? These are not just technical questions. This is about the future of what we know and who we listen to.

## What do we owe each other as stewards of knowledge?

If you’re a writer, editor, or builder of digital spaces, you’re part of this story. The choices you make, what you publish, how you structure it, and who you cite decide what gets remembered.

We should ask hard questions:
- How do we make sure underrepresented voices aren’t erased by algorithmic convenience?
- What can we do to keep the web weird, diverse, and surprising?
- How do we balance optimization with authenticity?

## The stakes

GEO gives us tools to surface knowledge, but it also gives us a responsibility. We can use our skills to lift up stories that might otherwise get lost. We can design for discoverability without flattening everything into the same template.

If AI is the new librarian, let’s make sure its shelves aren’t missing the best, strangest, and most vital books.

*Who gets to be remembered? The answer isn’t written yet. It’s up to us to make sure it’s not just the loudest voices, but the ones that matter most.*

As AI increasingly selects what we read and recall, understanding citations becomes crucial. Discover whose stories risk fading away and how to keep meaningful knowledge visible

GEO and the future of knowledge: Who gets to be remembered?


May was the month we finally shipped the stuff we've been promising ourselves for ages. You know that feeling when you've been talking about reorganizing your desk for months, and then you actually do it? That's what happened with Memo, MCP Playbook, and honestly, how we work as a team.

**Major updates:**

- [**Memo got rebuilt with contributor profiles and on-chain proof**](#memo-ui-overhaul-and-contributor-system-cleaned-up): New homepage, updated TOC, sidebar redesign, visible author info, and NFT minting support. Memo now reflects how we work and who's writing.
- [**MCP Playbook became operational**](#mcp-playbook-now-powers-how-we-document-and-log-project-work): Delivery folders now follow structured patterns (docs/, adr/, .chat/), and tools like observer-log and save_and_upload_chat_log work in real projects.
- [**Consulting inquiries picked up significantly**](#consulting-work-became-a-testing-ground): More client interest flowing in compared to early year, with team members like @minhlq and @hieuvd joining client calls and learning the shift from pure engineering to business-focused consulting.
- [**35+ new entries published across engineering, ops, consulting**](#content-ownership-habits-changed-internally): Covering everything from internal tooling and documentation to growth loops and consulting alignment.

**Supporting systems:**

- [**Prompt DB became the team's shared brain, and PromptKit entered prep**](#promptit-and-prompt-db-entered-the-pipeline): Centralized prompts for writing, debugging, and research with version control. PromptKit adds syncing and repeatable usage patterns.
- [**Observer-log bridged Discord and knowledge base**](#observer-log-now-active-on-discord): We shipped an internal Discord bot to quietly collect discussions, terms, and link drops. It's the foundation of a lightweight reporting layer.
- [**Live demos of vibe coding and MCP Discord integration**](#live-demos-of-mcp-discord-integration-and-ai-assisted-development-workflows): Real-time sessions showed AI-first development workflows from planning to implementation, plus team knowledge base querying through Discord bot integration.
- [**Forward Engineering: May edition**](#capturing-engineering-decisions-through-mcp-builds-and-publishing-infra): Shipped updates include MCP client builds, static site infra, Memo quality pipeline, and site build strategy documentation.

![thumbnail](assets/2025-whats-new-may-thumbnail.png)

## Memo UI overhaul and contributor system cleaned up

The biggest shift this month is the new Memo interface. The homepage now reflects what we're actually publishing. Sidebar structure was updated to highlight real usage flows. Topic folders are no longer buried. Memo now feels like a proper working wiki, not just a dumping ground.

- Table of contents structure was revised to reflect reading intent.
- Contributor names are now visible at the top of each post. This small tweak changed internal habits. More people now care about what they publish.
- We cleaned up visual consistency and spacing between sections, making browsing smoother.
- On-chain NFT minting now works for every published memo with a verified wallet. Minting is optional but adds visibility and ownership tracking.
- Tags and topic routing were made more reliable so content doesn't get lost in the archive.
- A dozen system-level articles were added to explain how Memo actually works: architecture, build log, deployment, static site choices, Git submodules, and more.

Here's a list of documents detailing the development of Memo: https://memo.d.foundation/build-log/memo/

### Content ownership habits changed internally

Publishing workflows shifted from individual efforts to integrated team processes.

- With clearer contributor visibility and article grouping, publishing is starting to feel less like a side-task and more like part of our workflow.
- Contributors now regularly track from ideation to final drafts, helped by better publishing tooling and contributor listing features on Memo.
    
![](assets/2025-whats-new-may-memo.png)

## MCP Playbook now powers how we document and log project work

- The MCP server ecosystem grew throughout May. Discord integration, database queries, GitHub automation, file processing. Each server handles specific workflows our team uses regularly.
- Chat logs sync to the right places without manual copying. Discord webhook integration captures insights from tech channels and stores them as searchable knowledge blocks.
- Used to structure delivery folders with /docs, /specs, /adr, and .chat directories.
- Early team usage shows tools like observer-log and save_and_upload_chat_log working well.
- Prompt syncing to prompt-db and changelog generation now feel more integrated with project flow.

→ Repo: [MCP Playbook](https://github.com/dwarvesf/mcp-playbook)

## Consulting work became a testing ground

Consulting inquiries picked up significantly in May compared to early year. More interesting than the volume increase was how we approached these projects differently.

Team member like @minhlq started joining client calls, learning the shift from pure engineering to business-focused consulting. The challenge isn't technical complexity - it's learning to understand what clients actually need versus what they initially request.

As @minhlq put it during our community call: "You have to guess what they really want. Sometimes they don't even know themselves." This requires a completely different skill set from traditional development work, shifting perspective from pure technical focus to understanding business value and client success metrics. Instead of treating consulting as separate from research work, we're using client projects to validate and refine the tools we're building.

## Article contributions picked up across ops, engineering, and consulting

Content output reached new levels with broader team participation across all functions. More than 35 memos were published this month, spanning:

- System and infra decisions (Makefiles, static sites, Git submodules).
- Product and consulting patterns (growth loops, agency structure, client-side vs team-side models): https://memo.d.foundation/consulting/
- Operational thinking (wealth studies, engagement models, planning frameworks): https://memo.d.foundation/handbook/
- Forward-thinking topics like inefficiency arbitrage, market cycles, and delivery signals

→ Browse all: [memo.d.foundation/updates](http://memo.d.foundation/updates) 

## Promptit and prompt-db entered the pipeline

We moved prompt management from ad-hoc sharing to structured systems and version control:

- PromptKit prep work began with content structure planning and internal syncing systems set up.
- prompt-db now lists operating prompts, templates, and synced prompts to help teams write and track more repeatable LLM patterns.
- The repo doubles as both a prompt library and version history for how prompt thinking evolves over time.

→ Repo: [Prompt DB](https://github.com/dwarvesf/prompt-db)

→ Memo: https://memo.d.foundation/prompts/ 

![](assets/2025-whats-new-may-promptdb.png)

## Observer-log now active on Discord

We deployed automated knowledge capture to track team discussions and shared resources.

- Our new Discord-based bot now logs tech activity, from shared links to concept discussions.
- Captures key context like terms, timestamps, and summary insights without disrupting team flow.
- Feeds into our internal reporting and documentation structure, acting as a passive knowledge collector.

→ Join our network and check it out at **👓・observer-log**: [discord.gg/dfoundation](http://discord.gg/dfoundation) 

![](assets/2025-whats-new-may-observerlog.png)

## Live demos of MCP Discord integration and AI-assisted development workflows

In our last community call included live demos that showed the tools in actual use, we proved our tools work by using them live during the community call. Real queries, real implementations, real feedback when things didn't work perfectly.

**MCP Discord bot querying team knowledge base:**

- Real-time querying of team knowledge base through Discord interface.
- Search functionality across prompt databases and documentation repos.
- Integration with multiple MCP servers (Playbook, GitHub, Context7).
- Live data retrieval showing actual response times and query results.
- User management with encrypted API keys and authorization headers.

**Complete planning workflow with AI:**

- Live coding session from initial brief to implementation using Gemini 2.5.
- Automated generation of overview.md and feature.md specification files.
- Project structure documentation using tree commands for context loading.
- MCP Playbook integration creating ADRs, changelogs, and specification templates.
- Real-time context building with 25+ tool calls for comprehensive understanding.
- Document-first approach showing planning before coding implementation.

These were working sessions that showed both what works and what still needs improvement. When the bot took time to initialize or queries didn't return perfect results, that provided valuable feedback for the next iteration.

## Capturing engineering decisions through MCP builds and publishing infra

We shipped the May edition of [Forward Engineering](https://memo.d.foundation/updates/forward/2025-05/), covering internal experiments like:

- Building MCP clients for Discord.
- Streamlining site deployment with Makefile.
- Memo quality pipelines and Git submodule structure.

The radar this month included key developments: MCP ecosystem expansion, agent-first workflows, vibe-coding approaches, and AI-powered IDE trends. Microsoft's decision to open-source VS Code's backend is particularly interesting - it democratizes AI coding tools and removes the need to fork entire editors just to add AI capabilities.

The format now includes more technical deep dives, meant to be reusable by others across teams. Instead of just tracking market trends, we're documenting what we're actually building and how others can use it.

![](assets/forward-engineering-05-2025.mp4)

## We're building a different kind of company

The changes in May show we're not building a traditional consulting or product company. The shift from consulting-first to research-first is already changing how we allocate resources, approach hiring, and prioritize work.

Our hiring strategy has started leaning toward specific traits: data intuition, architectural thinking, and a sense of aesthetic judgment. We're also preparing for an apprenticeship model to grow these capabilities internally over time.

Knowledge capture through tools like MCP Playbook, Observer Log, and runbooks lays the foundation for smart scaling. When operational knowledge lives in systems instead of people's heads, growth multiplies instead of getting lost.

On the infrastructure side, treasury protocols and automation systems are doing the heavy lifting. When admin runs itself, people can focus on problems that actually require human judgment.

Read more: https://memo.d.foundation/build-log/company

![](assets/2025-whats-new-may-consulting.png)

## What's next in June

June's looking interesting: expanding MCP server capabilities, finalizing vibe coding course materials, continuing to build tools that solve real problems. The apprenticeship program is taking shape, and we're seeing what AI-first consulting actually looks like in practice.

The next phase is moving from AI workflows to AI agents - systems that can orchestrate multiple tools and handle complex planning autonomously. We're already seeing early patterns of what this looks like through our MCP ecosystem and vibe coding approaches.

In May, we rolled out Memo’s on-chain publishing with optional NFT minting, tested internal tooling like MCP Playbook in real usage, and turned consulting projects into spaces to refine our workflow. Prompt DB and Observer Log matured into working systems, while Forward Engineering documented hands-on experiments across the team.

What's new in May 2025


In April, we leveled up Memo from a write-up space into a real knowledge hub. Our internal agent stack became more usable with updated MCP docs, and internal knowledge flows, from consulting to hiring were cleaned up and made easier to share. Highlights from the month at a glance:

- [**Switching to Vietnamese boosted social reach:**](#vietnamese-content-strategy-picked-up-real-traction) With no paid ads, content views jumped 912.1%. Standouts were the March Frontend Report and the guide on selecting vector DBs for LLM apps.
- [**Memo got reorganized, easier to read and contribute to:**](#memo-got-a-clearer-structure-contributor-profiles-and-a-better-publishing-flow) Content is grouped by topic, key sections are pinned, and contributor info is live. Publishing also runs on checklists.
- [**We cleaned up how our internal tools fit together:**](#clarifying-our-internal-agent-stack-with-mcp-docs-and-brain-db-syncing) MCP Playbook got documented, prompts are now synced centrally, and team chats are starting to turn into reusable knowledge blocks in Brain db.
- [**Consulting delivery aligns better with hiring and external plans:**](#aligning-consulting-delivery-with-hiring-signals-and-new-partnership-pilots) The delivery structure is now synced with BD and hiring signals. A pilot program is being prepped to support developers in NGO/NPO projects.
- [**Making internal output more visible and reusable:**](#making-internal-work-more-visible-and-reusable-across-the-board) Engineering and market updates now live in one place. Monthly build logs and learning notes help track growth.
- [**Updated handbook to reflect how we really work:**](#updated-handbook-to-reflect-how-we-work-today) Clearer company vision, role focus split, and refreshed policies for side projects, moonlighting, and open-source support.

![thumbnail](assets/2025-whats-new-april-thumbnail.png) 

## Vietnamese content strategy picked up real traction

April marked our move to Vietnamese-first content on socials. It clicked. Without spending a cent on ads, we saw a significant bump across the board:

- 141.9K views, up 912.1% from March.
- 453.5% increase in content interactions.
- All organic traffic.

Two posts stood out in particular:

- [Frontend Report (March)](https://www.facebook.com/share/p/1LjHQgtRiA/) got the most interactions.
- [Select Vector Database for LLM apps](https://www.facebook.com/share/p/1AcMs3Zffn/) has gained strong traction in the dev community.

## Memo got a clearer structure, contributor profiles and a better publishing flow

Memo is shifting from a place for write-ups into a proper knowledge base. We focused on reorganizing how content is grouped, credited, and match how we actually search and learn:

- Pinned sections like Brainery, Data Engineering, Prompt Engineering now lead the way for hands-on learning.
- Content is grouped into themes like AI Ops, Productivity, and Engineering to help readers browse more easily.
- Each piece of content moves through four levels: from quick notes to polished insights. This gives the team a clear path to document and reuse knowledge.
- Contributor profiles are live. Posts now show who’s behind the work, paired with a consistent visual style and on-chain minting for visibility and ownership.
- An audit checklist and content calendar are in place to keep everything timely, no more relying on memory or manual follow-ups.

→ Visit: https://memo.d.foundation/handbook/memo/content-levels/

![memo-content-level](assets/2025-whats-new-april-memo-content-level.png)

## Clarifying our internal agent stack with MCP docs and Brain db syncing

We worked on making our internal agent-based tools easier to understand and adopt across the team. The goal is to help the team see what powers our AI-first workflows, how to contribute, and how to apply these tools in projects.

- The MCP playbook server is now documented and shipped. It helps agents organize project knowledge into structured folders, like specs, changelogs, ADRs and save chat logs to the right places.
- We started syncing insights from internal chats into Brain db, turning casual discussions into structured knowledge that teams can build on.
- A new Playbook format is being drafted to help guide how we use internal tools throughout the software delivery cycle (SDLC).
- PromptKit and Prompt Playground are being prepared behind the scenes. A proper update is planned for May.

→ Repo: [MCP Playbook](https://github.com/dwarvesf/mcp-playbook)

## Aligning consulting delivery with hiring signals and new partnership pilots

Last month, we worked on tightening the link between how we deliver projects and how we grow the team. The focus was on making expectations clearer, surfacing hiring trends, and setting up better ways to support external work:

- Rolled out a new consulting delivery structure, in sync with aligned with the business team, so execution matches client direction from the start.
- Restarted signal tracking for hiring, especially in AI/data, so our hiring plans reflect where the demand is.
- Kicked off an internal pilot for NGO/NPO developer partnerships, exploring what support and impact can look like outside of client work.
- Began standardizing case study rewards for partnerships, so good work gets documented and recognized properly.

## Making internal work more visible and reusable across the board

We put effort into closing the gap between what gets built and how that work gets shared internally. A few structure changes are now in place to make team efforts easier to surface and connect:

- Merged engineering and market reports into a shared forward-engineering format, so what we ship lines up with the signals we track.
- Started logging build updates and monthly learning highlights in one place to keep track of our output and how we grow.
- Experimented with data contribution incentives to encourage team members to document insights that others can learn from or build on.

## Updated handbook to reflect how we work today

The Employee Handbook got a meaningful update this month, less about rules, more about clarity on how we work and where we’re heading together:

- Company vision now emphasizes co-creation: we build the future with the team, not just for it.
- Career growth structure added clearer expectations: 90% of your time is for your current role, 10% for long-term career bets.
- Open-source and venture support now better aligned: clarified how we backside projects that align with our values.
- NDA & moonlighting policies got an update to match the reality of cross-project and part-time collaboration.

→ Read the Handbook: https://memo.d.foundation/tags/handbook/

![how-we-spend-money](assets/2025-whats-new-april-how-we-spend-money.png)

In April, we reorganized Memo into a clearer knowledge hub, made internal tools easier to adopt with MCP documentation, and aligned consulting delivery with hiring signals. Our shift to Vietnamese content on social media sparked strong engagement, while weekly team efforts continued to surface insights through build logs and learning highlights.

What's new in April 2025


In March, we rolled out structured OGIF demos, launched key internal AI tools (GitHub Agent & MCP DB), and wrapped up the ICY-BTC swap. We also improved memo.d.foundation's UI, introduced meme culture internally, and our BD team tapped into Asia's Web3 and AI scenes to spot what's ahead. Here's the quick summary:

- [**Pushing AI-first workflows with GitHub Agent & MCP DB:**](#reinforcing-our-ai-first-mindset-with-internal-tooling) Automated PR management and structured data access to streamline internal operations.
- [**Sharing team progress through demos and case studies:**](#creating-space-for-team-wide-sharing-through-ogif-demos-case-studies) Showcased project updates and hands-on learnings that help connect engineering to everyday work.
- [**ICY-BTC swap finalized with internal demos and guides:**](#finalizing-icy-to-btc-transition-and-aligning-it-with-earning-strategies) Transition completed and support materials published on valuation and usage.
- [**memo.d.foundation UI upgraded:**](#upgrading-ui-memodfoundation-with-a-smoother-flow-and-better-look) Improved usability, content structure, search functionality, and integrated NFT minting. The handbook was also updated with policies reflecting current tech and consulting dynamics.
- [**Making office life part of the daily rhythm:**](#bringing-office-life-into-everyday-team-culture) Rolled out the 💩・tech-meme Discord channel to bring in humor and subtle shifts that make the office feel more like a shared space.
- [**Participated in Asia's Web3 & AI events:**](#tapping-into-the-web3-scene-real-signals-from-builders-on-the-ground) Joined regional events to observe how builders are shifting toward long-term, community-driven ecosystems.

![](assets/2025-whats-new-march-thumbnail.png)

## Reinforcing our AI-first mindset with internal tooling

March pushed us further toward an AI-first workflow by formalizing internal policies that encourage scripting and system-driven operations. Two new systems are now up and running:

### GitHub agent

Built on the Mastra framework, this system automates pull request monitoring, sends reminders for blockers like pending code reviews or merge conflicts, and posts weekly project summaries to Discord. It integrates seamlessly with our GitHub workflow and helps reduce review cycle bottlenecks.

→ Explore the repo: [github.com/dwarvesf/github-agent](https://github.com/dwarvesf/github-agent)

### MCP database

As part of our agentic stack, the MCP server supports querying PostgreSQL, DuckDB, and GCS-stored Parquet files. It exposes structured data for internal workflows and research tools, enabling use cases like real-time trend tracking and Discord queries (e.g., `?df upcoming birthday`). Built for extensibility, it includes a plugin-style interface for custom tools and handlers.

→ Explore the repo: [github.com/dwarvesf/mcp-db](https://github.com/dwarvesf/mcp-db)

These tools are already making our day-to-day smoother, helping cut down small blockers and freeing up time to focus on deeper work. We're building exactly the tools we need, one improvement at a time.

![](assets/2025-whats-new-march-github-agent.gif)

## Creating space for team-wide sharing through OGIF demos, case studies

March marked a deliberate shift in how we share and celebrate our work. The team introduced a structured format for OGIF demos, encouraging team members to present updates through lightning talks in a casual, open setting. These demos created space to surface behind-the-scenes work and helped connect the dots across teams.

### Highlights from the month

- **ICY-BTC swap:** @hnh walked through the swap mechanism and updates to ICY valuation logic, following February's launch.
- **GitHub bot:** @thanh introduced a new automation agent that handles PR reminders and activity summaries to reduce friction in code review cycles.
- **MCP integration & GitHub reminder bot:** Showcased MCP's integration into internal workflows and revisited the GitHub bot's reminder features, rounding out the month's focus on tooling and automation.
- **Memo UI improvements:** The team shared updates to [memo.d.foundation](https://memo.d.foundation/), focusing on readability, homepage structure, and contributor visibility.
- **MCP-db agentic:** @hnh explained how the MCP database supports automated workflows by handling structured queries across PostgreSQL, DuckDB, and GCS.
- **Pocket turning & Recapable:** @vincent demoed early gameplay builds and and outlined next steps for both projects.
- **Funding rate arbitrage:** @antran presented a multi-exchange trading strategy based on funding rate differentials, highlighting both technical setup and risks.

These demos reflect the team's commitment to transparency and progress, setting the stage for future milestones.

### Case studies: Turning output into insight

We continued documenting our work through technical write-ups and internal showcases on [memo.d.foundation](https://memo.d.foundation/):

- [ICY swap series](https://memo.d.foundation/tags/icy/): Covered token pricing, the mint/burn mechanism, and a practical guide to the ICY-to-BTC transition.
- [Screenz.ai](https://memo.d.foundation/playground/use-cases/ai-interview-platform-mvp/): A case study on building an MVP for an AI-powered interview platform, by @thanh.
- [Hedge Foundation](https://memo.d.foundation/playground/use-cases/create-slides-with-overleaf/): A workflow breakdown on using Overleaf and AI to streamline documentation and slide-making, by @ohagi.

## Finalizing ICY-to-BTC transition and aligning it with earning strategies

In March, the ICY-to-BTC swap officially went live following February's demo and final testing. With the system now in place, team members have a reliable way to convert ICY rewards into BTC, supporting our shift toward more sustainable earning strategies.

This rollout also tied into our internal focus on financial literacy. Throughout the month, we ran internal demos to walk through the ICY-to-BTC swap and introduced the guide to help the team better understand the mechanics and value behind the transition.

To support the adoption, we published:

- [A tutorial on how to perform the swap](https://memo.d.foundation/handbook/community/how-to-swap-icy-to-btc/)
- [A breakdown of the mint/burn mechanism](https://memo.d.foundation/playground/blockchain/cross-chain-transfers-implementing-a-token-swap-from-base-chain-to-bitcoin/)
- [A guide to how ICY token pricing works](https://memo.d.foundation/handbook/community/how-to-swap-icy-to-btc-copy/)

All resources are available on: <https://memo.d.foundation/handbook/community/icy>

![](assets/2025-whats-new-march-icy-tipping.png)

## Upgrading UI [memo.d.foundation](http://memo.d.foundation) with a smoother flow and better look

Last month marked a key update for [memo.d.foundation](http://memo.d.foundation/), our digital knowledge hub. The team wrapped up a round of UI upgrades to make Memo feel smoother and more structured. These changes aim to make learning in public more accessible for both readers and writers:

- Tweaked layout and spacing for easier reading across pages.
- Reorganised the homepage to help surface relevant content more clearly.
- Added minting for NFTs and proof of reading, now working without login sessions.
- Improved search to return more relevant results, faster.
- Contributor pages now show author history and related posts.
- Cleaned up folder structure, removed outdated content, and restructured the Handbook.

Alongside these UI changes, the Handbook and Playbook sections were updated to reflect how we operate today, with clearer policies, processes, and references aligned with the fast pace of tech and consulting work. From client engagement to internal operating, the goal is to make it easier for the team to find what they need and keep moving.

We're ready to shill more. Let us know what you think.

![](assets/2025-whats-new-march-mint-nft.png)

## Bringing office life into everyday team culture

We've taken steps to make the office a more welcoming space, aligning with our policy of bringing office life into our daily experience. This month, we launched a small but fun initiative - 💩・tech-meme channel to bring some lightness and shared humor into our internal culture. Team members share memes on Discord, archiving them on Google Photos to preserve these moments.

Additionally, two months into our transition from remote-first to hybrid, the presence at the office has become steady. The space now feels less like a traditional workplace and more like a spot where conversations happen naturally, ideas bounce around, and people find their rhythm together. Such a subtle shift, but one that we think will deepen our team's sense of belonging in the long run.

![](assets/2025-whats-new-march-tech-meme.png)

## Tapping into the Web3 scene: Real signals from builders on the ground

March brought a packed schedule for our BD rep @minh, who joined four standout events: XDC Network, Building Asia's Web3 Ecosystem Roadshow, Berachain: Growing in Asia with a Fun Community, Babylon: A New Way to Use Bitcoin.

There's still a lot of noise in the space, but you can tell some builders are trying to shift things. The bigger question from these sessions: Can Asia's Web3 scene turn its energy into something that lasts? Feels like the pieces are there.

For the full take, Minh shared two short write-ups from the road: [Talks and Takeaways from the Scene – Part 1](https://memo.d.foundation/updates/biz/2025-web3-vietnam-recap-pt1) and [Part 2](https://memo.d.foundation/updates/biz/2025-web3-vietnam-recap-pt2). Give them a read if you're curious about where Web3 might actually be heading.

![](assets/2025-whats-new-march-event.png)

## What's moving to April

- **Demo & recognition:** Deepen engagement in OGIF sharing, increase team participation, and boost visibility around peer recognition.
- **Office culture:** Roll out the "meme of the month" and "meme lord" role, and continue building small culture moments to strengthen team bonds.
- **ICY-BTC swap:** Collect usage data and feedback, and refine accordingly.
- **AI-first tools:** Expand GitHub Agent and MCP DB usage with new automation workflows based on internal input.
- **Memo UI:** Explore further integrations to improve accessibility.
- **Event participation:** Continue exploring AI & Web3 scenes, identifying events that support strategic relationships and learning.

Got ideas to make these even better? Hit us up on [Dwarves Discord](https://discord.gg/dfoundation).


Last month, the team kicked off structured OGIF demos, launched GitHub Agent and MCP DB to support internal automation, finalized the ICY-BTC swap, and rolled out UI and handbook updates on memo.d.foundation. We also set a more consistent office rhythm with meme culture picking up, while the BD team tuned into regional AI and Web3 events to stay close to what's happening next.

What's new in March 2025

In OGIF 41, the team covered key updates on the ICY-BTC swap, GitHub bot automation, MCP-DB system for agent workflows, and progress on the Pocket Turning and Recapable projects and we also shared insights into funding rate arbitrage strategies.

#41 ICY-BTC, GitHub bot, MCP-DB, Pocket Turing

OGIF office hours #41 - ICY-BTC swap, GitHub bot, MCP-DB, Pocket Turing, Recapable, and arbitrage strategy


- [**From remote-first to hybrid:**](#the-transition-to-hybrid-mode-strengthening-team-presence-with-coordination-and-perks) We've transitioned to a hybrid model, coordinated schedules, and rolled out perks like lunch support, transport coverage, and an Office Leaderboard to keep engagement high.
- [**ICY to BTC transition is in motion:**](#icy-to-btc-transition-from-experiment-to-the-next-chapter) ICY to BTC transition is in motion: We completed the first demo, proving the swap mechanism works. Now, we're in the final testing phase before the official launch.
- [**Reporting tech signals:**](#reporting-tech-signal-forward-engineering-2024) Dwarves Forward Engineering 2024 with moving in AI agents, blockchain applications, and the evolving talent market, key trends we're keeping an eye on.
- [**Engineering solutions in action:**](#technical-case-studies-updated-engineering-solutions-across-ai-data-and-trading-systems) We've updated case studies covering AI-powered project reporting, security enhancements, real-time trading analytics, and optimized data storage.
- [**Skip-level meeting with CEO:**](#skip-level-meeting-open-conversations-with-ceo) A space for direct, open discussions about challenges, new ideas, and improving how we operate.
- [**Annual health checkup:**](#annual-health-check-up-keeping-the-team-in-check) Routine screenings are scheduled for team members in HCM and Hanoi, with travel support for those in other locations.
- [**Health insurance renewal in progress:**](#health-insurance-renewal-in-progress) Bao Minh renewal process is underway, with details being finalized and updates coming in Basecamp.
- [**New Year gathering kicked off the year:**](#team-moments-new-year-gathering--tết-celebrations) We reunited to share stories and set the tone for 2025.

![](assets/2025-whats-new-feb-thumbnail.png)

## The transition to hybrid mode: Strengthening team presence with coordination and perks

One month into the Hybrid Working model, and we're picking up the pace. The shift from remote-first to hybrid means more structured office days, better team alignment, and a smoother workflow.

To keep things running efficiently, we've:

- Coordinated team schedules so office days are planned with purpose.
- Workspace upgrades: Apple Studio Displays and Herman Miller chairs are now in place, with more improvements on the way.
- Added perks: lunch support, transport coverage (3 ICY per check-in), and stocked office supplies.
- Launched the Office Leaderboard with the office-lover role: shoutout to [@quang](https://github.com/lmquang) and [@vincent](https://github.com/tuanddd) for topping the chart this month. They'll enjoy a free drink for every office day next month as a reward.

More hands in, fewer blockers. Got ideas to make the workspace better? Drop them in 🏢・lobby or open a support ticket. We're listening.

![](assets/2025-whats-new-feb-backt-to-office.png)

## ICY to BTC transition: From experiment to the next chapter

ICY started in 2020 as our first community experiment, evolving into a reward system by September 2022. Since then, it has powered engagement, rewarding contributions in discussions, research, and beyond.

Last month, we demoed the ICY-to-BTC swap, a major step toward transitioning to a more sustainable and future-proof reward system. The swap interface is in place, and the mechanics are working. Now, we're fine-tuning the final details before the official launch.

What's next?

- Final testing and security checks.
- Launch announcement with a step-by-step guide.
- Support for a smooth transition.

Stay tuned for the final rollout.

![](assets/2025-whats-new-feb-icy.png)

## Reporting tech signal: Forward engineering 2024

In 2024, we've mapped out key emerging technologies and their business impact to refine our technology roadmap and pinpoint the trends with the most potential across different markets.

Key highlights:

- AI agents are shifting from no-code to developer-driven workflows, with teams favoring self-hosted AI tools for better control.
- On the blockchain side, AI-powered on-chain actions are being explored for smart contract analysis and automated trading.
- Full-stack and AI/ML engineers remain the most sought-after roles, while AI automation is reshaping traditional software development. VC funding is leaning toward leaner, cost-efficient AI solutions.
- More to watch: AI governance, performance optimizations (DuckDB, WASM), and decentralized identity tech.

For the full read, [check out.](https://memo.d.foundation/updates/forward-engineering/2024-2025/)

![](assets/2025-whats-new-feb-forward-engineering.png)

## Technical case studies updated: Engineering solutions across AI, data, and trading systems

In this cycle, we focused on refining systems, improving performance, and integrating AI across our projects. Here's what the team has been working on:

- [Project reports system](https://memo.d.foundation/playground/use-cases/ai-powered-monthly-project-reports/) _([@tom](https://memo.d.foundation/contributor/tom)):_ Structuring raw data into insights that power operations.
- [AI-powered Ruby travel assistant](https://memo.d.foundation/playground/use-cases/ai-ruby-travel-assistant-chatbot/) _([@tom](https://memo.d.foundation/contributor/tom)):_ Leveraging Ruby + AWS Bedrock for a secure and maintainable AI assistant.
- [Binance transfer tracking](https://memo.d.foundation/playground/use-cases/binance-transfer-matching/) _([@bienvh](https://memo.d.foundation/contributor/bienvh)):_ Transforming fragmented transaction logs into structured fund flow data.
- [BTC-altcoin hedging indicators](https://memo.d.foundation/playground/use-cases/bitcoin-alt-performance-tracking/) _([@bienvh](https://memo.d.foundation/contributor/bienvh)):_ Visualizing performance metrics with Matplotlib & Seaborn.
- [AI chatbot for project management](https://memo.d.foundation/playground/use-cases/building-chatbot-agent-for-project-management-tool/) _([@thanh](https://github.com/zlatanpham)):_ Automating workflows using LangChain, LangGraph & GPT-4.
- [Centralized monitoring for trading](https://memo.d.foundation/playground/use-cases/centralized-monitoring-setup-for-trading-platform/) _([@thanh](https://github.com/zlatanpham))_ , _([@quang](https://github.com/lmquang)):_ Implementing Grafana & Prometheus for real-time alerts and system integrity.
- [Crypto market visualization in Golang](https://memo.d.foundation/playground/use-cases/crypto-market-outperform-chart-rendering/) _([@bienvh](https://memo.d.foundation/contributor/bienvh)):_ Interactive charts tracking BTC-Alt dynamics.
- [Data archival & recovery](https://memo.d.foundation/playground/use-cases/data-archive-and-recovery/) _([@bienvh](https://memo.d.foundation/contributor/bienvh)):_ Long-term stability strategies for high-volume trading systems.
- [Database security hardening](https://memo.d.foundation/playground/use-cases/database-hardening-for-trading-platform/) _([@thanh](https://github.com/zlatanpham)):_ Strengthening access control with RBAC, MFA, and network isolation.
- [Binance PNL analysis with Phoenix liveview](https://memo.d.foundation/playground/use-cases/implement-binance-future-pnl-analysis-page/) _([@minhtran](https://github.com/thminhVN)):_ Real-time portfolio tracking using server-side rendering & WebSockets.
- [Migrating to TimescaleDB](https://memo.d.foundation/playground/use-cases/migrate-normal-table-to-timescale-table/) _([@minhtran](https://github.com/thminhVN)):_ Boosting query performance with hypertables.
- [Hedge Foundation UI optimization](https://memo.d.foundation/playground/use-cases/optimizing-ui-for-effective-investment-experience/) _([@anna](https://memo.d.foundation/contributor/anhtran/)):_ Improving investment dashboards for seamless decision-making.
- [Historical data persistence](https://memo.d.foundation/playground/use-cases/persist-history-using-data-snapshot-pattern/) _([@bienvh](https://memo.d.foundation/contributor/bienvh)):_ Implementing data snapshots for efficient long-term storage.

![](assets/2025-whats-new-feb-usecase.png)

## Skip-level meeting: Open conversations with CEO

Last month, Skip Level Meetings kicked off, offering a direct space to raise blockers, no back-and-forths, just a space to bring up challenges, new directions, feedback, and talk about what's working (or not).

Whether it's about team operations, roadblocks in projects, or simply sharing thoughts on where we're headed, this is a chance to have real discussions that drive change.

If there's something on your mind, this is the place to discuss it.

## Annual health check-up: Keeping the team in check

We are preparing for the annual health checkup, ensuring everyone gets their routine screening done. Team members in HCM and Hanoi will have designated locations, while those from other areas can arrange travel to complete theirs.

For any questions, reach out to [@innno\_](https://github.com/innnotruong).

## Health insurance renewal in progress

The Ops Team is managing the renewal process for our Bao Minh health insurance to ensure continuous coverage for everyone. Details are being finalized, and updates will be shared in the Basecamp thread once the process is complete. Stay tuned.

## Team moments: New year gathering & Tết celebrations

We kicked off the Year of the Snake with our team reunion, creating space to share stories, reconnect, and set intentions for the year ahead. These moments remind us why we do what we do, building not just great technology but a community where everyone can thrive.

[Check out Weekly Digest #15](https://memo.d.foundation/updates/digest/15-new-year-gathering/) for photos and highlights from our New Year gathering.

![](assets/2025-whats-new-feb-tet-gathering.png)


Each month, we roll out a recap of our team and community's strides forward. February's recap covers the hybrid mode shift, ICY-to-BTC swap testing, updated use cases with AI and trading solutions, skip-level meetings, and the New Year gathering kickoff.

What's new in February 2025

In OGIF 39, the team explored React 19 and Deno Deploy updates, database scaling with CI and migrations, Tom’s AI-driven dev workflow, and macro insights on protectionism and globalization trends.

#39 Frontend report, DB Scaling, AI Workflow

OGIF office hours #39 - frontend updates, database scaling, AI workflow, and macro insights

In OGIF 38, the team explored Erlang automata, AI and fintech market shifts in Southeast Asia, year-end reflections with team awards, and a new hybrid work direction for 2025.

#38 Erlang automata, AI Trends, Year-End Awards

OGIF Office Hours #38 - Erlang automata p2, market report, DOTY, Year end celebrations 

Closing another milestone with 2024, it has been a year of building and rebuilding ,  strengthening what works, fixing what doesn't, and uncovering new paths along the way. Every milestone reached this year carries the marks of teamwork and persistence.

2024 in review


> **Recap:** Our visit to DZS Media, a successful film production company, showed us how another creative industry approaches quality and production. Their meticulous planning, expertise-driven decisions, and commitment to getting things right the first time mirror effective software development principles and reinforce the value of cross-industry learning.

The tech world has much to gain by learning from other industries. Techies always look for unconventional ways to seek insights and learnings. Recently, we had the opportunity to visit DZS Media, a film production company in Ho Chi Minh City, the powerhouse behind hits like "Siêu Lừa Gặp Siêu Lầy" and "Chị Chị Em Em 2".

During our visit, we witnessed DZS Media's meticulous production process. They've built a facility for every purpose - soundproof recording studios, talent training rooms, reference libraries - leaving no detail overlooked. Their discipline and work ethic were stunning. Every step was engineered to get it right the first time, a requirement in the film industry.

We were stunned to discover DZS Media's process mirrors our own software engineering practices. The high cost of film redos means that they need to understand the importance of getting it right the first time, and be super meticulous in their work, and they understand the importance of getting it right the first time. Their processes are structured to ensure that there is not need for a redo. This was a huge reminder for us as software engineers.

- Be an expert in your craft, then expand to bigger things.
- The film production process is mostly waterfall, so it's crucial to ensure that each step is done correctly to avoid high costs for redos.
- DZS Media's margin is high, but the success rate is not that high. Therefore, it is essential to have an expert eye to know which movies might have a higher chance of success. Same way, we choose which software development projects to be part of.
  • The content of a film must be good to be successful, regardless of the marketing, advertising, or famous actors.

Despite their success, DZS Media stayed humble. We were awed by their ability to wrangle celebrities and foster an environment where creativity and hard work thrive. We left with profound respect for the film industry - and the Herculean efforts behind blockbusters like Chị Chị Em Em and Siêu Lừa Gặp Siêu Lầy.

Our visit to DZS Media was an eye-opening experience, and we are grateful to have had the opportunity to learn from such a talented and dedicated team. We believe that we can take some of the lessons we learned during our visit and apply them to our own industry. We hope to have the opportunity to work with DZS Media in the future and see what we can learn from them again.

Til next WALA.

![Dwarves team visiting DZS Media](assets/dzs-media-wala.webp)

---

**WALA: to walk around, learn around.**

In our line of work, we hear and talk about domain knowledge all the time. WALA aims for exactly that: we, people in tech, take a break from sitting in front of our computers, to go out, connect with new people, and get to understand other businesses.

Through stories collected from Techie WALAs, we hope our community members get the chance to learn from others' successes and failures, gain insights into what works and doesn't, and reflect on their own works and practices.

Besides, breaking away from the stereotype of "tech people are introverts" is always fun.


Our visit to DZS Media revealed surprising parallels between film production and software development. Their meticulous planning, focus on getting things right the first time, and expertise-driven approach offers valuable insights for our engineering practices.

DZS Media

#2 Film production lessons for software engineering


Remote work is great, but there's something about the in-person vibe that helps us learn, share, and connect. To make the most of our hybrid style, we’ve set up an easy check-in process to reward those who pop by the office.

![Check-in at office to earn ICY tokens](assets/check-in-earn-icy.webp)

## Arriving at the office

Find your spot and get comfortable. Our office is set up for focus and creativity, so you’ll find a space that works for you.

## Connecting to the office wi-fi

Once you’re settled, make sure to connect to the office Wi-Fi. This keeps you linked to our system and ensures you’re ready to check in.

## Getting on Discord

Open Discord on your device and make sure you’re logged into the Dwarves server. If you haven’t joined yet, now’s the time.

## Checking-in

Head over to **`🏢・lobby`** channel. Type "gm" (short for "good morning") and hit send. That’s it, you’re officially checked in for the day.

## Earning your ICY tokens

After your "gm" message, our system will credit you with 5 ICY tokens, worth about $7.5. It’s our way of saying thanks for being here and joining the in-person energy.

## Making the most of your time

You’re all set. Now’s your chance to catch up with teammates, share ideas, or just enjoy the office vibe. These face-to-face moments make all the difference.


A guide on how to check in at the office and claim ICY token rewards.

Office check-in process for earning ICY


## Record & reward sharing at Dwarves

If you're part of the Dwarves community, you'll notice our culture of continuous learning and knowledge sharing. This culture isn’t just about individual growth; it’s also about building a strong, connected community.

We believe learning is key to success and our goal is to create an environment where it’s prioritized, valued, and rewarded, allowing everyone to grow.

To support this, we’ve organized a variety of engaging events and activities that encourage and recognize knowledge sharing. Additionally, we allocate a portion of our profits to acknowledge these contributions with awards.

## Our approach to learning and growth

Learning goes hand in hand with a growth mindset. In our fast-moving industry, staying ahead means picking up new knowledge all the time. The more knowledge you share, the more rewards you earn. It’s that simple.

## Monthly pool of up to 2500 ICY for recognized contributions

We’ve set aside a monthly pool of **2500 ICY (around $4000)** to reward those who contribute valuable insights. **70%** of this pool is dedicated to those who actively share knowledge across the community.

Additionally, we place extra value on contributions in key areas like **AI/LLM**, **Golang**, **Software Architecture**, and **Blockchain**. If you’ve got expertise in these fields, your insights will be especially appreciated and may earn you more ICY.

Check out the [**🧊・earn-icy**](https://discord.com/channels/462663954813157376/1006198672486309908/1239502938918096960) channel to see how we distribute our ICY and get involved.

## How you can participate and make a contribution

If you have something worth sharing? Drop useful links in our research channels such as [**💻・tech**](https://discord.com/channels/462663954813157376/810481888619135046/1281086341995565057), [**💡・til**](https://discord.com/channels/462663954813157376/1001883339046797342/1281097209072320615) to get recognized. Got a topic in mind? Present it in our OGIFs or submit a note to our [**memo**](https://memo.d.foundation/). Community members are welcome to participate too.

We also love open-source work, especially building tools that boost our productivity. If you’re into that, join the force at [**🦄・build**](https://discord.com/channels/462663954813157376/1280726623414390805/1280791483280261161) and start cooking up something great.

We hope this push will keep our learning culture strong and moving forward.

Happy coding and sharing!


Discover how the Dwarves community fosters a culture of continuous learning and knowledge sharing. With a monthly reward pool of up to 2500 ICY, contributors are recognized for sharing valuable insights, especially in areas like AI/LLM, Golang, and more. Get involved and grow with us.

Record and reward sharing at Dwarves


To keep everything running smoothly, it’s important that we all follow a clear process when requesting leave. Whether you’re planning a half-shift or a full day off, we want to make sure your absence doesn’t disrupt the team or the project.

By following these steps, you help ensure that everyone is on the same page and that your work is covered while you're away:

### Before request submission

Discuss your leave with the client and team in advance to align tasks and minimize the impact on the project.

### How to submit request

- Log in to Basecamp.
- Create a ticket in the Woodland channel > On-Leave Request list.
- Use the format: Name | Type of absence (off/remote) | Date | Shift (if any).
- Assign to: Project Manager, Account Manager, and Project Lead.
- Timing:
  - **Urgent**: Immediate
  - **Non-urgent**: 2x absence duration
  - **Holiday**: 1-2 weeks in advance

For example, if Thanh Pham plans to have his day off on both Jul 9th to 12th, the request must be submitted 8 days in advance, on Jul 1st. If Thanh Pham's mentor is Han Ngo, the request should be formatted as follows:

![Leave request form example](assets/leave-request-calendar.webp)

### Verification & notification

After submitting the request, the line manager and leader will discuss the request with you. They will work with you to align the workload and resources to ensure the project remains on track. A working process will be designed to prevent any interruptions during your absence.

### Approval/denial

If your request is approved, the manager will mark the ticket as done and note your return date. Basecamp will send an approval email to everyone involved, and the Google Calendar will be updated.

Since the client doesn't receive Basecamp notifications, you or the manager must inform the client via email. If denied, the manager or lead will note the reason in the ticket.

### Announcement

Once your request is approved, a short informal message should be delivered to the related team channel to notify other team members. On the client side, you must announce your leave to the client’s communication channel and remind them before the leave.

### Holiday notifications

1-2 weeks before the holiday starts, Operations will send an official email announcement to all clients about the holiday period. Then, 2-3 days before the holiday begins, your Project Manager or Leader will remind clients informally via Slack or other communication channels.

**Note**: During holidays or days off, unless stated as URGENT, we should NOT respond to clients on that day.


A consistent on leave process prevents a company from being accidentally disrupted when an employee request to be absent.

Leave request

Submit a leave request


### Objectives

As an Ops Team/Manager member, it’s important to manage leave requests effectively to ensure smooth project operations and clear communication.

This checklist guides you through verifying, approving, or denying leave requests, and handling holiday notifications, helping to keep everything on track.

### Verification & notification

- [ ] Acknowledge the employee's leave request.
- [ ] Discuss the request with the employee.
- [ ] Confirm the leave details.
- [ ] Align workload and resources to prevent interruptions.
- [ ] Reassign critical tasks (if necessary).
- [ ] Plan for to covering the employee’s responsibilities (if necessary).

### Approval/denial process

After receiving the Basecamp ticket notification:

**If Approved**

- [ ] Mark the ticket as done and note the employee's return date.
- [ ] Ensure Basecamp sends a notification to involved parties and updates Google Calendar.
- [ ] Inform the client via email.
- [ ] Update the project timeline (if necessary).
- [ ] Monitor project progress during the employee's leave.

**If Denied**

- [ ] Note the reason in the ticket.
- [ ] Inform the employee and provide feedback (if applicable).
- [ ] Suggest alternative solutions or adjustments (if possible).

### Holidays

**1-2 Weeks Before Holiday**

- [ ] Send an official announcement via email to all clients.
- [ ] Confirm that all ongoing projects have a holiday plan in place.
- [ ] Announce the holiday schedule on Discord to all team members.

**2-3 Days Before Holiday**

- [ ] Remind clients informally via Slack or other communication channels.
- [ ] Review the holiday plan with the team to address any last-minute issues or concerns.
- [ ] Send a short reminder about the holiday schedule on Discord.


The checklist of leave and request for the team.


## Objectives

An off-boarding process must ensure three things:

1. Your employee feels good.
2. The departure causes minimal disruption.
3. The termination process must be well-wrapped to make sure the company policy and procedures are all conformed.

## Project offboarding

- [ ] Last day confirmation with client by email
- [ ] Resource replacement
- [ ] Project handoff completed
- [ ] Source code backup

## Company offboarding

### Exit interviews and final communications

- [ ] Exit interview with lead/manager
  - [ ] Gather feedback
  - [ ] Invite to join alumni activities on discords/event
- [ ] Exit talk with HR/Ops
  - [ ] Remind about important points in the Contractor Agreement
- [ ] Last day & final paycheck informed
- [ ] Offboarding email - Remind on survival terms in Contractor Agreement
- [ ] Thank you & farewell letter to personal email
- [ ] Farewell message posted (Optional)
- [ ] Update DF resource planning file
- [ ] Update LinkedIn + endorse Dwarves

### Account and access management

- [ ] Remove email account
- [ ] Remove Git account
- [ ] Remove 1password account
- [ ] Remove Basecamp account
- [ ] Remove access to other work channels
- [ ] Remove database access
- [ ] Update Fortress profile
- [ ] Update Discord Role → Alumni + Remove Discord Access from work-related channels

### Equipment and resources

- [ ] Office card / work device (laptop, phone) if applicable
- [ ] Any other company-owned equipment
- [ ] Remind member to delete source code from their machine

## Post-Departure

- [ ] Follow up on any outstanding items or handover tasks
- [ ] Conduct a brief team meeting to address any gaps left by the departure
- [ ] Update relevant documentation and contact lists

### Handover transfer

- [ ] Conduct handover transfer sessions with team members
- [ ] Document any unique scripts or tools created by the employee
- [ ] Capture information about ongoing experiments or research

Note: This aims for a smooth, positive offboarding that maintains good relations with the departing employee while protecting company interests. The checklist can be adapted to the specific role and company technology/processes.


The process when an employee offboard from the team.

Offboarding


Organizations are always looking for ways to improve efficiency and productivity. Large Language Models (LLMs) are a powerful technology that can help create smart internal tools. However, using LLMs in existing workflows can be complicated and resource-heavy. This is where managed LLMOps comes into play, providing a smoother way to develop and deploy LLM-powered tools. In this post, we'll see how platforms like Dify enhance the workflow for building internal AI tools.

## The challenge of building LLM-powered internal tools

LLMs have great potential to enhance business processes, but using them for internal tools comes with challenges:

1. **Complexity**: Using LLMs requires deep technical knowledge of AI and machine learning.
2. **Resource intensity**: Training and fine-tuning LLMs can be expensive and time-consuming.
3. **Maintenance**: Keeping LLM-based tools updated and running well needs ongoing attention.

These factors make it hard for many organizations to fully use LLM technology, especially those without dedicated AI teams.

## Managed LLMOps: A solution for efficient development

Managed LLMOps platforms solve these challenges by offering a complete environment for developing, deploying, and managing LLM-powered applications. These platforms simplify the complexity of LLMs, allowing developers and business users to focus on creating valuable tools instead of dealing with AI infrastructure.

## Dify: An example of managed LLMOps in action

Dify is a great example of a managed LLMOps platform that makes creating LLM-powered internal tools easier. Here are some key features:

1. **User-friendly interface**: Dify has an easy-to-use interface that lets both technical and non-technical users create AI applications.
2. **Pre-built templates**: Users can start quickly with templates for common use cases.
3. **Customization options**: Dify allows for deep customization when needed.
4. **Integrated workflow management**: The platform includes tools for managing the entire lifecycle of AI applications.

To make the deployment process even smoother and manage resources better, we use [elest.io](http://elest.io/) to deploy Dify. [Elest.io](http://elest.io/) is a fully managed DevOps platform, similar to DigitalOcean's marketplace but with more open-source applications. This approach offers several benefits:

- **Simplified setup**: [Elest.io](http://elest.io/) automates much of the deployment process, reducing the time and expertise needed to get Dify up and running.
- **Cost control**: By using [elest.io](http://elest.io/)'s infrastructure, we can easily manage and optimize costs across different cloud providers.
- **Flexibility**: [Elest.io](http://elest.io/) supports various cloud providers, allowing us to choose the best and most cost-effective option for our needs.
- **Scalability**: As our LLM tool usage grows, [elest.io](http://elest.io/) makes it easier to scale our Dify deployment to meet increasing demands.

This combination of Dify's powerful LLMOps capabilities and [elest.io](http://elest.io/)'s streamlined deployment process creates an efficient, cost-effective solution for organizations looking to use LLMs in their internal tools. This makes it possible for an average developer to build and deploy an internal tool in minutes.

## Case studies: Internal tools built with Dify

To show the advantage of managed LLMOps, let's look at some example tools built using Dify:

### 1. SQL sorcerer

This tool turns everyday language into SQL queries, allowing non-technical team members to extract insights from databases without learning complex query languages. We use it to make queries to our DuckDB database, integrating it with our memo website and knowledge base.

![assets/building-llm-powered-tools-with-dify-sql-sorcerer.webp](assets/building-llm-powered-tools-with-dify-sql-sorcerer.webp)

![assets/building-llm-powered-tools-with-dify-sql-sorcerer-test-duckdb.webp](assets/building-llm-powered-tools-with-dify-sql-sorcerer-test-duckdb.webp)

### 2. OGIF memo summarizer

Specialized in extracting information from YouTube transcripts, this tool quickly generates time-stamped summaries with key points, saving hours of manual video analysis. We recently wrote an article about this tool, which you can read [here](../ai/how-we-crafted-the-ogif-summarizer-bot-to-streamline-weekly-knowledge-sharing.md).

### 3. Discord summarizer assistant

Using large language models, this workflow helps translate and summarize conversations across different languages, making global team communication easier.

![assets/building-llm-powered-tools-with-dify-discord-summarizer.webp](assets/building-llm-powered-tools-with-dify-discord-summarizer.webp)

These tools help us significantly increase our productivity. We extensively use Claude 3.5 Sonnet, and occasionally GPT-4 for more detailed instructions. Without the hard work of @innno\_ and her efforts on our social media platforms, we wouldn't be able to build these tools.

## Best practices for developing internal LLM tools

When using managed LLMOps platforms like Dify to create internal tools, consider these best practices:

1. **Start with a clear use case**: Identify specific pain points or inefficiencies in your workflows that LLMs can address.
2. **Iterate based on feedback**: Regularly collect and incorporate user feedback to improve your tools.
3. **Ensure data privacy**: When dealing with sensitive internal data, make sure your LLM applications follow your organization's security policies.
4. **Monitor performance**: Use the analytics provided by your LLMOps platform to track usage and optimize performance.

## Conclusion

Managed LLMOps platforms like Dify are making AI technology accessible to organizations of all sizes, allowing them to create powerful internal tools without needing extensive AI expertise. By simplifying the development and deployment process, these platforms are paving the way for a new era of AI-augmented productivity tools. As LLM technology continues to advance, we can expect to see even more innovative applications that transform the way we work.


Discover how managed LLMOps platforms like Dify streamline the development of AI-powered internal tools. Learn about the challenges of integrating LLMs, the benefits of managed solutions, and real-world examples of efficient AI tool creation. Perfect for businesses looking to enhance productivity with AI without extensive technical expertise.

Streamlining internal tool development with managed LLMOps: A Dify case study


### What’s OGIF?

OGIF stands for "Oh God It’s Friday." It’s our weekly Friday tradition where members share 10-minute talks. The team hops on Discord to share and discuss diverse topics like software development, engineering patterns, industry trends, finance, entrepreneurship, blockchain, AI, and a mix of other cool stuff. It’s a quick, engaging way to learn something new.

We value the importance of sharing our work with other people at Dwarves. And it's a chance for people who don't work directly on development to feel included in the process.

### Meet the OGIF memo summarizer

Working in collaboration with my colleague @innno\_, we crafted a chatbot using Dify. This bot transcribes YouTube videos and extracts key points from our OGIF sessions. The result? A major boost in our ability to review and reference the knowledge shared during these meetings.

![](assets/how-we-crafted-the-ogif-summarizer-bot-to-streamline-weekly-knowledge-sharing_crafting-ogif-summarize-bot-7.webp)

### How it works?

**YouTube Transcription**: We integrated a YouTube transcription workflow as a function-calling tool for our chatbot.

**Intelligent Summarization**: The chatbot generates structured summaries from the transcribed content using a well-designed prompt.

**Three-Tier Summary Structure**:

1. **Short summary**: 3-5 key timestamps with brief descriptions of the most important topics.

![](assets/how-we-crafted-the-ogif-summarizer-bot-to-streamline-weekly-knowledge-sharing_crafting-ogif-summarize-bot-1.webp)

2. **Detailed summary**: Comprehensive timestamps, each with 2-3 bullet points providing in-depth information.

![](assets/how-we-crafted-the-ogif-summarizer-bot-to-streamline-weekly-knowledge-sharing_crafting-ogif-summarize-bot-2.webp)

3. **Languages:** The summary is available in both English and Vietnamese.

![](assets/how-we-crafted-the-ogif-summarizer-bot-to-streamline-weekly-knowledge-sharing_crafting-ogif-summarize-bot-3.webp)

### The prompt

The core of our summarizer is the prompt we’ve meticulously designed. Here’s what it does:

- Generates structured summaries with accurate timestamps.
  ![](assets/how-we-crafted-the-ogif-summarizer-bot-to-streamline-weekly-knowledge-sharing_crafting-ogif-summarize-bot-4.webp)
- Creates clickable links to specific points in the video.
- Offers both a quick overview and detailed insights.

![](assets/how-we-crafted-the-ogif-summarizer-bot-to-streamline-weekly-knowledge-sharing_crafting-ogif-summarize-bot-5.webp)

- Maintains consistent formatting for easy reading.
- Provides a comprehensive overview of the video content.

![](assets/how-we-crafted-the-ogif-summarizer-bot-to-streamline-weekly-knowledge-sharing_crafting-ogif-summarize-bot-6.webp)

### Benefits

- **Time-Saving**: Team members can quickly grasp the main points of a session without watching the entire video.
- **Easy navigation**: Clickable timestamps for swift access to specific topics of interest.
- **Knowledge retention**: The structured summary serves as a reliable reference for future use.
- **Improved accessibility**: Makes the session content more accessible to team members who couldn’t attend live.

### What’s next?

We’re always looking to enhance our OGIF Memo Summarizer. Some future ideas include:

- Integrating automatic tagging for easy topic categorization.
- Implementing a search function across multiple summaries.
- Creating a visual timeline of topics discussed over multiple sessions.

### Wrapping up

The OGIF Memo Summarizer has improved our weekly knowledge-sharing sessions. Using AI, we've made a system that saves time and enhances the value of our Friday office hours.

We recommend other teams try similar tools to streamline their knowledge-sharing. In software engineering, efficient learning and sharing information can give you a big advantage.

Happy coding and happy sharing.


Introducing the OGIF Memo Summarizer, a chatbot we developed using Dify in collaboration with @innno_. This tool transcribes YouTube videos and extracts key points from our Oh God It’s Friday (OGIF) sessions. By providing both short and detailed summaries in English and Vietnamese, it significantly enhances our ability to review and reference the diverse knowledge shared every Friday.

How we crafted the OGIF summarizer bot to streamline weekly knowledge-sharing


Gradient descent is a fundamental optimization algorithm in machine learning. It's a bit like finding your way down a mountain in the fog: you take small steps in the direction that seems to be going downhill the fastest.

In machine learning, the "mountain" is a mathematical function, and the "downhill direction" helps us find the best values for our model's parameters.

### Imagine you're sliding down a hill to find the lowest point

**The Hill**

Imagine you’re standing on a hill. The hill has many ups and downs, and your goal is to find the lowest point in the hill, where there’s a treasure hidden.

**Your Steps**

1. **Starting point**: You start somewhere on the hill. You don't know if it's the lowest point, but you’re going to find out.

2. **Looking around**: You look around to see which direction the ground slopes downward. This tells you which way to go to get closer to the lowest point.

3. **Taking a step**: You take a small step down the hill in that direction.

4. **Repeat**: After taking a step, you look around again, see which way is down, and take another small step. You keep doing this until you reach the lowest point where you can’t go down any further.

### In machine learning

**1. The Hill**: Represents the error or how wrong the computer’s guesses are when trying to learn something (like recognizing cats and dogs).

**2. Lowest point**: Represents the best possible way the computer can learn from the data, minimizing errors.

**3. Steps**: Each small step you take is like the computer adjusting its guesses a little bit each time to improve its learning.

**4. Looking around:** The computer checks how it’s doing and decides which way to adjust its guesses to make fewer mistakes.

**5. Repeat:** The computer keeps adjusting its guesses little by little until it finds the best way to learn from the data, which is like you reaching the lowest point on the hill.

![](assets/explaining-gradient-descent-with-a-simple-analogy.png)

### Gradient descent in simple terms

- **You:** The computer trying to learn.
- **Hill:** The error in guesses.
- **Lowest point:** Best learning with the least errors.
- **Steps:** Small adjustments to improve guesses.
- **Looking around:** Checking which way reduces errors the most.

Just like you keep stepping down the hill to find the treasure, the computer keeps adjusting its guesses to learn better and make the fewest mistakes.

### Reference

<https://medium.com/onfido-tech/machine-learning-101-be2e0a86c96a>


Gradient descent is a fundamental optimization algorithm in machine learning. It's a way for models to learn from data and improve their accuracy by gradually adjusting their internal settings. Think of it like carefully descending a hill to find the lowest point, each small step you take brings you closer to the best possible solution.

Explaining gradient descent in machine learning with a simple analogy


### Memo knowledge base meeting

Memo is our team's wiki on how we work, learn, operate the team at Dwarves. It's a one-stop shop for all things Dwarves, written by us for fellow craftsmen.

Here are the simple steps we follow each week to keep the Memo pipeline organized and our team informed.

### Sort out memo content

- Check all memos to-do lists in Basecamp and ensure the content pipeline is up to date.

![](assets/memo-knowledge-base-meeting-1.webp)

- Prepare a quick update on any changes or new info.
- Share this update in our Friday meeting.
- Make sure [memo.d.foundation](http://memo.d.foundation) > `Home` shows the latest content.

![](assets/memo-knowledge-base-meeting-2.webp)

### Basecamp memo to-do list

- Assign each cluster to the relevant team member, and make sure everyone knows their responsibilities.

![](assets/memo-knowledge-base-meeting-3.webp)

- If content needs to be done soon, move it to the `Soon`. This section includes articles that are prioritized for upcoming publication.
- Keep the to-do list in `Soon` less than 10 items.
- Focus on the most important tasks first and meet the deadline.

![](assets/memo-knowledge-base-meeting-4.webp)

### Map of content

- Develop and sort out your content map to track existing content, what needs updating, and what new content is planned. e.g: [df-topic](https://docs.google.com/spreadsheets/d/1HzCwXFrWkaCQoYXaZsHnb-Qge6kJEPoSDLVRULJKREc/edit#gid=0).
- Check out this guide to create [map of content](make-a-moc.md).

By sticking to the checklist each week, we can ensure our memo is in the loop, and our projects stay on track.


Here are the simple steps we follow each week to keep the Memo content pipeline organized and our team informed.

Memo meeting


### Choosing the right directory for the right topic

The first thing is to determine the field that you’re writing in. Whether you're interested in writing about blockchain, communication, design, engineering, market, security, or writing there's a directory for you in `playground`.

![](assets/memo-publication-workflow-choose-topic.webp)

If you’re unsure where your content fits, just message our supporters on Discord for guidance.

### Writing your content

To learn how to write, submit, and publish your memo, see [this guide](publish-on-memo.md). Before you start, ensure each article includes these **mandatory fields**: title, description, author, date, and tags.

![](assets/memo-publication-workflow-metadata.webp)

- Name your files using kebab case, e.g: `how-to-write-a-memo.md`
- Verify all links in your article by running the repository locally.
- Upload any images to the `assets` folder and reference them accordingly.
- For image and screenshot guidelines in your article, refer to [this guide](../guides/take-better-screenshots-on-mac.md).

![](assets/memo-publication-workflow-images-format.webp)

![](assets/memo-publication-workflow-format.webp)

### Review process

After writing your article, let a reviewer know if it's a draft or the final version.

- For content: Our experts will review and improve your work. For example, @tom handles engineering, and @nikki focuses on communications.
- For format and design: @anna oversees the visual and structural aspects. Once you're done, take a screenshot, upload it to our server, and ping @anna for her feedback.

### Feedback

Gather all of the feedback, and work on them. For detailed instructions, read the article [Life cycle of a publication](publication-life-cycle.md).


This guide will help you step-by-step create content and publish on memo.

Memo publication workflow


> **Recap:** Our long-awaited visit to SP Group revealed that digital transformation in large enterprises faces more cultural than technical challenges. We discovered that successful partnerships require treating external engineers as part of one team, and that effective engineers need to understand industry-specific problems beyond just coding solutions.

We've always wanted to visit [SP Group](http://spgroup.com.sg/), one of our partners, but the pandemic made it impossible until now. This year, the opportunity finally came when we decided to attend Echelon X in Singapore.

Meeting the SPG team in person was insightful and rewarding. We learned more about the challenges of digital transformation for enterprises, remembered why SPG chose to work with us, and saw how we could promote a growth mindset for our engineers.

Plus, our friends at SPG make amazing soju beer bombs.

Everyone in our team for this visit would have their own takeaways, but a few things resonate with all of us.

- For a partnership to work, all engineers from SPG and Dwarves should act as one team. SPG treats our team as their own, which helps our collaboration. They train and lead everyone together, fostering unity.
- SPG showed us that digital transformation is more about people and their ways of working than technology. There's a gap between the tech department and the rest of the organization. True transformation starts by overcoming resistance to change and fostering a culture of learning and adaptability.
- SPG is so large that each department operates almost like an independent company. Employees are deeply rooted in their established workflows, and introducing new technology often feels like adding more work rather than simplifying it.
- Data security is a big concern at SPG. Internal teams have strict, lengthy processes to access data, and it's even harder for external partners like us. While AI and other tech are being discussed, the main issue is keeping data safe. Engineers must be aware of security and privacy, often dealing with regulatory challenges.
- While adopting trending tech like AI and AR is great, the real challenge is using them to solve business problems. What sets top engineers apart is their ability to understand industry-specific issues and use technology to address them.

All in all, visiting SPG for us reinforced our direction of how we should grow our team and how we should look at the bigger picture of the tech scene. Engineers need to expand their perspectives beyond just coding.

We are greatly grateful for how welcoming and open the SPG team was to us. We look forward to continue contributing to the changes SPG is making every day.

![Dwarves team with SP Group in Singapore](assets/sp-group-wala.webp)

---

**WALA: to walk around, learn around.**

In our line of work, we hear and talk about domain knowledge all the time. WALA aims for exactly that: we, people in tech, take a break from sitting in front of our computers, to go out, connect with new people, and get to understand other businesses.

Through stories collected from Techie WALAs, we hope our community members get the chance to learn from others' successes and failures, gain insights into what works and doesn't, and reflect on their own works and practices.

Besides, breaking away from the stereotype of "tech people are introverts" is always fun.


Our visit to SP Group offered valuable perspectives on enterprise digital transformation challenges. We learned that successful transformation depends more on people and organizational culture than technology, while strong partnerships require treating external teams as part of your own.

SP Group

#3 Digital transformation insights from the energy sector


Road to Discover Dwarves’ Voice: As you know, each individual at Dwarves represents craftsmanship and well-crafted products. I consider craftsmanship as one of the most fundamental aspects of our work, reflected in every piece of content we create.

Whatever version of these guidelines you read, rest assured it’s not the last. Keep them up to date. It takes many forms, and I always strive to improve my content.

## Writing for website

Dwarves’ website serves as the primary platform for visitors to discover who we are and what we offer. Given the diverse audience we attract, it's important to maintain a tone of expertise and authority in our writing.

- Use clear and concise language, avoid complex sentence structures and jargon.
- Active voice to make content easy to digest.
- Tell the audience what you want them to do next (CTAs).
- Speak our characteristics, whether it’s showing our expertise and skills or stating our value proposition.

![web](assets/how-i-create-content-for-multiple-platforms-at-dwarves-tone-website.webp)

![web-final.png](assets/how-i-create-content-for-multiple-platforms-at-dwarves-website-example.webp)

## Writing for social media

I use social media to build and maintain company relationships with our audience. It’s an open platform in which sharing and learning are welcomed and applauded.

Treating social media like a conversation, means I strive to be less serious, and more cheerful but at the same time, still polite and considerate of our audience.

![tone social.png](assets/how-i-create-content-for-multiple-platforms-at-dwarves-tone-social.webp)

### Facebook

- Facebook content aims to strike a balance between being informative, engaging, and algorithm-friendly.
- The goal is to grab the viewer’s attention within seconds.
- Keep posts concise and impactful, using minimal text and a short form.
- Make posts actionable: try different tactics to grab your audience's attention.

![facebook-final.png](assets/how-i-create-content-for-multiple-platforms-at-dwarves-facebook-example.webp)

### LinkedIn

- Focus on sharing industry knowledge and insights.
- LinkedIn posts typically range from 100-150 words for regular posts, while longer articles can reach up to 1,300 characters.
- Showcase professional achievements and milestones to highlight accomplishments and learning experiences.

![linkedin-final.png](assets/how-i-create-content-for-multiple-platforms-at-dwarves-linkedin-example.webp)

### X / Twitter

- Verified accounts can exceed the 280-character limit, and utilizing tweet threads is encouraged.
- Keep your tweets brief, focused, and include clear CTAs.
- Share links to relevant articles and blog posts to boost website traffic.
- Actively engage with retweets, replies, and mentions to foster audience interaction and appreciation.

![twitter-final.png](assets/how-i-create-content-for-multiple-platforms-at-dwarves-twitter-example.webp)

### Instagram

- Get right to the point right away, a few lines of a caption.
- Interactive features like stories, reels, polls, questions, and sliders to engage viewers.
- Use high-quality visuals, including images and videos, to captivate your audience.
- Embrace trends, relevant hashtags to increase visibility.

![instagram-final.png](assets/how-i-create-content-for-multiple-platforms-at-dwarves-instagram-example.webp)

## Writing for blog posts

The blog post is a format to share knowledge and offer in-depth insights into the tech & design world. A blog post from Dwarves is usually a collaborative effort - a summary of workshops we worked on together, a research report done by a sub-unit, or a case study put together by everyone on the project. Here's a brief guideline to get started:

- Choose a topic.
- Conduct thorough research to find angles and keywords.
- Outline your goals, target audience, what you’d like to cover for each section.
- Fill in your outline with research and craft an engaging introduction.
- Write your headline title, sub-header, and meta description.
- Proofread your work for flow and errors.
- Full-length articles should still be professional.

![blog](assets/how-i-create-content-for-multiple-platforms-at-dwarves-blog-example.webp)

## Writing for newsletter

Dwarves’ newsletter serves as an additional fresh voice that aims to provide more engineering-related insights and thoughts throughout our work cycles.

When crafting newsletter:

- Determine its purpose (e.g., company updates, upcoming events).
- Consider what the audience needs to ensure inclusivity and intentionality.
- Maintain a consistent and appropriate tone of voice.
- Include links and CTAs, and use visuals and font choices to draw the eye.

![](assets/how-i-create-content-for-multiple-platforms-at-dwarves-newsletter.webp)

## Writing for the Discord community

Dwarves Discord network is where we discuss new tech, industry practices, hang out with friends, and spread positive vibes. If I want to use the platform reflected in what I do, then our copy needs to do just that.

To maintain consistency with our platform's culture:

- Keep our posts original, relatable, and reliable content that resonates with the audience.
- Add a bit of joy, making memorable moments around Discord.
- Set a fun warm-up or icebreaker tone of voice, sparking conversations among members.

![discord](assets/how-i-create-content-for-multiple-platforms-at-dwarves-discord.webp)

![discord-final.png](assets/how-i-create-content-for-multiple-platforms-at-dwarves-discord-example.webp)

## Best practices

### Stay focused

Keep content centered on the main topic to maintain reader engagement and understanding. Create a pattern/structure to guide our audience through the articles by making use of titles and headings.

### Make it understandable

Write in a casual tone, using conversational language that is easy to grasp. Add humor when appropriate but avoid overdoing it.

### References

Include external links to back my points up and enhance credibility.

### Use different formats

Break up the content using headings, bullet points, images, videos, and other formats to highlight key points and improve readability.

### Keep it short, smart, and quirky

Craft the posts across various platforms to be short, informative, and infused with a touch of personality. Use simple language for quick reading and a bigger impact.

### Mind your hashtags

Research the nature of each social media platform to choose relevant hashtags. Avoid overloading your posts with hashtags if they aren't necessary.

### Trending news

Be aware of trending news and topics in design-related industries. It could be a great
opportunity to put in a word of celebrating achievements or expressing our point of view on the matter.

### Final thoughts

If you're newish to posting - just post. Don't run around chasing algorithms or trends. It'll exhaust you in no time.

## Reference

Adapted from ["Write content for multimedia guidelines"](write-content-for-multimedia-guidelines.md)


To help all our Dwarves team members, create original, helpful, and consistent writing across various platforms, we've put together this content guideline as a reference whenever we're writing for Dwarves.

How I create content for multiple platforms


> “ It’s not that we need a unified language in all contexts; rather we just need enough context to get everyone on the same page." _Jake Albaugh, Developer Advocate, Figma_

At Dwarves, we believe in the power of communication. We understand that words have the ability to shape our brand, build connections with others, and share knowledge with the world.

To help all our Dwarves team members, create original, helpful, and consistent writing across various platforms, we've put together this content guideline as a reference whenever we're writing for Dwarves.

We won’t front. Here at Dwarves, we approach writing in the same way we create products: we write for people. In other words, we focus on the **quality** and **consistency** of the content before setting goals, defining the tone of voice, and the content production process.

## Setting writing goals

### Inform

Before we start writing anything, take a moment to ask ourselves this: "If Dwarves were a person, how would we want folks to see and think about us?" That's the secret sauce to nailing down our brand vibe, getting our message out there loud and clear, and making sure we show off our true personality.

### Connect

We're all about building and nurturing connections with folks. We want people to feel connected to Dwarves on an emotional level and have an impression on us.

So, before we start typing away, we ask: "What vibe do we want people to get when they think about Dwarves Design?"

### Educate

Knowledge sharing is at the core of what we do. We believe in growing together and sharing what we know. We strive to provide helpful information and offer opportunities for learning further (workshops, courses, learning materials..) even when those opportunities are not offered by us directly.

### Express

Express our viewpoint confidently. While it's crucial to connect emotionally with your audience, do not forget that you're the experts in your field. We encourage you to showcase your perspective, your learning, and your point of view as long as it remains objective and unbiased.

### Entertain

The best way to share tech stuff is to keep it clear, even for people who aren't techies. Whether it's hot industry news or some mind-bending tech concept, if we can explain it in a way that makes sense to anyone, then we know we’re doing it right. Try to make things easier for your audience. Learning should be fun and interesting, not like pulling teeth!

### Inspire

We've discovered that inspiring people to grow and thrive is most effective when we use language that uplifts and inspires. It's about fostering positivity and encouragement, creating a sense that we're all part of something bigger and better, moving forward together.

Writing is not just acknowledging the achievements of our audience, but also celebrating the successes of our clients and the remarkable advancements occurring in the tech and satellite industries.

### Learn

We're on a journey of learning alongside our audience. Every step helps us refine ourselves, and receive lessons learned in return. It's these insights that enable us to enhance the benefits we offer and deliver more value to our audience. Don't hesitate to ask questions along the way; they're key to our growth.

## Writing content instructions

### Active voice matters

**Active voice:** Dwarves built and delivered a dozen top-notch software products for tech-focused companies.

**Passive voice:** A dozen top-notch software products were built and delivered by Dwarves for tech-focused companies.

We often lean towards using active voice because it's straightforward, concise, and grabs attention more effectively. Passive voice, on the other hand, has the action done to the subject, lacking the sense of being in charge. If the subject of the sentence is doing the action, then voila, it's active voice.

Or you can use these questions tests, it's usually good to go and mostly it'll be in active voice.

- Did you write in a clear and straight-to-the-point manner?
- Did you explain things in the simplest way possible without losing any meaning?

### Add your point of view

Write as if it is a conversation. Use the second person (you) to address your audience and refer to yourself as (we).

Bring in other points of view when it’s fit. We want to celebrate and recognize other people on the team too.

### Keep it scannable

We all have different methods of reading. Some people read everything you write, while some scan through.

Break your content into small paragraphs, and form a hierarchy with levels of importance. Create and follow a content pattern to support scanning.

### Calls to action

Identifying your ideal audience before using calls to action is like turning on a spotlight in the dark. The step you customize the CTAs to match the audience’s interest at the right time, and right place can avoid a downgrade to our brand image.

Remember to double-check that your CTA writing fits with what's happening in the industry and that it's interesting and makes sense.

### Emojis are fine

With Dwarves’ brand personality, emojis could be of use as a way to familiarize people with us and add more interest to our writing. Use emojis where you see it’s fit, just don’t overuse them.

### Exclamation points & question marks

Avoid using multiple exclamation points and question marks. Although we aim to be friendly, we also want to maintain professionalism and seriousness when necessary. Instead of overusing "!!!", opt for expressive words to convey emotions.

### Technical terms

If there are technical terms in writing, define them in simple language so everyone can understand what we are writing about.

### Tags & hashtags

Use tags and hashtags accurately, according to the content. It will help increase its potential distribution and exposure to the targeted audience.

### Copyright

Never use content or images licensed as non-commercial without getting permission from the owners first. In case there’s non-commercial material, credit the owners and include words of thanks.

### Check and fix

Recheck each piece (content structure, grammar, and wording) before submitting the content for review and feedback. Then, we move to the final step of publishing and sharing the content.

If we find ourselves missing more than two points from this guideline, seek assistance from our line manager. And don't forget to credit your name at the end.

### Reflect & adapt

Allocate time for self-reflection and develop the habit of reviewing after our work is published:

- Track the work’s performance, get feedback from peers (both good and bad)
- Enhance self-awareness by identifying areas for improvement
- Go far and wide to search for new things related to your work
- Read more

## Voice & tone

### Authentic voice

The authentic voice is a consistent element - it’s how we describe our perspectives and reflect our personality.

At Dwarves, we speak as the **highly skilled partner** for our audience. It’s mean:

- We are experienced and skillful.
- We understand our audience and we think from their point of view.
- We think of ourselves as their partner, it’s a long-term relationship built upon trust, understanding, and mutual goals.
- We are passionate about sharing knowledge and growing alongside one another.

### Appropriate tone

Our tone varies to align with the circumstances - who we’re talking with (audience), what we’re talking about (topic) and where (channel) the conversation is taking place.

Most of the time, our tone is casual and sincere with a bit of subtle humor. However, it’s crucial to set the fine line between being casual and being offensive, make sure you never cross that line. No matter the circumstance, think about how people would perceive and feel about your content.

We expect you to be agile and responsive to the circumstances when writing. In some situations, humor or cheerfulness might not be appropriate. Work your way around it instead of forcing it into your content, in case it might backslash and harm the Dwarves brand name.

Here’s a simple chart to help you assess and generate the right tone in a certain situation.

![](assets/writing-content-for-multimedia-guidelines_writing-content-for-multimedia-guideline-tone.webp)

## Overall

Remember, the goal is to write content that resonates with your audience. The more they can relate to what you're saying, the more likely they are to engage with your content.


Write content for multimedia guidelines


We know there are countless Discord servers out there. Ours aims to be different. From the start, we designed it as a space _for developers_, prioritizing genuine connection and knowledge sharing over corporate speak. We operate it as a blend of company and community because we believe that's the most valuable approach.

So, what actually happens here?

- **We share knowledge:** We discuss software insights through seminars, casual channel chats, and tech talks. If it's about development, it's welcome.
- **We connect with people:** This is our virtual space to hang out with friends, alumni, and like-minded developers. No forced networking.
- **We build in the open:** We're creating a software network people genuinely want to join. Discord is central to that effort.

We recently reorganized the channels to hopefully make navigation and connection easier. Here's a breakdown:

## Where stuff happens: the channels

Channels fall into two main categories: common areas for everyone and spaces more focused on our internal consulting work.

### Community hangouts (everyone welcome)

- **off-topic:** For general, non-work conversations.
  - `⛺・random`: The place for memes, weekend stories, pet pictures, and anything else off-topic.
  - `📈・trading-cafe`: Discussions about markets, crypto, and trading.
- **research:** The hub for technical discussions.
  - `🌟・starboard`: Notable messages highlighted by the community land here.
  - `💡・til`: Share your "today I learned" moments, big or small.
  - `💻・tech`: General technology discussions, news, and questions.
  - `🎒・topics`: Focused discussions on specific technical subjects.

### Internal & ops channels (mostly for staff & mods)

- **project:** Discussions related to active client projects (primarily for our consulting team).
- **consulting:** The main area for internal team communication.
  - `🏢・lobby`: General company-wide announcements and discussions.
  - `🦄・pink-alert`: For urgent matters needing immediate attention.
- **moderation:** Keeping the community running smoothly.
  - `🗣・community`: Coordination for community initiatives.
  - `🎗️・operation`: Server management and administrative tasks.
- **misc & log:** Essential background channels.
  - `🤖・bot-commands`: Interacting with server bots.
  - `🧊・icy-log`: Automated server activity logs.

## Who's who: Discord roles

We needed a role system that reflects contribution and expertise as we grow, not just arbitrary labels. Our system combines ladder-based roles (earned through participation) and function-based roles (based on responsibilities).

Why this structure? We want to recognize engagement and skill, eventually linking roles to tangible benefits like NFTs and `$icy` staking (more details soon). It's about creating a system that rewards active participation.

![Dwarves network discord Role Structure](assets/discord-role-structure.webp)

### The core MMA roles (mastery, meaning, autonomy)

This system recognizes different types of impact:

- **@labs (mastery):** Your technical skill is recognized and valued by the community.
- **@sers (meaning):** You make meaningful contributions, through quality work or positive community involvement.
- **@chad (autonomy):** You consistently deliver high-quality work effectively and reliably.

### Keeping the lights on (moderation)

- **supporter:** Welcomes new members and helps with daily questions.
- **moderator:** Organizes events, facilitates discussions, and may host talks.
- **smod:** Oversees major community and operational functions.

### Community crew

- **guest:** The starting role for everyone.
- **newbie:** Granted after basic introductions. Welcome aboard!
- **frens:** Actively participates in public channels.
- **contributor:** Helps bring new, valuable members into the community.
- **trustee:** A recognized and trusted voice within the community.

### Consulting staff (our internal team structure)

- **apprentice:** Team members new to Dwarves.
- **baby dwarf:** Developing their focus within the team.
- **dwarf:** Actively participates in R&D and learning.
- **crafter:** Consistently delivers quality software.
- **specialist:** Possesses deep expertise in a specific domain.
- **principle:** Helps maintain and elevate the team's standards.
- **elite:** Guides the team's technical direction.

### Functional roles (what people focus on)

These roles represent key operational areas:

- **engagement:** Aligns the team around vision and values.
- **learning:** Promotes continuous skill development.
- **partnership:** Focuses on client relationships and project acquisition.
- **communication:** Ensures transparent information flow.
- **delivery:** Oversees the quality and shipment of work.

## Our helpful bots

Being developers, we've built bots to automate tasks and add useful features:

- **Mochi:** A tipping bot using `$MOCHI`. Use `!tip` to give a virtual high-five for helpful answers or contributions.
- **Tono:** Our primary server management bot, handling roles and background tasks.
- **Fortress:** An internal tool for tracking performance and issues (less community-facing).

## How do I level up? (the `$icy` system)

We use our custom token, [`$icy`](icy.md), as the server's primary internal currency – think of it as community points.

You earn `$icy` through activity and contributions. Higher engagement leads to more `$icy`, which helps you climb the role ladder.

Achieving certain roles will also eventually grant a boosting NFT, providing tangible value back to our most active members.

That covers the basics! Feel free to jump into a channel and introduce yourself.

See you [on the server!](http://discord.gg/dfoundation)

---

> Next: [Earn](earn.md)


Our Discord isn't just another company server; it's a place for both our team and the wider developer community. This guide explains how it works and where you fit in.

Discord

Dwarves network discord


I grab screenshots pretty often. Although macOS’s native screenshot tool is decent for most cases, it’s still a very basic one. Here are a few tips on how to take great-looking screenshots with a simple tool and in less time.

## Installation and setup

CleanShot X is actually an app I downloaded as part of my Setapp subscription. I use CleanShot every single day. The app offers a wide range of features, from capturing screenshots and recording your screen to annotating and quick editing.

1. Sign up subscription on Setapp
2. Download and install CleanShot X
3. Once installed, the app is going to ask if you want CleanShot to be your default screenshot tool.
4. You will find various commands under the CleanShot X Extension by clicking the CleanShot shortcut in the Control Center.

![](assets/how-to-take-better-screenshots-on-mac_menu-bar-shortcut.webp)

## Using CleanShot X

### **Added keyboard shortcuts to Quick Access Overlay**

You can spend time figuring out what workflow and keyboard shortcuts are best for you. Open settings, here’s what I found works best for my setup.

- `Command Shift 4`: capturse an area / a part of the screen
- `Command Shift 3`: captures full screen
- `Command Shift 5`: captures all-in-one
- `Command Shift 5`: captures window
- `⌘C`: Copy to clipboard
- `⌘S`: Save
- `⌘W`: Close
- `⌘U`: Upload to Cloud
- `⌘E`: Open annotation tool

CleanShot is highly customizable, you can adjust nearly every behavior and tweak settings for your needs.

### **Annotation and Editing Tools**

- **Annotate**: Annotate your screenshots with various tools. Highlight or hide specific parts of your screenshots, crop, and add necessary annotations.

![](assets/how-to-take-better-screenshots-on-mac_annotation-tool.webp)

- **Background tool in Annotate:** easily create beautiful social media posts that stand out from others. You can even change the padding, shadow, alignment, and border-radius of your screenshot. The Auto Balance option will make your screenshot look perfectly aligned by adjusting the space around the content.

- **Using Dwarves color scheme in Background Tool:** when editing your cropped screenshot in Cleanshot, you have the option to place it on a blank canvas or use Dwarves’ branding color scheme. It's also possible to easily customize the screenshot.

  1. **Customization at Pain Color:** choose a custom color using the RGB sliders then enter a Hex code **`F8F8F8`**.
  2. **Dwarves' branding scheme:** Set Dwarves' branding colors as the background wallpaper (if different from Pain Color).
  3. **Alignment:** center your screenshot on the canvas for a balanced look.
  4. **Padding:** adjust the padding to 76 for optimal spacing around your content.
  5. **Shadow:** apply a shadow effect with a strength of 28 to enhance the depth of your screenshot.
  6. **Dwarves logo:** add the Dwarves logo in the top left corner

![](assets/how-to-take-better-screenshots-on-mac_df-color-scheme.webp)

![](assets/how-to-take-better-screenshots-on-mac_rgb-df.webp)

### **Screen Capture Features**

- **Scrolling capture**: refers to taking a screenshot of a webpage while scrolling down. Select the Scrolling screenshot, start scrolling slowly, or use auto-scrolling.
  This feature is used when using VSCode to write articles/publications and will submit screenshots to the manager for feedback on both content and visual.

![](assets/how-to-take-better-screenshots-on-mac_scrolling-capture_compressed.mp4)

- **Capture Text (OCR)**: use OCR to capture text from your screen. Simply select an area that contains the text, and it will be copied to your clipboard.

- **All-In-One mode**: this mode allows you to specify the size and lock the aspect ratio for your screenshots. It also saves your last selection, making it easier to retake your last screenshot.

- **Recording features**: choose between recording a video or a GIF, whether to capture a specific window, custom dimensions, a part of the screen, or fullscreen. With our built-in video editor, you will be able to prepare a screen recording for sharing, by reducing its file size or changing the audio settings.

- **Open history**: access your screenshot history. You can remove files from the Capture History or restore recent captures if you ever need them again.

## Overall

This guide will help you quickly make great screenshots with this tool. It does exactly what we need it to do, and I think you'll love it, too. Keep practicing with these tools, they're like the cherry on top, adding that extra something to your work.


Taking screenshots of them shouldn’t be that challenging. In this article, I’ll take you through my screenshot workflow with a handful of simple tools and techniques and grab screenshots with negligible effort.

How to take better screenshots on Mac


Our [Dwarves Discord network](discord.md) is the space where we connect with friends, alumni, and other like-minded developers.

One way we encourage collaboration and skill growth is through **bounties**. These are tasks that reward community members with our token, **$ICY**, for contributions. Bounties often involve work outside a developer's primary skillset, offering a chance to learn and contribute in new ways.

### Who can participate?

Our bounty program provides opportunities for developers looking for interesting challenges and a way to connect with others.

- The program is open to anyone with the necessary skills for a specific bounty.
- Common skills needed include writing, design, research, development, and finance analysis.

### How it works

First, join our Discord server. If you haven't already, say hello in the `😀・arrival` channel.

1. **Check the bounty board:** Visit <earn.d.foundation> to see available tasks.
2. **Claim a bounty:** Select a bounty you want to work on and claim it by opening a ticket in the `⁠🎫・support-ticket` channel on Discord.
3. **Deliver the work & get paid:** Complete the bounty requirements. Once your contribution (usually a Pull Request on GitHub) is approved and merged, you'll receive your $ICY reward.

### Rewards

We allocate a monthly pool of **1700 $ICY** (roughly equivalent to $2,500 USD, though the value fluctuates) for the bounty system.

You can use your earned **$ICY** to redeem exclusive Dwarves swag or swap it for USDC.

Please note: Rewards are paid out _after_ the corresponding Pull Request (PR) is accepted and merged into the relevant Dwarves GitHub repository. We aim to create a welcoming environment for contributors, and bounties are a key part of that.

![Dwarves Foundation Community Bounty Program](assets/community-bounty-program.webp)

---

> Next: [Sharing](sharing.md)


Bounties reward community members with $ICY for contributing work that helps developers expand their skills beyond their usual focus.

Earn

Earning with sidegig


### The idea: A path to better software

> _“Everything in software architecture is a trade-off, and the why is more important than how." Neal Ford is a Director and software architect at ThoughtWorks._

At Dwarves, we believe that growth is our universal language, and we always strive to improve ourselves, individual-wise and team-wise.

At the end of 2021, starting with engineering practices, the core idea behind creating a software design group is to enable engineers to develop the skills required to become software architects. While there is no predetermined path or set of qualifications, several key abilities can help engineers gain the knowledge and experience to advance as architects. Becoming a strong software architect is more about applying skills in practice than just gaining theoretical knowledge.

### Welcoming all team members: Embracing diversity and inclusivity

Outside of work, we encourage the Dwarves to improve their knowledge and skills. Software Design Group - where people can develop themselves and as a team, where the team discusses and collects the point of view on software systems.

By thriving on diversity, Dwarves welcomes professionals from various backgrounds, skill sets, and experiences to join us, learn with us, and build with us. We embrace inclusivity promote the exchange of fresh ideas, encourage creativity, and help to foster a sense of belonging among team members.

### Developing skills and professional knowledge: Continuous growth and mastery

After every training session, there was both positive and constructive feedback from the team. The best part was knowing how they were able to advance and hone their skills.

- **Develop a broad technical perspective:** Through the ongoing training, team members were asked to understand how technologies, frameworks, and languages work together at an enterprise level. They should keep up with software trends to see how new tools could benefit their organization.
- **Gain experience with system design:** Designing complex system architectures is at the heart of a software architect's job. The team members themselves have experience in creating scalable, practical software designs and understanding the performance demands to build knowledge that translates directly to architectural work.
- **Develop a user experience mindset:** Providing a good user experience was enforced at all phases. This focus on user experience (UX) encourages team members to put themselves in the shoes of the end-users and consider the impact of their work on the overall usability, accessibility, and satisfaction of the software.
- **Teamwork mindset:** Regardless of roles and seniority, the collaboration between individuals in the team was evident, with everyone clearly understanding their responsibilities and working together effectively.

### Level up the tech quality

We build software. The primary purpose of the Software Design Group is to create high-quality software solutions. Software architects need to be hands-on, we input the discoveries and new research into practices. By creating an environment where everyone feels valued and respected, we can unlock the full potential of our engineers and drive innovation forward.

Here are some of our proofs:

**Demo**

- Explicit locking in SQL DBMS: [https://bit.ly/3qoELO5](https://bit.ly/3qoELO5)
- Overview of Hashicorp Vault: [https://bit.ly/3qoEEC9](https://bit.ly/3qoEEC9)
- Postgres implement multi-version concurrency control: [https://bit.ly/3WG9SB5](https://bit.ly/3WG9SB5)

**Dwarves Brainery**

- Some light and casual articles on our Brainery: [https://brain.d.foundation/](https://brain.d.foundation/)

**Radio Talk**

- Software Modeling & Architecture: [https://youtu.be/6hNXFhz0qow](https://youtu.be/6hNXFhz0qow)
- Introduction to Driven Domain Design: [https://www.youtube.com/watch?v=8ZiS-MFXN28](https://www.youtube.com/watch?v=8ZiS-MFXN28)
- Database Sharding: [https://www.youtube.com/watch?v=QiUWIyigz4U](https://www.youtube.com/watch?v=QiUWIyigz4U)
- State Machine Pattern: [https://www.youtube.com/watch?v=rtxSf1QP1wk](https://www.youtube.com/watch?v=rtxSf1QP1wk)
- Database Partition: [https://www.youtube.com/watch?v=XoRUFn3UjII](https://www.youtube.com/watch?v=XoRUFn3UjII)

**Articles**

- Design a system for a video streaming platform startup: [https://bit.ly/43yyoWR](https://bit.ly/43yyoWR)
- zk-SNARKs: [https://bit.ly/43n7jXe](https://bit.ly/43n7jXe)
- Database Designs for Multilingual Apps: [https://bit.ly/45HNvPw](https://bit.ly/45HNvPw)

From every piece of collected knowledge, the group can design robust architectures, develop scalable code, and implement efficient algorithms to build developer-focused products that strengthen the software core. The result is the delivery of software products that meet or exceed client expectations, leading to customer satisfaction, increased revenue, and a competitive edge in the market.

So far, collaborating between the software design team has led to creative solutions we may not have achieved by working separately. Always keep learning and coding.

---

**Life at Dwarves** is a series of stories about people, perspectives and lives at the Dwarves Foundation.


At the end of 2021, starting with engineering practices, the core idea behind creating a software design group is to enable engineers to develop the skills required to become software architects.