I love grammars. It’s like an API or a data schema, but for a language. This would be very cool and I would love to see it!
I love grammars. It’s like an API or a data schema, but for a language. This would be very cool and I would love to see it!
It is Fast!, and also, (it is secure 🔒)
I recently picked up a pipe. It has all the rituals and escapism of a cigar, without the hour-long commitment.
That being said, sometimes being”occupied” for an hour is part of the appeal. Each has their place ime.
But then arr.length == the last index, and that’s just too convenient :(
The good old days. We ate berries in the woods; enjoyed the company of whomever we pleased; and worshipped the moon simply because it was cool.
Then we invented turbotax and multi-factor authentication :(
Is American Pragmatism a thing? If you explain it to me, will I feel better about myself?
Devops is a meaningful term
You’re out here solving impossible problems. You’re “The Fixer” from Pulp Fiction. Fools look at story points. Pros see an unsolvable story that languished for years until you came along and defeated it. A single point for you is an entire epic to other teams.
Everything is a differentiator that can be spun to your advantage. The points aren’t accurate, and you’re the only one with enough guts to step up to the plate and finally work these neglected tickets; even if it won’t “look good” on some “dashboard” - that’s not what’s important; you’re here to help the organization succeed.
If the system doesn’t make you look good, you have to make yourself look good. If you weren’t putting in the effort, it would be hard - but as you say, everyone who takes a deeper look clearly sees the odds stacked against you, and how hard you’re working / the progress you’re making; despite those odds.
Don’t let some metrics dashboard decide your worth, king!
I’m very flaky here, as rust is the big one, but I think zig and/or nim might be
Indeed, and good points. How many users do you have? I assume this isn’t just for you, and setting up multiple nfs shares with tailscale access policies isn’t feasible. SMB might be the best play. I’ll have to refresh my memory on file sharing protocols
NFS for storage, tailscale / wireguard for access control?
Your current setting is the “loopback” address. You’re listening for traffic to this address, and the only thing that can send to the loopback is yourself. This is a safe default, it means only the computer running the software can talk to it. Generally 0.0.0.0 listens on all available addresses. If that doesn’t work, use your local / internal ip.
This ui smells like it’s trying to hide the implementation details, but that makes things extremely difficult when troubleshooting
Vscode already supports linting yaml against a schema file. Once you start configuring your code with configuration-as-code, you’re just writing more code.
If I need to “generate” some insane config with miles of boilerplate, I would use js to build my json, which can be ported to just about anything. This would replace js in that process.
I’m not sold on the need for this.
Even with something like k8s, I’d reach for pulumi before I put another layer on top of yaml.
You can reduce doorknob turning dramatically by running on a non-standard port.
Scanners love 80 and 443, and they really love 20, but not so much 4263.
I used to run a landing page on my domain with buttons to either the request system / jellyfin viva la reverse proxy. If you’re paranoid about it, tie nginx to a waf. If you’re extra paranoid, you’ll need some kind of vpn / ip allow-listing
Hello yes my email is dot at dotat dot at
The other six are (copied from the article):
Phone picture album roll? Photo reel? Downloads folder! But on a phone. Apple hates calling things folders idk lol
Excellent! Thank you :)
Thank you, that’s an excellent read! This reminds me of the “expected value of perfect information” - sometimes it is worthwhile to answer a question, and sometimes it isn’t. Every once in a while I find myself in an engineering call discussing a minor problem, and I run the numbers to see if the change we are discussing is even worth talking about. One time the combined salaries of the people on the call had already outpaced the cost savings of the change over the next 10 years. We quickly stopped that discussion lol