200 karma · joined March 1, 2020
Flat head: the bigger the better in this format, and simplicity has it's place, but easy to destroy in a variety of situations. Also, when you're out of options cutting a flathead slot into a destroyed screw might just work. The classic 6.5/10
Phillips: everywhere, but rather bad. You get a finite but unknown number of interactions with Phillips heads before it suddenly strips out and you're sad. This includes both the screws and the bits, Philips bits are the only ones I've ever had that shatter, the rest fairly predictably deform and can be retired.
Square (Robertson): bettr than the above. However, they're also like hex (Allen) but less good.
Hex (Allen): one of my favorites, and they scale rather well. BUT, if you strip it at all, maybe even once, you're done, the angles are shallow enough that there's no coming back, you've cut out a circle.
Posix: like Phillips if you squint, but if you actually use the right bit and, most importantly, push down harder than seems reasonable times 2, you'll pretty much never have a problem.
Torx: not lots of experience, and there's the rub. At the moment they're a hard bit for a layperson to find, regardless of their advantages
They may mean more specific things for all those things Plex "can't" do, but I can't tell from just the comparison page. Plex has plenty of issues, no need to make up more.
[1] A quote from their page on subtitles: Other formats such as VOBSUB, PGS, etc. may work on some Plex apps but not all. For the majority of apps, both VOBSUB and PGS subtitles will require the video to be transcoded to “burn in” the subtitles for streaming.
As I'm writing though, that probably wouldn't help in most university network setups, which the article mentioned. Tunneling is probably the path of least resistance there.
(I'm not really picking on your comment per say, I get your sentiment too)
Edit: also, to be fair to apple, it's the only real hardware complaint I have, despite being overall negative on the OS the hardware is otherwise great, which is why it's such an unexpected dissonance
Tech-wise, my "home server" is a business dell whatever bought second hand, main personal computer came from a startup liquidation, the computer that replaced went to a relative, and I've been able to re-home several routers/modems I saved from other folks apartment cleanouts (though the ones I have left are bumping against isp and speed limitations unfortunately).
I'm also looking forward to buying out my work MacBook for cheap when I get to 3 years, since it's rather beefy.
Also a swe, but in the US
1. Used it themselves and didn't move any faster because of having to learn a new way of thinking
2. Used it themselves and tried to do something that seemed reasonable to them but the no-code couldn't handle
3. Had a no code solution built elsewhere in a company dumped onto them for maintenance, or to be implemented into an more robust product. I've seen this play out as:
- Marketing/Sales "this mostly working and critically important to our pipieline, fold it into our system and add these 3 features. ETA should be like 2 weeks right?"
- Engineering "what is this? I've never heard of it. It's going to take like 4 months to fold it into our system properly and add those features. Why didn't you ask us to build this from the start? It would have taken way less time."
- Marketing "You said it would take a month to complete, and a month before it would be prioritized. We needed it in a week so we did this. If it only took us a week why will it take you months?"
1 and 2 are mostly folks who aren't the right target market, they're right and also they don't really matter unless you're trying to target those devs specifically. 3 is a real concern, because those are the devs who will campaign furiously against a product in meetings, getting burned by that once sticks around for a long time. And both sides of the conversation in 3 are often correct from their perspective, which makes it even harder. A no code solution that actually has an off-ramp to a more robust implementation would be an amazing way to deal with that, but that might always be against incentives.
To the examples, fly.io caught my attention primarily by offering a useful free tier DB, and tailscale has my attention as a "beat this" offering for some homelab access stuff (meaning some stuff could but I at least have a benchmark). Until this post I didn't actually know one was YC and another wasn't. I'm interested in both purely because of HN posts.
I believe this is the relavent passage in the article the GP is referencing, which is incorrect if you take "runtime" to mean something like when the line is executed: "Python is a dynamically typed language. By definition, you don’t know the real types of variables at runtime."
It _is_ however correct to say you don't know the real type _before_ runtime, at least python does not.
Edit: nearsighted, I don't remember the glasses prescription but contacts are -3.25
Aggressive minimizing is the best I've found. Basically only 1 pot meals and a dishwasher (two for pasta or rice I guess, but those pots can go in the dishwasher, even if it's kitchen sins). You can buy precut veggies and ground meat, chuck it in a stir fry with spices, use a bowl, spoon, and spatula, call it a day. Really the only manual cleaning then is the one pot (cast iron is great here because you can hit it with a metal scrub, quick and no thought even with burnt on stuff).
I'd expect all the groceries can be delivered without much premium (though I can motivate to get to the store most of the time so I'm not sure): onions, peppers, carrots, mushrooms, meat of choice, spices, basic sauces is 90% of it.
Also, learn to fry eggs and flip them in the pan. Removes the need to wash a spatula. Toast bagel, and the only thing to wash is the pan, and while it's still hot it's basically a rinse. Great easy breakfast/lunch.
What I can say is any cooking tool you do actually use, get it quality. If I use I knife I want it to cut easily, if I have a pan I want it not to stick and be easy to clean, if I have a cast iron I want to abuse it without remorse.
Obsolete feels like a strong term. for a problem thats truly document oriented workloads mongodb still seems more efficient, if not in literal performance then in scope and understandability. the mongodb API is the defacto "standard" API for document dbs as far as I can tell, and realistically SQL is a notable barrier for application devs. Also, operationally, mongodb is easier to run, between Atlas and having more clustering capabilities available for "easy". Those two things mean you _can_ move faster than with postgres (with the same relative amount of knowledge)
That said, for the aforementioned side project, a few nights got me the basic pieces of the API in place (next big step is the aggregation pipeline, which id argue is intermediate for mongodb and much less used), so it's not hard to adapt a codebase to pg/jsonb. And imo there aren't that many hardcore document only problems at the small or even medium size. And once you're at medium to large, the mongodb pain of transactions as a second class citizen, lack of data integrity options, schema fluidity, and overall less strict structuring makes Pg much more appealing. Pg/jsonb is powerful, and if you have someone willing to be a db admin postgres is extremely powerful.
So, mongodb maybe not Obsolete (it's popularity would attest otherwise if nothing else), but id take a better option if I were able. But if I needed a FE or mid-tier application dev to magically be an infra person, mongodb starts looking good again.
"Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for mometic.com. The certificate is only valid for *.mometic.com."
2. Double shift for Search all (actions, classes, functions, etc)
3. Learn a bit of regex for more complex file searches
4. Actually learn the debugger features beyond just breakpoint
Also +1 for refactoring tools, that's one of my next ide learning adventures
From clicking through to the documentation.
What are the usual sales tax requirements for GitHub Sponsors? To my uninformed self, having a normal repo that folks support is along the lines of general support, but a Sponsor repo starts to sound alot like a value provided.
The Mercy was deployed after some communication between New York hospitals, and the understanding at least was that it would mostly be handling emergency, trauma, and routine patients (what military docs are good are at as a stereotype), and free up capacity for the hospitals to deal with COVID. The "normal" medical stuff promptly dropped in demand with lockdown, between fewer accidents and deferred care. So there wasn't much for the Mercy to do, the few covid patients sent over were about all of an "unknown air transmissible virus" (working theory at the time) that it was really equipped to handle, because that wasn't the mission they were expecting.
[0]It's a whole lot of other bad things though: bad practice, and confusing, and something I'd never considered doing.