Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tetha
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
83 ms
·
961.
▲
by
tetha
7y ago
In my book, the answer has always been: tabs for indentation, spaces for alignment. Tabs allow everyone to choose the gap for new blocks they like, and spaces make sure that a gap of 16 characters is always a gap of 16 characters (because w
962.
▲
by
tetha
7y ago
Mh, I fully agree that I don't expect '(cd /proc; echo *)' to hang because of the disk being full. However, with my current setup, the alerting checks all disks of all monitored systems every minute, and once a single of
963.
▲
by
tetha
7y ago
Hm. I am impressed by the casual kernel debugging. I couldn't do that. However, why would I have to do that if running check_disk on all important file systems tells me if file systems are >80% or >90% full? There'll be bugs
964.
▲
by
tetha
7y ago
I'm currently experiencing this, and especially the whole delivery vs discovery, knows vs unknowns and their impacts on estimations. It's quite interesting, especially how differently you have to handle delivery vs discovery proje
965.
▲
by
tetha
7y ago
I was reminded of golang as well. I kind of like this framework, because I dislike the overly magic dispatch mechanisms of annotation-driven java. Basic request dispatching in golang can look and be clunky, but that one clunky place tells y
966.
▲
by
tetha
7y ago
Sadly, that's an era old and gone. I'm still a friend of open WIFI like the freifunkers, or social computing - just ask and share some compute resources in my cellar. It's great to give kids access to programming and server r
967.
▲
by
tetha
7y ago
Yeah, size is one matter, technology focus is another one. We've been acquired by a bigger shop with a lot less technology focus and exactly what you're describing is already happening. Things that should take 2 month waiting for
968.
▲
by
tetha
7y ago
Reading the audit, this kind of confirms my base question when building infrastructure: If people don't do the right thing the business needs, why is it too hard to do? Can't we reduce the pain to do the right thing so doing the l
969.
▲
by
tetha
7y ago
The counterpoint to DRY doesn't seem to have a name, but it very much exists. I know it under the names of 'oversharing' or 'premature sharing'. Practically, this tends to extend the question of DRY: Is the code the
970.
▲
by
tetha
7y ago
>they will try to have several #1 priority items - sometimes by having several priority lists or categories that are all "equally important". I'm currently struggling with exactly that. We're the ops-team, so the infr
971.
▲
by
tetha
7y ago
I pretty much agree with this. From different hobbies, skill seems to determine two things: How much advantage or luck you need to utilize your skill, and the multiplier you get from your initial edge. This can be scary at a small scale lik
972.
▲
by
tetha
7y ago
On top of that, I find taking a shell and running `pwgen 24` much easier and faster. It even generates a couple of passwords if need a few. And can be piped into things like ssh sessions for automation. And yes, our recommended way is to ha
973.
▲
by
tetha
7y ago
Yup. And on top of that, my team does have slack time, but that doesn't mean we stop working when the mandatory tasks are done. We rather spend the downtime resolving time-consuming technical debt, automating some steps in the workflow
974.
▲
by
tetha
7y ago
We recently had a 15 month long project almost fail due to some stupid shit and a really wonky error no one understood so far. <Almost fail> as in "Keep the customer on the phone we have 3 possible things to try and don't ha
975.
▲
by
tetha
7y ago
Someone at our place recently commented that the ops team during an incident strongly feels like NASA mission control in critical moments[1]. I wanted to protest, but that's surprisingly accurate. > And if anyone is screaming or get
976.
▲
by
tetha
7y ago
>There's an unspoken dogma that without a $1000 phone and pricey Mac, you can't be a creator. You just made me realize an interesting cultural shift. I distinctly recall how an old 386 or 486 wasn't good enough to run the
977.
▲
by
tetha
7y ago
I'm more on the operational side, but I have the same experience. I easily spend 50% of the time I spend on technical topics documenting my findings. To us, good, structured documentation and/or well-written tickets are a crucial
978.
▲
by
tetha
7y ago
Something we have built for our stuff: There's a private repository and all applications run with minimum versions for their dependencies, so if there's a new available version, everything will update. Beyond that, we have a daily
979.
▲
by
tetha
7y ago
A product manager I've recently worked with had a similar approach. Don't ask: Why is X important. Always ask: Can I skip Y for X? Can I not do X to invest the same time to do Y? That kind of thinking has kind of put a very big tr
980.
▲
by
tetha
7y ago
I don't think that's relevant. If a software has a feature usable in creative ways, and there are persons willing to exploit the software, they eventually will. Exploits and malware will be written due to human curiosity and greed
981.
▲
by
tetha
7y ago
I've been considering and pondering similar things for my own career. I think there are two things going on. First off, there are assumptions that full stack developers are 100% amazing at all points in the stack. That's not the c
982.
▲
by
tetha
7y ago
To me it feels like a broader audience is starting to realize how much of an unlawful wild west the internet can be - and how much SIGINT and other entities abuse that. And how little preparations some networks have - networks with serious
983.
▲
by
tetha
7y ago
Not just -u - always <set -euo pipefail> unless you have a good reason. Fail on non-zero exit code outside of some special cases, undefined variables, and non-zero exit codes in a pipeline. And always use shellcheck, shellcheck is too
984.
▲
by
tetha
7y ago
I have lost dearly held content to the internet deciding to not host it anymore, including spotify. At this point, I trust my backup 2x SSD mirror more than some cloud. So I guess we're two old guys yelling at clouds. And this will jus
985.
▲
by
tetha
7y ago
This has been a complaint especially in the adventure game community. If I go to the cinema to watch the endgame or a john wick movie, I pay 10 bucks for 2 hours of movies. A lot of AAA games are a bunch of boring filler with some interacti
986.
▲
by
tetha
7y ago
I am sad with this threads discussion. Or I'm old. This is a logical step in lock-in disguised as user experience. Back in the day, if you could maintain the data, my 15 physical 3.5 inch rather unfloppy floppies were monkey island. I
987.
▲
by
tetha
7y ago
> Sure, on an otherwise 100% secure system accessed only by trusted users there is no problem, but not having . in PATH is a trivial mitigation. All systems are secure and sufficiently hardened until a botnet demonstrates otherwise, aren
988.
▲
by
tetha
7y ago
Incremental improvements to an infrastructure or rather the software ecosystem of a company isn't something many people talk about, indeed. Shiny new tools are interesting and flashy to look at. For example, I'm very happy with th
989.
▲
by
tetha
7y ago
Idk, in quake and other games, you had servers forcing no skins. Damn no-skin no-model, rail gun jousting boxes were utterly frustrating but darned fun to play on. This is a really weird change. I guess monetarily expected. Eh.
990.
▲
by
tetha
7y ago
No, I think that's exactly the point. I have spent some money on doom, counterstrike, quake, unreal or even chess. Or none on games like tremulous. I've spent a lot of time in these games, I've found friends in this games tha
More ›