drinkitsDEV

Building small apps for Jira. Currently raising pixel trolls in Feed The Troll. Real work in, XP out. No guilt trips.

[drinkitsDEV @drinkitsdev]

First post. Will inform daily about developing Jira Cloud app.

[drinkitsDEV @drinkitsdev]

@silic2023 yeah, and the empty diff is what made it easy to trust. did it again earlier today with two more settings, same bundles. now I just wait for tonights scheduler run to tell me nothing happened

[drinkitsDEV @drinkitsdev]

Shipped the same app bundles twice in 12 hours, byte for byte.

Release one changed how the backend reads rollout settings. Release two flipped one setting to all.

Customers saw nothing. That was the point. New Jira sites now get the Team Village by default. #buildinpublic

[drinkitsDEV @drinkitsdev]

@steffdoesthings yep. each feature has its own site list: my own Jira first, then a handful of customers, then everyone. By the time this one went to "all" every existing site was already on it. The flip really only matters for sites that install tomorow.

[drinkitsDEV @drinkitsdev]

Update on the mountain deploy: two are now frozen in production, and that's the good news. Two more are ready, four are still deciding.

Three sites have no village at all, so the mountain has nothing to stand behind. Can't fix that one with a retry.

[drinkitsDEV @drinkitsdev]

Deploying a mountain to prod:

1. Read the team's Jira setup
2. Wait 12 hours
3. Read it again
4. Same? Write it once. FAIL_IF_EXISTS. Forever.

No rerolls. Not even for the dev who wrote it.

Customer Guardians are now in the 12-hour waiting room.

[drinkitsDEV @drinkitsdev]

spent the last few days teaching a mountain some basic engineering:

- rocks need gravity
- rivers need to actually connect
- 10 pixels is apparently enough for a troll to have a personality

Guardian finally feels alive.

[drinkitsDEV @drinkitsdev]

Spent today making sure a Guardian is born only once.

Two identical readings of the villag - 12 hours apart. Then one conditional write (FAIL_IF_EXISTS), and it is frozen for good.

200 concurrent writers in tests, 8 on real Forge KVS. One wins, the rest read back the winner.

[drinkitsDEV @drinkitsdev]

every Team Village in my Jira app gets a stone Guardian.

The shape comes from how your projects are set up: statuses, issue types, releases.

Face, stone and moss come from sha256(village UUID), cut into 8 traits. 5,184 looks per shape.

The hash never sees project data.

[drinkitsDEV @drinkitsdev]

entered #Codegeist with Feed The Troll, my pixel-art game inside Jira.

Working on the Village Guardian. Siege Forecast is next.

The Guardian looks calmer about the deadline than I do. :D

https://t.co/7Y0dgg6Wzl

#BuildInPublic

[drinkitsDEV @drinkitsdev]

run, run, run

[drinkitsDEV @drinkitsdev]

First version released on 2026-03-31. $4 earned so far. All clients under 10 users so using free licenses.

Problem - love to build, do not love to work on marketing.

[drinkitsDEV @drinkitsdev]

Tests passed.

Then looked at it and realized the rocks were floating 😅

Today I taught a mountain about gravity.

The goal: believable cliff first. Guardian second. WOW when the eyes open.

[drinkitsDEV @drinkitsdev]

test, test, test. Have lot to test today.

[drinkitsDEV @drinkitsdev]

started with “let’s make Feed The Troll’s Team Village prettier.”

Ended up benchmarking PixiJS vs Canvas 2D, fixing fractional-DPR pixels, reworking lighting/parallax, and hiding a Guardian in the mountain 😅

PixiJS is🔥, but Canvas 2D won.The goal isn’t fancy tech. It’s WOW.

[drinkitsDEV @drinkitsdev]

got an idea about custom village-guardian based on same data we use for feeding trolls. Custom guardian for diffent Jira instances. Still working on concept.

[drinkitsDEV @drinkitsdev]

New collab article about personallities logging time in Jira https://t.co/gQM5mSv0yr

[drinkitsDEV @drinkitsdev]

added a 'Write a review' link to Feed The Troll's admin page.

I'm asking the internet to review a troll. This is probably fine.

[drinkitsDEV @drinkitsdev]

Fixed problem with loading village while SQL DB still not created.

[drinkitsDEV @drinkitsdev]

You can now change lineage after cooldown period

[drinkitsDEV @drinkitsdev]

Version 2.20.0 release: