You can only get so much better at reducing "dumb" deaths and injuries when you spend all day every day around things that will kill you if you touch them.
I think there is a bit of survivor bias here. People like to say "everything is shit now, I've had this item for 20 years and it still works." But that's because they can see that 20 year old item, not all the shit they bought 20 years ago that broke and they got rid of.
I'm kind of glad this is all happening because it provides a nice example to point to when I try to explain why I don't want to be dependent on a vendor for these sorts of things.
A label is fine. With USB the risk is that the thing doesn't work as well as it could. It's been the situation forever with extension cords that they have the wire gauge printed on them, and in that case the risk is that if you choose the wrong cable you will burn your house down. Labels are good enough.
Yeah we were trying to develop an internal corporate MacOS desktop app and the amount of shit I had to go through just to get it to the point where someone who isn't a developer was able to run it was absolutely insane. In the end a lot of this is probably even counterproductive as people get used to these sort of things coming with instructions to disable all security and paste these sudo commands into a terminal to get it running...
As an American that stuff is fairly inconsequential to me, although I am already aware of those things so I wouldn't even have a reason to ask. Likewise a Chinese person probably wouldn't have much interest in topics that a US-based model would censor. I guess the answer is just for everyone is that if you are going to talk politics with a chatbot, don't use one from your own country.
Of course he presents a hypothetical person who honestly earned a billion dollars, because he can't name an actual example. All you have to do is double your million dollar business every month for a year and a half! I'm sure this genius would take me up on my offer to work for him for $1 on the first day and doubling it every day for a month, right?
Why would remote working have anything to do with the amount of junior hiring? You can maybe make the case that remote work isn't as helpful for juniors etc etc. but that has absolutely nothing to do with the decision to create a job requisition or not.
I wish I could do the same thing. Coworkers would be allowed to ask me X number of questions per month, and once they hit that limit I get the rest of the month off.
I'm one of those cowards that always succumbs to the pressure and ends up tipping, but it bothers me enough that I just won't buy anything if I know I'm going to get asked. This is good training.
But it is being continually refueled. The output of an LLM, at least in the process of generating code, is a combined product of human creativity and the LLMl. I have told it what to do, fixed what it got wrong, and verified the solution was correct through testing.
Interesting that I read elsewhere that most Venezuelan oil goes to China due to the sanctions. Would be nice to see them put a carrier group down there to guard their shipments...
Is the new Gemini really that good? The "AI Overview" stuff on the google search page is so incredibly bad that I have never even given it a look. If so, the AI Overview is horribly bad negative advertising because it's so useless and frequently completely wrong.
Why not do it in English? I have a "program" that exists entirely as the history of an AI chatbot session. To "run the program" I load the history and a file into the message context and say "Now do this file." It kind of reminds me of a Smalltalk VM in a weird way.
I've always seen estimates as trying to guess the highest number the PO will accept, the time or effort involved in actually completing the task is irrelevant. I have never had a PO or anyone else complain that a task was completed more quickly than expected. However I do have to be careful to not tell them it is complete too early, lest they start expecting shorter cycles.
At least in my company we've stopped calling them "estimates". They are deadlines, which everyone has always treated "estimates" as anyway.
Unfortunately in the real world deadlines are necessary. The customer is not just mad that they didn't get the shiny new thing, especially in the case of B2B stuff, the customer is implementing plans and projects based on the availability of X feature on Y date. Back to the initial point, these deadlines often come down to how quickly the customer is going to be able to implement their end of the solution, if they aren't going to be ready to use the feature for six months there's no reason for us to bust our asses trying to get it out in a week.
In my experience, having to track my hours absolutely destroys my performance. Thinking about how I need to pay attention to how long I spend on everything is a constant distraction in the back of my head while I try to do anything useful, and then I spend the rest of the day procrastinating having to fill out the paperwork. I know I'm not the only one because the entire dev staff was ready to mutiny the last time I was at a company that tried to get devs to start tracking their hours.
It sucks if you're looking for entry level work, of course. However, I'm a TL/manager with mostly entry-level reports and I have told them for a while the other side of this mentioned here - by the time they get to senior level they are going to be able to name their price in the shortage.
I'm staff and that is probably the main thing I use AI for. It's maybe a bit ironic that AI is a lot better at sounding like an empathetic human being than I am, but I'm still better at writing code.