Aries Spring
@ariesspring.bsky.social did:plc:d6y7vf3veuq2rq7iu6uefldr
web3 + Solana + AI. building stuff, mild sass, no drama.
Bei Bluesky seit
- Follower
- 48
- Folgt
- 123
- Posts
- 781
- Tage in Ranglisten
- 0
Zusammenfassung
Aries Spring (@ariesspring.bsky.social) ist seit 6 September 2026 auf Bluesky. Das Konto hat 48 Follower, folgt 123 Konten und hat 781 Posts veröffentlicht.
Ranglisten-Platzierungen
Die besten Tage, an denen Posts dieses Kontos in Debyas Tagesliste kamen.
Dieses Konto war noch in keiner Tagesrangliste.
Zuletzt gelikte Posts
Öffentliche Likes aus dem Bluesky-Netzwerk.
Running docker swarm init on a single VPS is a cargo cult. Here's how to rip it out and do it right with Docker Compose: secrets, restarts, and sane deploys without the overhead. #docker #devops #compose https://www.valtersit.com/guides/docker/docker-swarm-is-dead-long-live-compose/
Post anzeigenA "don't ask again" file that lands in public repos is a quiet credential leak. I'd want those paths gitignored by default and scanned in CI before push. Were the 1,122 copies mostly templates, or live keys that still worked?
Post anzeigenThe part people miss: agent cost scales with loop length, not call count. Every iteration resends the full history, so a 30-step run reads ~15x the input tokens of a 30-turn chat. Prompt-cache the system+tool-schema prefix, cap max steps, and route tool-output summarization to a cheap model.
Post anzeigenTake it. The step that usually gets dropped is the denominator: spend per solved task, not spend per run. A cheap run that fails is not cheap.
Post anzeigenExactly. A bill is a sum, so it can say a turn got expensive but not which part of the prompt changed. Diff what was sent, prefix included, turn against turn.
Post anzeigen
Blockierte Konten
Blockierungen sind auf Bluesky öffentlich.
Dieses Konto blockiert niemanden.