One of the more rational things he's said. The US is not interested in holding him accountable and other countries aren't willing/able to risk attacking the US to kidnap him.
If only he could be as sympathetic and intelligent as The Gang.
I think you're correct that this is how Americans define "good businessman". But there's some missing cognition when they then decide that he should run things.
"A 'good dream' is when you're in a dream and enjoy yourself. Freddy Kruger has many good dreams. Therefore, I hope Freddy is in my dream."
It's basically impossible to tell with these between the example being totally fabricated, true but only happens some small percentage of time, true and happens most of the time but you got lucky, and true and reliable but now the company has patched this specific case because it blew up online.
Thanks for helping me remember watching Occupy Wall Street and Arab Spring fail :-(
I don't understand how you think this works.
If I say, "now we have robots that can build a car from scratch!" the automakers will be salivating. But if my robot actually cannot build a car, then I don't think it's going to cause mass layoffs.
Many of the big software companies are doing mass layoffs. It's not because AI has taken over the jobs. They always hired extra people as a form of anti-competitiveness. Now they're doing layoffs to drive salaries down. That sucks and tech workers would be smart to unionize (we won't). But I don't see any radical shift in the industry.
I've heard this from others, too. I don't really get it.
I watched a teammate working with AI:
- Identify the problem: a function was getting passed an object-field when it should be getting the whole object
- Write instruction to the AI: "refactor the function I've selected to take a Foo instead of a String or Box. Then in the Foo function, use the bar parameter. Don't change other files or functions."
- Wait ~5s for Cursor to do it
It did the instructions and didn't fuck anything up, so I guess it was a success? But they already knew exactly what the fixed code should look like, so it seems like they just took a slow and boring path to get there.
When I'm working with a new intern, they cost me time. Everything is 2-4x slower. It's worth it because (a) I like working with people and someone just getting into programming makes me feel happy and (b) after a few months I'm able to trust that they can do things on their own and I'm not constantly checking to see if they've actually deleted random code or put an authentication check on an unauthenticated endpoint etc etc. The point of an intern is to see if you want to hire them as a jr dev who will actually become worthwhile in 6+ months.
In my own experience, these are two different people.
One who hasn't thought about the actual evidence or legal burden. They just saw on the news that the suspect is definitely guilty and their reaction is: "yeah, guilty of killing someone who deserved to die. Rock on murderer-dude."
The other person is thinking about the law and the evidence presented so far and finds it pretty thin. They might or might not feel like healthcare CEOs should be executed, but I have not heard this type of person lauding Mangione for the killing because they are skeptical that he had anything to do with it.
It may be that your friends are less internally-consistent.
The job market is not terrible. But there is a frustrating thing where a "senior" developer with 3 years of experience will get tons of recruiter-spam offering them $200k+ positions, while a junior developer (your position) will get ghosted when you apply for a job that's offering to pay $50k. So it can feel demoralizing because people you see as your peers are having a very different experience. (And if you go in some circles the FOMO just never stops; people telling you you're wasting your life not being a Meta dev getting $800k TComp or founding a unicorn start-up...)
You say you enjoyed programming, which sure sounds to me like you could enjoy getting paid to do it. But it's easy to overwork yourself because your boss says that real developers pull 80-hour weeks. Or burn out because it's so frustrating to watch bad decisions ruin your good work. If you can find the right balance of caring and not caring, you can make good money and enjoy your job.
And it only takes a year or two to get rid of the "junior developer" label and then jobs are a lot easier. (Others have said that the market is bad. And it is bad compared to how it was in, like, 2020. But it's still a very good market all things considered.)
As an undergraduate, I wondered how it was possible to write code professionally, because I could only barely fit the semester-long programming assignment in my head. When I asked my professor about it, I got an independent study credit to learn about UML.
UML (as a representative example of thoughtful documentation) is a partial answer. But actually a much larger part is that with practice I can hold a lot more code in my head. Today, that semester project seems trivial and if I see a stack trace I can tell you how to fix the bug that caused that exception to get thrown.
As a senior dev, I'd answer "how do you remember what your code does?" with
- As you work, you get better at just remembering
- As you find patterns and follow them, you'll have less to remember (I bet I know what the
downloadUnpackUpdate()method does!) - As you do the first two, you'll learn to recognize when comments are helpful
Mniot
0 post score0 comment score
joined 2 years ago
I think "support the working class" doesn't have to mean "do whatever they say". We're all generally propagandized into oblivion. Like, the US working class has been concerned about immigrants and trans women in sports but it's not pro-worker to go after those things.