CodeMonument

i need this in my life

@mikker Bought Tuna Pro 🥳 Tested it for the grace period and found it valuable to my workflow, use it daily now and improve the edges which don't translate yet from my workflows with raycast ^^

@mitsuhiko hahaha, nice! :D

We got caveman at home.

Congrats!

@cnakazawa @etrepum Yes, also noticed that for me! No new experience, only getting the code in the shape I knew before. Trying to offset this by using the extra time I have due to LLm coding for doing more little experiments 🙌😍

@etrepum Me constantly telling it "make the API the way I want" does not make me feel accomplished. Good API design is based on experience, and I'm not making new experiences.

Now that coding agents solve engineering problems better and faster than me, I no longer get as much excitement out of problem solving. While I used LLMs six months ago for fate, they were still at a stage where I had to do most of the thinking and deep coding myself. It's possible that it will be forever the last open source project I built from scratch that feels like a big accomplishment. For example, I'm super proud of the actions API: fate.technology/guide/actions At the same time, I'm super excited to make fate work super well for void.cloud soon!

@mattpocockuk Did not have time to Rest it yet, when u do I'll report!

Anyone who's tried my new /domain-model skill - any feedback? Hearing positive noises but would love more detail. It replaces /grill-me in my stack, adding a thin layer of docs and ADRs during ideation.

@LeadcodeDev @unTananaHere @thdxr Yes, definitely better standard lib and language! But switch to strong typing was hard and even i, as someone who pitched dart to his colleagues at the time, have to admit that typescript with its better js compat simply won the market :D

@CodeMonument @unTananaHere @thdxr And yet Dart is a thousand times more successful than JavaScript (same for Typescript) if we talk about Standard api, reliability or stability of the language

we had to declare bankruptcy and start over painful decision/process and it set us back a bunch but now we have the foundations to try and do something good

The OpenClaw story on the @TEDTalks stage. @steipete knocked it out of the park. Standing ovation. ted.com/talks/peter_st…

Released SuperCmd 1.0.16 🎉 You'll love this update ❤️‍🔥 cause we now have the world's best calculator in SuperCmd! You can go crazy with the calculations👀 "7 football fields in km + 20 yards" "1 tbsp of honey in gram" "10am pst to ist + 5 hours" Other keys updates ✨ 📁 Now you can pin any file or folder in launcher that you frequently access 🔗 Deeplink for all SuperCmd commands and installed extensions ⌨️ Configured shortcuts will show-up after the command in search 🌗 Toggle system theme & shutdown command Github: github.com/SuperCmdLabs/S… Download: supercmd.sh

tokenjuice beta (v0.4) is out! 🧃 🥧 Native pi and Claude extensions 🚪 Escape hatch for harnesses when failing 🐧 Linux binaries 😃 Unicode emoji and CJK support ⚙️ Improved rules for npm, yarn, bun and pnpm Grab here: github.com/vincentkoc/tok…

runline is also an SDK, a CLI and it's open source! so you could plug it into any agent or use it as a library, or tell me why it's bad on gh, do whatever, go crazy! github.com/Michaelliv/run…

@theo I have to admit, I tried it at the start, it was too rough since I cloudn't use screenshots properly and went back to pi. Maybe I'll try again in some days to check the progress, t3 Chat is seriously the best chat interface, so I'll expect much from the interface of t3 code

T3 Code just broke 50k users 😳

announcing artifacts - a versioned file system that speaks git certainly the coolest thing i've ever built and i got to build it with some truly great people fearless leader: @elithrar zig/git nerd: @mattzcarey storage goat: @thomas_ankcorn blog.cloudflare.com/artifacts-git-…

Ohhh, I have to try after moving ! ✨

Because flutter has some serious flaws. I looked into it for a long time, but: - on mobile iOS it's too buggy and has slight to severe differences to native behavior - on web it's too heavy due to webassembly, coding tooling is awkward - you have to use dart, which simply lost to typescript Either build full web and adapt it to mobile and desktop with electron or ionic/capacitor Or Build react native/ expo on iOS and android, web for the rest of Or Build everything native

@thdxr stupid question maybe, but why is nobody using flutter to build these desktop apps?

Yeeees, found a similar thing for Claude code only some time ago so I'm very excited to get this in pi! Thanks @nicopreme !

See the GitHub repo for details. There are some known issues, which I am planning to address soon. Feel free to leave feedback to show interest. github.com/KurtGokhan/teg…

@AriesTheCoder @theo I use solidjs. Ecosystem is not there completely yet, but since the foundation is so good, we probably should start to build on it long term. SolidJS 2 even fully integrates with async signals which is sooooo nice

@theo What should we be using instead boss?

Why are you still using React when you can vibe code something better in a day?

I need to check out this supervisord thing. Thought about making my containers like the linuxserver io images, they use something different for this process supervisor inside the container, I forgot the name

unpopular dockerfile takes (that actually work) 1 - stop using alpine — yes, it's tiny. but musl libc ≠ glibc. your python/node app will rebuild native deps from scratch or just... silently be slower. use -slim (debian-slim) instead. same size win, zero grief. 2 - layer order is your cache strategy. COPY your lockfile first, run install, then copy source. invalidating the install layer on every code change is a skill issue ngl 3 - multi-stage builds aren't just "best practice" — they're the actual reason your prod image doesn't ship gcc and 400mb of build tools. builder stage = bloat zone. final stage = lean mean container. 4 - COPY . . is fine actually — if your .dockerignore is correct. most pain here is from forgetting to ignore node_modules/, .git, *.log. fix the ignore file, not the COPY. 5 - one process per container is a vibe, not a law. if your app needs nginx + app server and you're not at k8s scale — just use supervisord. the "one process" dogma costs more complexity than it saves sometimes. 6 - pin your base image by digest, not tag. node:20 today ≠ node:20 in 6 months. prod broke because of a tag? that's a you problem tbh. 7 - BuildKit cache mounts (--mount=type=cache) will change your life. pip/apt/cargo cache between builds without it ending up in the final layer. nobody talks about this enough fr there's no "best practice" in a vacuum. alpine is great for Go binaries. slim is great for Python. scratch is great for static bins. know your workload, then choose. btw if you want something to catch all this stuff automatically - check out dockerfile-roast — a linter written in Rust that literally roasts your Dockerfile. 63 rules, brutally honest output (but it can also provide just dry facts, no roast), runs on any OS or as a docker container github.com/immanuwell/doc… #docker #devops #kubernetes #backend #linux #rust #sre #containers