nogridbag
Me: "Send a message to <wife>".
Gemini: "OK what's the message?"
Me: "Can you bring Tylenol I'm having a headache?"
Gemini: "I'm sorry, I cannot help with that. If you need medical advice..." <-- or something to that extent.
Up to this point, I thought when Gemini would prompt for a message, it would simply accept whatever I said essentially as plain text - and maybe with the new Rambler feature on Pixel phones it may cleanup my message slightly.
But now I can see scenarios where Gemini would possibly need to parse my input. And it should have been obvious since I would often say things like "cancel" and I never questioned it.
The human in the loop did not properly delete an invalid license plate number from one of the databases the flock system checks against.
The issue issues are with:
1. Human in the loop
2. Third party database police use for homicide info
3. Police response
I don't see what the license plate reading technology has to do with any of this. It seems like the only thing working reliably.
We have tons of wrapper classes in our codebase which seem ideal as value objects. For example, instead of passing around "String emailAddress", we have a wrapper class EmailAddress. While we can now make our EmailAddress class a value object, we cannot do "==". Unlike ZoneId in which there's a fixed set and you can intern all ZoneIds in the string pool, email addresses are unique and trying to intern all email addresses would be a bad idea. So it seems like using .equals is here to stay even for these types of basic classes.
I have seen a surge of overly complicated PRs now that we're in the AI era, but it's our job to be the gatekeeper and push back on this crud from entering the codebase. And that's likely true of any language.
Plus, I don't believe Cancel reverts changes the user made if they clicked Apply already. So your suggestion would go against how the UX of OK/Apply/Cancel has historically worked.
The teacher likely didn't know that he used to be my best friend growing up, and at some point was more knowledgable with computers than me. He introduced me to things like IRC. But he became one of the most popular kids at school and started distancing himself from me.
After getting our papers back, he came over to brag about how he found his paper online and that's how we discovered we submitted the same exact essay. At that point in time, I thought the teacher must have assumed he copied from me. But I think your explanation is likely more plausible. I guess the teacher just skimmed the papers and graded based on our expected grade.
And then said developer does what they think feels right: "I have my state and I simply want all the fields to reflect my state". So they try and rewrite the component into some sort of mini immediate-mode style component. All of the event handlers get wired up a single "layoutComponent" method that tries to call all the UI component setters based on the current state with all the problems you alluded to. I know I've done this type of things numerous times before going back all the way to my first internship, well before React was even a thing.
I think modern frameworks solve the reactivity issue this well enough, that it really doesn't matter if the underlying framework is not natively reactive. I will say though that I've primarily used Vue.js where most state is relatively local and we don't try to re-render the world on every input. I think part of the problem with modern dev is likely that React has become the default instead of a simpler framework like Vue.
I've let her play around with Google Docs before. But what I really wanted was something like Creative Writer that is more kid friendly. I used Gemini (sorry) to suggest some software and it suggested "Book Creator" which is intended for schools/teachers. I signed up as a fake teacher and added my kids as students and they did create some really creative books, importing images, and adding their own drawings. But it's still missing that kid-friendly vibe like Creative Writer.
I remember also receiving that weird VHS tape from Nintendo in the mail: https://www.youtube.com/watch?v=rJzIc_c1PvE
I have no idea how I received that, but it was so cool!
But then VideoGuide [1] was released (available from RadioShack). I begged my parents for that and honestly it was the most amazing product and worked flawlessly. I felt like I was living in the future.
I had to add my signature and write in the date so it looks like it was handwritten. So the plan was to just draw the date with a pencil tool and if that failed use the text tool to write the date.
First I instinctively clicked the pencil icon which turned out to be a highlighter. That's a great example where if they had added color for the tip and line it would have clearly looked like a highlighter. After that failed, I clicked that "i" icon because it looks like it's for inserting text. Honestly I was in such a rush I didn't even see the info pane popping up and was dang confused when nothing was happening.
I'm very familiar with info icons and have used them in my own apps, yet I had never seen one without the circle around it.
Your link appears to be a basic ray tracer which anyone who has taken an intro to computer graphics course in college is likely required to implement and would only need a javascript canvas. To be honest I have no idea how much OPs real-time ray tracing differs in complexity from traditional ray tracing.
In a declarative framework, while it is still technically possible, it is very rare. The current app I'm working on is one of the largest front-end apps I've worked on (multiple years of dev). We've had a single infinite loop issue reported that was trivial to fix. We have very junior UI devs compared to teams I've worked on in the past, yet our UI defect rate is incredibly low.
You have your model (data), and conceptually, you just want to bind that model to the view. But you have to write all this imperative code to do that. It's very simple with an imperative UI to have infinite loops even with very simple UIs. "When this field changes, I want to update this other field". But that other field has it's own event listeners that trigger other effects. The event listeners work fine in their own silo, but the interactions between fields cause unintended effects that are not obvious reading the code.
When the component is mounted, the behavior is very hard to reason about and you spend lots of time in a debugger tracing through all the event listeners just to reach the initial state of the UI. Additionally, in these frameworks the developer is typically responsible for cleaning up all the event listeners. It's very easy to forget to clean these up properly.
Once a UI reaches a certain complexity, you try to rewrite the imperative code so that it almost reads declarative and you wish you could simply use a declarative UI framework. I can't speak for React as I have not used that in a long time, but in Vue.js I never write the UI to use global state. All state is local to the views that it pertains to and with defineModel introduced back in late 2023, you can write small UI components without all the plumbing required in earlier versions. I've never experienced such a simple and reliable UI framework previously.
private void execute(Stmt statement) {
switch (statement) {
case Stmt.Expression expression -> evaluate(expression.expr());
case Stmt.Block block -> executeBlock(block.statements(),
new Environment(environment));
...
public sealed interface Expr permits
Expr.Assign,
Expr.Binary,
Expr.Call,
Expr.Function,
.... more exprs hereThat was also what I tried doing to try and remedy the problem. The problem is normally when you want to deactivate cruise, it's because there's a slower car in front. And it's a bit unnerving to accelerate towards the slower vehicle (even if ever so subtle) when the goal is to deactivate cruise. I've attempted this about 3 times on the highway and it just didn't feel comfortable so I stopped doing that. I wish there was simply some setting so that after deactivating cruise there was some smoother ramp up to the current regen setting. For example, after deactivating cruise it's max-regen should be similar to ICE vehicle deceleration, then after N milliseconds ramp up to last used regen. That would solve the problem for me.
I have a really hard time using cruise control in my Genesis EV. I usually use one of the regen breaking modes, and when you disable cruise control, the car will automatically start regen braking unless you have you have the throttle at the perfect position which is near impossible. And that's much more noticeable if you use one of the more heavy regen modes.
So I have to follow this pattern: Disable regen, engage cruise, use cruise, disable cruise, enable regen just to use it for a few minutes. And with the Genesis, every time you change between regen modes the car kind of jerks a bit. I've heard this is not really a problem in Teslas. Of course I could simply not use regenerative braking (a major feature of the car) or I can attempt to change my driving habits and not use cruise control as often. For long drives I much prefer my ICE vehicle specifically because of this.
The other thing may be related more to my driving position. The car is heavy and rides harshly over bumps which causes my foot to accidentally push harder on the throttle for < 1 sec. And because it's an EV which has quick acceleration the car occasionally will accelerate fast after I hit a bump. I've driven a ton of ICE sports cars with hard suspensions and never had this problem. Perhaps I'm just getting old and now have bad reflexes!