banner
LightNews
kolaente.de
kolaente
@kolaente.de
83 followers 94 following 120 posts
Developer, Go + Vue + Laravel + Docker, building @vikunja.io
Posts Media Videos Starter Packs
kolaente.de
kolaente @kolaente.de · 11h
Put that in a while true loop and it should keep running forever.

Will the output be useful? Maybe
kolaente.de
kolaente @kolaente.de · 11h
cat PROMPT.md | claude --dangerously-skip-permissions
1 1
kolaente.de
kolaente @kolaente.de · 3d
github.com/go-vikunja/vikunja/pull/1643/files

3 line change, 380 lines of new tests (this was previously under-tested).

With Code Agents, there's no excuse to not write tests.
Fix/filter persistence table by kolaente · Pull Request #1643 · go-vikunja/vikunja
Resolves #1478
github.com
kolaente.de
kolaente @kolaente.de · 4d
Me searching for full text search databases right now

It's all BM25 under the hood! (Most of the time)
kolaente.de
kolaente @kolaente.de · 13d
Basically "git rebase -i <first commit sha>", then it opens a text editor where you can pick and choose how you want to edit the history.

To find the first commit, "git log --reverse | head -n5" will show it.
2
kolaente.de
kolaente @kolaente.de · 13d
I would recommend an interactive rebase, then pick and squash the commits how you want them (or delete entierly).

Some details about this here: git-scm.com/book/en/v2/G...

Otherwise, happy to help!
Git - Rewriting History
git-scm.com
1 2
Reposted by kolaente
gergely.pragmaticengineer.com
Gergely Orosz @gergely.pragmaticengineer.com · 14d
AI agents being able to run unit tests is SUCH a massive unlock.

If you're a dev who has utilized unit tests heavily: using a tool like Claude Code makes so much sense.

And if you don't yet use tests: with AI agents, don't see how you would not do it sooner or later...
8 5 61
kolaente.de
kolaente @kolaente.de · 14d
In other words, I love git squash.
1 1 1
kolaente.de
kolaente @kolaente.de · 14d
A story in six parts:
A screenshot of a Git commit history showing six sequential commits by user "kolaente" on a dark interface. The commits tell a story of debugging frustration: 1. "simplify, cleanup" (1 hour ago) 2. "fix test" (1 hour ago) - marked with red X 3. "fix test" (56 minutes ago) - marked with red X 4. "actually fix test now" (42 minutes ago) - marked with red X 5. "make this work" (31 minutes ago) - marked with red X 6. "finally" (21 minutes ago) - marked with green checkmark The progression of increasingly desperate commit messages followed by multiple failed builds (red X icons) before finally succeeding (green checkmark) captures the relatable experience of debugging code.
1
kolaente.de
kolaente @kolaente.de · 14d
cc @simonwillison.net
kolaente.de
kolaente @kolaente.de · 16d
Check out golangci-lint, it does a bunch of this (and more) at once with an easy config file
3
kolaente.de
kolaente @kolaente.de · Sep 11
I've recently blogged about my AI workflow here: blog.kolaente.de/2025/09/how-...

My workflow today was a little different, will post a follow-up.
How I use AI coding tools | kolaente's Blog
blog.kolaente.de
kolaente.de
kolaente @kolaente.de · Sep 11
This was a pretty wild experience! I'll continue and refine this but it seems kinda promising. These things are still dumb as hell, but they're getting to a point where they're really usable.
1
kolaente.de
kolaente @kolaente.de · Sep 11
Most of the time, I had Codex or Claude write an implementation plan, iterate on it, then have one of the two implement the plan. In some cases, I would throw away the result and start over, but many times worked after some refinement.
1
kolaente.de
kolaente @kolaente.de · Sep 11
To get today's RC 2 out of the door, I did 13 PRs - only today. Some were trivial fixes, some were more complicated.

For all of them, coding agents did most of the legwork. I mainly supervised and guided.
1
Reposted by kolaente
vikunja.io
Vikunja @vikunja.io · Sep 11
Because of the great success of 1.0.0-rc1, we proudly present rc2! 🚀

Over 145 commits have been made, most of them bug fixes but also many dependency updates.

🐛 Find all the bugs! Report them so that we can go on and fix them.

github.com/go-vikunja/v...
Release v1.0.0-rc2 · go-vikunja/vikunja
This is the third release candidate of v1.0.0. Over 145 commits have been made, most of them bug fixes but also many dependency updates. Please test this release thoroughly and report any issues yo...
github.com
1 3
kolaente.de
kolaente @kolaente.de · Sep 11
I love when it's buzzing with activity like this.
This is a GitHub repository insights dashboard displaying activity for the week of September 4, 2025 through September 11, 2025, with a period selector showing "1 week" in the top right. The overview shows two horizontal progress bars indicating 40 active pull requests represented by a predominantly purple bar with a small green section, and 27 active issues shown with a predominantly red bar and small green section. Below this are four key statistics: 38 merged pull requests, 2 open pull requests, 18 closed issues, and 9 new issues. The summary section states that excluding merges, 3 authors have pushed 45 commits to main and 54 commits to all branches, and that on main, 46 files have changed with 1,581 additions and 1,208 deletions. On the right side is a "Top Committers" section featuring a bar chart with the y-axis labeled "Commits" scaling up to 25, showing three bars of decreasing height representing approximately 25, 23, and 3 commits respectively, with three user profile avatars displayed below the corresponding bars.
1
Reposted by kolaente
vikunja.io
Vikunja @vikunja.io · Sep 11
Vikunja users have been asking for real-time updates, and we're ready to build it!

We're seeking sponsors to help bring this to life. If you or your organization use Vikunja and would like to support this improvement, we'd love to talk to you, in the issue or via email.

github.com/go-vikunja/v...
go-vikunja/vikunja
The to-do app to organize your life. Contribute to go-vikunja/vikunja development by creating an account on GitHub.
https://github.com/go-vikunja/vikunja/issues/1460"
3 3
kolaente.de
kolaente @kolaente.de · Sep 10
oh no how should I work now
1
kolaente.de
kolaente @kolaente.de · Sep 5
I remembered that I have a blog and published something:

blog.kolaente.de/2025/09/how-...
How I use AI coding tools | kolaente's Blog
blog.kolaente.de
1
kolaente.de
kolaente @kolaente.de · Aug 17
Well we still have to do the 1.0 release 😅

With the last "real" feature release 13 months ago, this feels a little arbitrary now. And of course there are still plenty of things to improve. It never ends I guess I just had to move toward 1.0 at some point.
Reposted by kolaente
vikunja.io
Vikunja @vikunja.io · Aug 17
The first (second) release candidate of v1.0.0 is now published! Please test thoroughly and report any issues you might find.

(rc0 did not get published due to CI issues)

github.com/go-vikunja/v...
github.com
1 6 6
kolaente.de
kolaente @kolaente.de · Jul 25
Wild: tell claude code it should create multiple agents and it goes off and creates multiple mini-claudes to research in parallel
kolaente.de
kolaente @kolaente.de · Jul 22
AI programming agents might make you more productive, but they won't make the time spent battling IDEs and dev environment setups (guess who just spent an hour to set it all up?)
kolaente.de
kolaente @kolaente.de · Jun 26
And it didn't even fix my problem! Before: 1092 typecheck issues, now 1982 typecheck issues...