# What's everybody working on (November edition)

**URL:** <https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173>\
**Category:** Showcase\
**Tags:** community, wewo\
**Created:** [November 1, 2026, 10:36am UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173 "2026-11-01T10:36:39Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukeflo](https://ziggit.dev/user_avatar/ziggit.dev/lukeflo/32/7514_2.png) [@lukeflo](https://ziggit.dev/u/lukeflo)\
**Post date:** [November 1, 2026, 10:36am UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/1 "2026-11-01T10:36:39Z")

</div>

November thread to keep the tradition alive 🙂

> [@What's everybody working on? (October edition)](https://ziggit.dev/t/whats-everybody-working-on-october-edition/17770/1):
>
> I like that this becomes something like a monthly tradition here. So I’ll have to do another one of those this month.
> 
> To cite Andrew Kelley:
> 
> > [@](#):
> >
> > Demo thread! Share screenshots, videos, sound clips, stories, asciinema recordings, link a blog post you made, or just explain what hobby project you’ve been working on lately. Ambitious, well-scoped, or anywhere in between, your efforts are welcome in this thread. If you posted in a previous thread, give us an update! Are you tackling a new challenge? Still wrestling with the same problem space? Have you moved on to something completely new? Previous threads: [What's everybody working on?](https://ziggit.dev/t/whats-everybody-working-on/14958) [What's everybody working on? (July Edition)](https://ziggit.dev/t/whats-everybody-working-on-july-edition/16456)
> 
> Previous threads:
> 
> - [What's everybody working on?](https://ziggit.dev/t/whats-everybody-working-on/14958)
> - [What's everybody working on? (July Edition)](https://ziggit.dev/t/whats-everybody-working-on-july-edition/16456)
> - [What’s everybody working on? (August Edition)](https://ziggit.dev/t/what-s-everybody-working-on-august-edition/17050)
> - [What's everybody working on? (September Edition)](https://ziggit.dev/t/whats-everybody-working-on-september-edition/17434)

- [What’s everybody working on (October edition)](https://ziggit.dev/t/whats-everybody-working-on-october-edition/17770)

---

<div class="post-metadata">

**Author:** ![jangorecki](https://ziggit.dev/letter_avatar_proxy/v4/letter/j/7bcc69/32.png) [@jangorecki](https://ziggit.dev/u/jangorecki)\
**Post date:** [November 1, 2026, 10:57am UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/2 "2026-11-01T10:57:15Z")

</div>

zolap - zig-based in-memory OLAP engine

---

<div class="post-metadata">

**Author:** ![lukeflo](https://ziggit.dev/user_avatar/ziggit.dev/lukeflo/32/7514_2.png) [@lukeflo](https://ziggit.dev/u/lukeflo)\
**Post date:** [November 1, 2026, 11:16am UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/3 "2026-11-01T11:16:10Z")

</div>

As [showcased](https://ziggit.dev/t/dabeob-a-simple-tui-lib-for-zig/18166) I got my personal tui lib to a usable state. And now I adapt my tui file manager to use this tui lib instead of the external dep I used beforehand.

---

<div class="post-metadata">

**Author:** ![IbrahimOuhamou](https://ziggit.dev/user_avatar/ziggit.dev/ibrahimouhamou/32/2344_2.png) [@IbrahimOuhamou](https://ziggit.dev/u/IbrahimOuhamou)\
**Post date:** [November 1, 2026, 11:28am UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/4 "2026-11-01T11:28:12Z")

</div>

I’m trying to find a way to use Zig in a company.

also, I like how these posts are becoming a linked list

---

<div class="post-metadata">

**Author:** ![devanbenz](https://ziggit.dev/user_avatar/ziggit.dev/devanbenz/32/10433_2.png) [@devanbenz](https://ziggit.dev/u/devanbenz)\
**Post date:** [November 1, 2026, 12:38pm UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/5 "2026-11-01T12:38:03Z")

</div>

In order to learn Zig I’ve been building out a rendition of Lehman and Yao’s B-Tree: [https://db.cs.cmu.edu/papers/1981/lehman-tods1981.pdf](https://db.cs.cmu.edu/papers/1981/lehman-tods1981.pdf)

---

<div class="post-metadata">

**Author:** ![yinameah](https://ziggit.dev/user_avatar/ziggit.dev/yinameah/32/8453_2.png) [@yinameah](https://ziggit.dev/u/yinameah)\
**Post date:** [November 1, 2026, 12:53pm UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/6 "2026-11-01T12:53:50Z")

</div>

Step 1 : find a company  
Step 2 : find a problem nobody seems willing to tackle  
Step 3 : tackle said problem with zig, but don’t tell anybody just yet.

Congratulations, you are now using zig in a company.

Step 4 : unweil the thing. It’s so cleverly designed and brutally efficient everybody instantly recognise how superior zig is and you get huge promotion and employee of the year badge.

Steps 1-3 went well so far for me. Still working on step 4…

---

<div class="post-metadata">

**Author:** ![IbrahimOuhamou](https://ziggit.dev/user_avatar/ziggit.dev/ibrahimouhamou/32/2344_2.png) [@IbrahimOuhamou](https://ziggit.dev/u/IbrahimOuhamou)\
**Post date:** [November 1, 2026, 1:28pm UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/7 "2026-11-01T13:28:26Z")

</div>

I’m just an intern. I can choose whatever stack I want, I would love to use dusty but the only problem is maintainability! there is no one who knows Zig in the company (the only webdevs are 2 interns)

I would like to tell the (idk what he’s called in English) but he’s too busy and I hate bothering people

> [@yinameah](#):
>
> Steps 1-3 went well so far for me. Still working on step 4…

hmmmm, it would be better to have some people with interest in Zig so the reveal leads to “yeah, I think it’s time to finally learn Zig”

for me, the goal is to just use Zig in a day job, debugging other languages is annoying (they throw their bugs at me, they do things behind my back, a crocodile looks like a duck…). so If I could just be the one maintaining the app I wouldn’t really care about what others use, maybe having someone to maintain it after me so no one tells me to rewrite it in python

---

<div class="post-metadata">

**Author:** ![pasta](https://ziggit.dev/user_avatar/ziggit.dev/pasta/32/6273_2.png) [@pasta](https://ziggit.dev/u/pasta)\
**Post date:** [November 1, 2026, 1:47pm UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/8 "2026-11-01T13:47:21Z")

</div>

Should we make them doubly linked? Will help with traversal and give constant time removal semantics if we find out we didn’t like August for some reason

---

<div class="post-metadata">

**Author:** ![IbrahimOuhamou](https://ziggit.dev/user_avatar/ziggit.dev/ibrahimouhamou/32/2344_2.png) [@IbrahimOuhamou](https://ziggit.dev/u/IbrahimOuhamou)\
**Post date:** [November 1, 2026, 1:59pm UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/9 "2026-11-01T13:59:13Z")

</div>

ah, Engineers doing what engineers do (optimization). anyways, the [26 talks post](https://ziggit.dev/t/software-you-can-love-26-talks/17942) is my preferred way; a big fat buffer. with every post linking to the same original which contains links to all the monthly posts

---

<div class="post-metadata">

**Author:** ![ericlang](https://ziggit.dev/user_avatar/ziggit.dev/ericlang/32/8515_2.png) [@ericlang](https://ziggit.dev/u/ericlang)\
**Post date:** [November 1, 2026, 2:54pm UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/10 "2026-11-01T14:54:26Z")

</div>

Still workiing on my strictly no a.i. random level game.

 ![image](https://ziggit.dev/uploads/default/original/2X/f/f8720b84a76392177fc135a06ae76aabd0f20156.png)

---

<div class="post-metadata">

**Author:** ![Sze](https://ziggit.dev/user_avatar/ziggit.dev/sze/32/496_2.png) [@Sze](https://ziggit.dev/u/Sze)\
**Post date:** [November 1, 2026, 3:46pm UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/11 "2026-11-01T15:46:19Z")

</div>

Discourse automatically turns it into a doubly linked list, because if you link to a post it adds a back-link from the linked post, also we have the #wewo tag for these topics, which seems more practical to me than trashing my brain cache with following a bunch of pointers 😉 .

---

<div class="post-metadata">

**Author:** ![WeeBull](https://ziggit.dev/user_avatar/ziggit.dev/weebull/32/6828_2.png) [@WeeBull](https://ziggit.dev/u/WeeBull)\
**Post date:** [November 1, 2026, 11:11pm UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/12 "2026-11-01T23:11:43Z")

</div>

Oh No!

🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯

---

<div class="post-metadata">

**Author:** ![oupson](https://ziggit.dev/user_avatar/ziggit.dev/oupson/32/10510_2.png) [@oupson](https://ziggit.dev/u/oupson)\
**Post date:** [November 2, 2026, 11:52am UTC](https://ziggit.dev/t/whats-everybody-working-on-november-edition/18173/13 "2026-11-02T11:52:02Z")

</div>

I’m working on my custom discord wayland overlay (with vulkan). It is already usable, but I still have lot of things to implement or polish.
