You realize that Bitcoin is traceable, right? You kinda picked the wrong crypto to use as an example. Unless you’re completely in the Bitcoin system and never connect to any outside system or interact with anyone who interacts with an outside system or interact with anyone who interacts with someone who interacts with an outside system or so on (it’s not quite ad infinitum), you are most likely traceable. Tools like Chainalysis have been used by governments for almost a decade.

Your other points aren’t really valid if you ever want to convert Bitcoin to something that isn’t Bitcoin. I’m not aware of complete supply chains and grids that exist solely on Bitcoin (or any combination of crypto for that matter) so things like having control of your money, needing ID, and trusting centralized entities (sure, exchanges plural) are a huge part of Bitcoin.

I don’t know about selling directly to shops. A lot of owners can be weird about that. I’ve made plenty of deals with people playing at the shops, though.

Part of this is because the article’s author pushes a lot of sensationalist content to drive traffic to their Rust book(s). I remember similar articles several times over the last year, at least one of which was a thinly disguised ad for the Black Hat Rust book. That doesn’t mean the author is wrong, necessarily, but it does get annoying after a bit.

You might check your friendly local game store(s) too! Some of them might be willing to buy them from you or put you in touch with local folks who would be interested.

ZeniMax was doing dumb shit long before Microsoft. Bethesda has had a clueless culture for more than a decade. 2019’s disastrous performance across almost all verticals not only showed how clueless both BGS and ZeniMax were, it also paved the way for the Microsoft acquisition so Altman could get his bag. Todd Howard and Pete Hines let their original successes go to their heads and forgot the market changes.

While it’s certainly true that some classes of bugs are very easy to fix (“oh shit I forgot to apply the correct style”; “I mean to use this method whoops”), many bugs that exist in later-stage games require pulling a bunch of shit apart to figure it out. They’re in the same pool of difficulty usually as performance optimizations or balancing new functionality. Getting a successful test case can be difficult even if the bug is readily apparent. Getting the regression test to pass is the subject of a plethora of literature. It can be hard and difficulty often scales with codebase. If the bug was obvious and easy, it would have been done before.

If it was obvious and easy and wasn’t done before because of time constraints, devs can still charge more because their wages should have gone up. This whole thread OP is kinda nuts (not the commenter I’m vehemently agreeing with and expanding on).

It doesn’t sound like you have a good grasp on the differences between this case and Ross Ulbricht.

I wasn’t aware Silk Road was taken down via FISA. I’ve read all of the long form accounts of it that I’m aware of and I don’t remember FISA being mentioned at all. Can you share a source?

I am not surprised by either the author or the HN community completely missing it’s getting harder to die if and only if you can afford it or want to throw your family into crippling debt for the rest of their lives. This might be a US problem only. I rolled my eyes when the article opened with “sophisticated New Yorkers” and then completely ignored the cost all of this incurs.

The Supreme Court has already ruled the police have no duty to protect. I highly doubt there will be a ruling in favor of the kids. If there is one, there’s absolutely no fucking way it stands on appeal in the Fifth Circuit or Supreme Court.

It wasn’t obvious because I’m not quite sure why someone would suggest using software that both needs regular updates and will never get any more updates because those updates along with good faith open source contributions have been moved behind a paywall.

Which one? The deprecated one without updates? Or the paid one that’s basically RustRover?

The baseline cloud certs should be much cheaper. AWS Associate tiers are something like 150/test.

You might also have luck with the big consulting companies. NTT, Slalom, Accenture, stuff like that. Might be less permanent but will pay pretty well.

PyCharm and IntelliJ Community don’t have commercial restrictions. I’m still pretty anti-RustRover given this and the whole bait-and-switch where they turned the open source Rust plugin into what is now a closed source, paid editor. JetBrains still had done nothing to ameliorate this.

If you are able to find a US govt job and can make it through the whatever period you need to be a contractor until you get hired on as a federal employee, this should cover you. I have a contact in a similar situation except cluster headaches. It’s going to pay less than private sector and you might have to learn some new skills for the right role. IIRC Softrams just landed a huge federal contract and hires warm bodies; might be a great place to start.

I’ve got a lot of contacts on the market right now struggling to land a gig that wouldn’t have struggled a few years ago. Do you have DevOps skills? Any security qualifications? Get both. Are you working on certs? Do some. Have you hired a resume service? Do so. The last two are things I normally think are kinda bullshit but they are edges that seem to matter right now.

As for a recruiting firm, I feel like all the good recruiters I’ve worked with would have advocated for me. That’s a total fucking crapshoot tho. I’ve worked with plenty that have shafted me. I don’t think there’s a specific firm for this problem.

The only feature that vanilla Make doesn’t have over this is solid Windows support.

I’ve evaluated a ton of these tools for CI/CD processes and common task management. So far I have found that Make is the best solution for task management unless you need strong Windows support. If you want to go crazy, you can use Autotools but that’s really only for builds not tasks. I get it; it’s cool to reinvent the wheel with a new feature that makes one thing a little bit easier.

I carried BAND-AID® Brand TOUGH STRIPS® (had to go look it up to get all the bullshit right) in my wallet for years. I highly recommend these specifically because they work incredibly well in situations most bandages don’t. I used to slap them all over while working in a wood shop for a variety of reasons. They stay on all day even doing crazy shit. They’ll cover just about anything pretty well including harder spots like fingertips.

I don’t carry them anymore because I have a deathly tape allergy and they will kill me now. I get so many little nicks and cuts to this day that I wish I could slap those fuckers on.

All of the science isn’t based on a single study with fifty college kids. Here’s another one and another one and another one and a meta study. Since you disagree with accepted science and literature, I’m gonna disengage. If you’d like to provide more than your interpretation of the world, I’d be happy to continue. I’d take some analysis on cognitive load, maybe some understanding that people other than you exist, certainly less rambling about a specific bad experience(s) you’ve had with explicit methodologies.

Thanks for taking the time to respond. I’d really like to see some citations.

• Interruptions suck for office jobs
• Check flow state citations in intro
• Search for “lean [your field]” and whichever lean principle you’re curious about

I know sharing facts won’t necessarily change your opinion; I wanted to highlight I’m not talking out of my ass to everyone else reading the thread.

If every request is an emergency that needs to immediately interrupt everything else, then your throughput is drastically reduced. The extra cognitive load that comes from the interrupts also affects throughput. If you constantly have to watch DMs/channels/email for work that might pull you away from your existing work, you’re not hitting a deep work state.

Unless your role is intentionally interrupt-driven requests, it’s much better to drop items in a queue to be processed regularly. The tighter the deadlines, the more important moving from interrupt-driven to queue-driven is. The last 30+ years of workflow research coupled with neuroscience have really highlighted the efficacy of queues.