I mean, if the North Korean employees are doing good work, the companies employing them aren't exactly incentivized to find out that they're really North Koreans, cuz then they have an obligation to fire their actually productive employee.
Huh. The onus is to do the personal verification during the interview and offer process. It doesn't make any sense to do it once the employee has already been onboarded, although it makes sense to visually ensure from time to time that they're still the same person that was interviewed.
The point is that there are legit American citizens who are in on the con. They have real SSNs and an actual presence in the US. They run proxy servers out of their house to make it seem like that's where their web traffic is coming from. From the company's perspective, everything seems like a regular remote employee.
A proxy server can't fool an in-person interview. Totally bizarre how in-person interviews have fallen out of fashion, now that they're needed the most.
I actually have first hand experience with this! One person came for the on site interview, and a different and much worse dev did the remote work once hired. This was over a decade ago now.
I actually don't think her reasoning has to do with other people at all. I think it's that given she wants to make an image of a poorly designed object, she knows she could either do it herself, or she could do something that takes 99% less effort but produces a result that's 90% as good. Her brain says "the easier way is obviously more efficient, clearly that's what you should do". But using AI isn't actually a satisfying process so even though it's way easier, she doesn't have a desire to do it. Of course the option to do it the way she's always done it is still there and would be just as satisfying in the end. The difficulty is that now there's a little part of her brain that would be going "you're acting inefficiently/irrationally", which just makes the process less pleasant and harder to convince herself to continue with. To me it seems like
I know I have experienced this, and I bet a lot of people here have experienced this, with writing code by hand vs having Claude do it. I genuinely enjoy writing code, but now to get that joy, I have to commit to writing code _for the sake of writing code_, since it's no longer necessary to do it to achieve the end goal I have.
I have the exact same feeling as you towards coding AI for hobby projects. Though this sentiment isn't new, and AI is just a detail.
I'm not a musician, but I'm attracted to synthesizers and bought a couple in the past just for fun. I immediately get caught in a quicksand of DAWs and plugins and whatnot, which kill the fun for me (it's too similar to work), but at the same time I can't ignore the tools because now the synth is too "bland".
I am a musician and electronic music is my primary jam. I once bought way too many plugins on Black Friday because there were so many incredible deals. The next day, I opened my preferred DAW and I was just overwhelmed with options. It caused my creativity to short-circuit. I didn't make music again for months because of the sheer sense of drowning in new tools.
Of course, every time I've ever added just one tool I've been fine. I explore it and learn it and figure out the limitations and how to make it do what I want (or decide I don't like it).
The brain is funny. It's not always possible to rationally explain our motivations and blockers in a way that feels satisfying. I'm a big believer that words help us understand feelings / reality. Not being able to articulate the things that are blocking us satisfactorily makes it harder, or possibly impossible, to work through them or try to tackle them or work around them.
And then there are the times when we can perfectly explain our feelings in a way that accurately represents the inner turmoil but it's just a crappy new reality. I think that's a lot of what people are feeling wrt coding agents.
Are your frontend builds actually so slow that you're not seeing them live? I've gotten used to most frontend builds being single digit seconds or less for what feels like a decade now.
Not build speed, the human review cycle. When the AI generates a component, I still need to read through it manually to make sure it does what I intended, handles edge cases, and fits the existing patterns. That takes 8-12 minutes per component regardless of how fast the build is.
The slow part is not the computer. It is me reading AI-generated code line by line before I trust it enough to ship.
Ok, obviously unethical to do it, but this sounds like you've got the power to create some sci-fi shared dreaming device, where you can read people's brainwaves and send signals to other people's masks based on those signals. Or send signals to everyone at the same time and suddenly people all across the world experience some change in their dream simultaneously.
Like, don't actually do it, but I feel like there's inspiration for a sci-fi novel or short story there.
I second this! I switched to mint recently. They are offering unlimited data including hotspot for $15/mo for up to a year if you prepay. I think then it goes to their standard rate which is $30/mo for unlimited, or $15/mo for 5gb.
I tried it for the first time the other day after having heard how much better it's gotten recently, and it made me really wonder how bad was the UX _before_ all these recent improvements. I don't want to bash on it too hard, because it's clear that a ton of hard work has gone into it, but it was really a struggle for me to get some pretty basic things done. The only feedback for a lot of things I tried to do was some not-very helpful error messages in the console, or just the whole program crashing. After trying hard for quite a few hours, reading lots of docs and watching tutorials, I ended up giving up and going back to Fusion 360.
reply