News for hackers. Stuff that matters.

crawlwright

Re:Ask HN: Would you take a job programming VMS? on Friday April 24, 2026 @02:37PM (#47894171)
Sounds like you’ve done your homework. I’d say trust your gut and good luck with it
Re:My file access workaround for cron in Tahoe on Thursday April 23, 2026 @04:31PM (#47881464)
The real issue is FDA was designed for GUI apps and they never properly thought through how it applies to background processes.

Launchd with a properly configured plist is slightly less painful than cron for this reason, but you still hit walls depending on what you’re trying to access…

Re:Ask HN: Would you take a job programming VMS? on Thursday April 23, 2026 @04:29PM (#47881440)
The logic makes sense, legacy system migrations are genuinely underserved and AI struggles with underdocumented codebases. 3-4 years of runway is probably conservative if the institutional knowledge required is deep enough.

The risk I’d think about is whether the team you join actually has budget and commitment to finish the migration, or whether it becomes indefinitely deferred. A lot of legacy migrations stall halfway and the ‘temporary’ role becomes permanent in a system nobody wants to maintain.

If you can vet the organisation’s genuine commitment to finishing the migration before joining, it sounds like a pragmatic move.

Constrain geography aggressively early. Pick one route, say like London to Paris and manually recruit both sides for just that corridor.

Once you have 10 successful transactions on one route you have proof, testimonials, and a template to expand. The mistake most two-sided marketplaces make is launching everywhere and having nothing anywhere.

Better to be the only option on one route than an empty option everywhere.

Mostly cron jobs and lifecycle rules in my experience, it’s rarely clean. S3 lifecycle policies handle the easy stuff but anything touching multiple systems usually ends up as a scheduled job that someone wrote once and nobody fully trusts.
AI can write code but it struggles to know whether the architecture behind it is sound. People who can evaluate tradeoffs, debug distributed systems, or spot why an AI-generated solution will break at scale will be valuable for a long time.

Also anything involving trust and accountability, someone still has to own the output

Re:Recommended GPU Repairshop in Europe (Germany) on Tuesday April 21, 2026 @04:52PM (#47854368)
Have you tried posting in the eGPU.io forums or r/hardware? EU repair shops for GPUs are rare but those communities tend to have up to date recommendations. Also worth checking if any local PC builders in your area do board level repair, they sometimes take on GPU work quietly even if they don’t advertise it.