Wait I always use a fuckton of raw garlic in my hummus and it's fuckin delicious
Please, I do need this recipe. For reasons.
Agreed. Maybe there should be an option in the settings to enable/disable them automatically.
Linux or Windows?
As for your questions:
- this CPU will be fine for years for absolutely everything except AAA gaming.
- On Linux, 16Gbs of RAM is fine. As other said, prefer 2x8Gb instead of a single 16Gb.
- 250Gb of storage is very cramped by modern standards. I would go at least 512Gb. Buy your SSD from elsewhere, it's much cheaper.
- maybe grab an extra USB-C in case you need to plug an external drive while charging your PC.
Haha yeah I can't do concise, thanks ADHD.
Just make sure the case either fits a 28.5mm dial or takes a standard chapter ring. That's probably the only caveat. Parts from the reputable shops are guaranteed to fit so it might be more reassuring to start there. Parts on AliExpress need careful examination of the listing and customer pictures.
Also, grab a couple extra stems just in case.
Thanks!
It's not that hard really. I made about half a dozen Seiko 5 mods and small repairs with basic tools.
I'd say:
- Get a cheap watchmakers toolkit, it's more than enough for this purpose, plus some good wire cutters, Rodico watchmakers putty and lint free cotton pads for nail polish.
- get familiar with the terminology so you know what to look for and which ones you need (eg. movement, stem, crown, dial, hands, chapter ring, case, crystal, bezel, bezel insert etc.)
- because the Seiko 5 modding scene is huge, start with a cheap standard Seiko movement like an NH35 or NH36, and search for compatible case, dial and hands. Most aftermarket dials are the Seiko 5 standard 28.5mm, so most hands and cases assume this diameter.
- A good starting point would be an SKX007 base as it was the king of modding. Unfortunately, like all "real" Seiko 5s, it's not made anymore, but there are a truckload of compatible parts in a infinity of styles still being made, including cases.
- you can get cheap but random quality parts on AliExpress, or very high quality but rather expensive parts at reputable online shops like Dagaz Watch, DLW Watches, Namoki Mods or Lucius Atelier.
- The hardest part by far is fitting the hands, especially the seconds hand, the rest is trivial in comparison. Even cutting the stem to length.
- There are video tutorials everywhere on YouTube to help you on the nontrivial bits (inserting and removing the stem, fitting the crown, fitting the hands etc).
Don't hesitate to ask more questions ;)
Go AMD. The open-source drivers already provide the best performance compared to the closed-source ones, and are included in the kernel and Mesa, which means the cards will work out of the box. For the best performance and latest drivers and optimizations you should switch to a distro with more up to date packages than Debian if you plan on buying a current gen card tho. For example, Fedora is a very good mix between working OOTB, ease of use and bleeding-edge packages.
nVidia is... difficult. The open-source drivers are getting better but are still way behind closed-source drivers, and each closed-source drivers version only works with a single kernel version. It might work OK as long as the drivers and kernel are kept in sync (I think Pop! or Nobara have nVidia specific versions for this reason), but otherwise each kernel upgrade is a risk. Plus nVidia drivers are basically shit with Wayland and cause a ton of issues.
Intel has a good track record with iGPUs so discrete cards should be as trivial to use as AMD ones, if more at the entry-level performance-wise.
And that's why we're moving away from coding games where I work. Bad people try to cheat, good people can panic and shit the bed.
When I do interviews, I'm more interested in the candidate's relevant experience, what kind of issues they faced, how they were solved, if they think they could have done things differently, and how they think. Code itself is irrelevant unless I can review a sprint's worth of PRs.
When I ask more technical questions, I never ask for code but for an explanation on how they would tackle the problem. For example, I often ask about finding a simple solution to get all data relevant to a certain date in two, simple, historized tables. If you know window functions, it's trivial. If you don't, your solution will be slow and dirty and painful. But as most devs don't know about window functions anyway, it lets me see how they approach the issue and if they understand what parts should have a trivial solution to make it simple.
Sorry, the goal here was to offer a few sensible alternatives, not overwhelm the reader with choices. The gist here is "start with something solid, reputable and popular, branch out later".
Too much choices lead to analysis paralysis, and to goal here is to learn how to swim first. There are dozens of great distros, probably more than half of that worthy to be on this list, as there are dozens of great DEs, probably more than half of that worthy to be on this list.
No chance. Amazon has a long history of using a ton of FOSS code on AWS and contributing fuck-all.
There are more bugs reported. That makes all the difference.
People used to closed source everything are trained to eat shit and find a workaround.
I moved my SSD from my old 8th gen Intel laptop to my brand new Zen 4 Framework 16. It was absolutely uneventful. Almost disappointing 😅