> Someone just randomly joined my Tailnet
> Tailscalar here. Yeah, this sucks.
8mo ago but anyway.
https://www.reddit.com/r/Tailscale/comments/1ksy3xy/someone_just_randomly_joined_my_tailnet/
> Tailscalar here. Yeah, this sucks.
8mo ago but anyway.
https://www.reddit.com/r/Tailscale/comments/1ksy3xy/someone_just_randomly_joined_my_tailnet/
Reddit
From the Tailscale community on Reddit
Explore this post and more from the Tailscale community
Everyone hypes Zig’s compile-time execution, but most examples end up being Sudoku, chess, or other abstract math problems.
Yeah, there are cases where comptime is genuinely useful, but they’re far less hype-worthy. Compile time doesn’t simplify glue code, sorry.
Yeah, there are cases where comptime is genuinely useful, but they’re far less hype-worthy. Compile time doesn’t simplify glue code, sorry.
This media is not supported in your browser
VIEW IN TELEGRAM
Are we AGI yet? (Github's home page)
At least now I know why WiFi on my Mac is a shitshow
$ uptime
11:23 up 60 days
3 SEV-1 incidents in one day. Non-related. Different teams. Different projects. How was your Monday?
> If you don't know what you're doing, AI fails with death by a thousand cuts.
https://www.anup.io/why-ai-coding-advice-contradicts-itself/
I always find it funny when software... ahem engineers write 1k (I’m not kidding)
https://www.anup.io/why-ai-coding-advice-contradicts-itself/
I always find it funny when software... ahem engineers write 1k (I’m not kidding)
CLAUDE.md files but can’t write a Go doc for a struct or a README for humans, ffs.Gods gave us automatic code formatting, but mediocre peasants ignore it because discipline is apparently optional in their IDE.
UPD: sadly im not kidding, im literally in this shitshow, fucking comedy on steroids with ai
UPD: sadly im not kidding, im literally in this shitshow, fucking comedy on steroids with ai
Damn boi, that's a cool project. Finally it's not a custom ad-hoc tool per project but something reusable. At least that's how I see (want to see?) it.
https://boringsql.com/products/regresql/
And also in Go https://github.com/boringsql/regresql
https://boringsql.com/products/regresql/
And also in Go https://github.com/boringsql/regresql
boringSQL | Supercharge your SQL & PostgreSQL powers
RegreSQL - SQL Regression Testing Tool
RegreSQL catches query regressions before production. Compare query outputs against baselines, track EXPLAIN plan costs, and test migrations with confidence.
I Wasted 8 Years of My Life in Crypto
> The reality hit me like a fucking truck. I am NOT building a new financial system. I built a casino. A casino that does not call itself a casino, but it is the biggest, online, multi-player 24/7 casino our generation has ever concocted.
https://x.com/kenchangh/status/1994854381267947640
1k comments https://news.ycombinator.com/item?id=46181371
> The reality hit me like a fucking truck. I am NOT building a new financial system. I built a casino. A casino that does not call itself a casino, but it is the biggest, online, multi-player 24/7 casino our generation has ever concocted.
https://x.com/kenchangh/status/1994854381267947640
1k comments https://news.ycombinator.com/item?id=46181371
X (formerly Twitter)
ken (@kenchangh) on X
I Wasted 8 Years of My Life in Crypto
Damn, Apple's App Store Connect/TestFlight became fast as hell. At least in terms of delivering new build to the device/testers.
At the same damn time UI on the web is slow as hell, from the good side - nothing has changed, which is good.
Modern IT is astonishing.
At the same damn time UI on the web is slow as hell, from the good side - nothing has changed, which is good.
Modern IT is astonishing.
Regarding recent Github outage:
> In the Bad Old Days before Github (before Sourceforge even) building and package sucked because of the hundred source tarballs you had to fetch, on any given day 3 would be down (this is why Debian does the "_orig" tarballs the way they do). Now it sucks because on any given day either all of them are available or none of them are.
> In the Bad Old Days before Github (before Sourceforge even) building and package sucked because of the hundred source tarballs you had to fetch, on any given day 3 would be down (this is why Debian does the "_orig" tarballs the way they do). Now it sucks because on any given day either all of them are available or none of them are.
TTR 1w and everyone is happy.
Miss 1 standup and it gets escalated to the manager.
I think I need to change smth in my life.
Anyway, I have finished a deploy tool for my pet-projects:
This will definitely not make you happy, but I am. I can now easily do whatever I want with the services. Just a Go CLI for
~400 lines of code. The only things left are cleaning up binaries on the server (already 10Gb, oof) and tests (any idea how to tests SSH commands? lol)
(it even supports a multi-host setup but haven't tried this for real)
Miss 1 standup and it gets escalated to the manager.
I think I need to change smth in my life.
Anyway, I have finished a deploy tool for my pet-projects:
$ abctl
usage:
abctl build <service> | all
abctl deploy <service> | all
abctl canary <service> | all
abctl undeploy <service> | all
abctl start <service>
abctl stop <service>
abctl restart <service>
abctl reload <service>
abctl logs [service]
abctl status [service]
This will definitely not make you happy, but I am. I can now easily do whatever I want with the services. Just a Go CLI for
systemd, journalctl & go.~400 lines of code. The only things left are cleaning up binaries on the server (already 10Gb, oof) and tests (any idea how to tests SSH commands? lol)
(it even supports a multi-host setup but haven't tried this for real)
How do you design database API for
Let's assume we're talking about Postgres and JSONB column. We've
How you design such things? Definitely non-Go question, so everyone is welcome. Thanks in advance.
update and patch queries?Let's assume we're talking about Postgres and JSONB column. We've
UpdateUser where we just set new value to this column data JSONB but for PatchUser we just want to update fullname field in this column.How you design such things? Definitely non-Go question, so everyone is welcome. Thanks in advance.
Goroutines: the concurrency model we wanted all along (2023)
https://jayconrod.com/posts/128/goroutines-the-concurrency-model-we-wanted-all-along
https://jayconrod.com/posts/128/goroutines-the-concurrency-model-we-wanted-all-along
jayconrod.com
Goroutines: the concurrency model we wanted all along
Goroutines are the single feature that distinguishes Go from other languages. They look very much like threads, but they are cheap to create and manage. Go's runtime schedules goroutines onto real threads efficiently so you can easily create lots of goroutines.