It was originally meant as a better JavaScript and it was. It failed when none of the other browsers expressed interest in supporting it. It languished for a while and then was taken up by the Flutter team. At the time Flutter took it up it was somewhere around the level of Java 8 in features but not quite on par. Since then it’s seen some massive improvements to the type system and language. It’s completely null sound, not just null safe like Kotlin. It recently got records/tuples and one of the more capable pattern matching syntaxes I’ve ever seen in a functional imperative hybrid language. The next stable version of dart will introduce a compiler macro system that is very promising. The syntax isn’t always the prettiest due to it trying to not totally break old code. I do think that it offers a wide range of modern language features that competes heavily with Swift and Kotlin in the mobile space.

The only things JSON has over xml is that it’s easier to write a parser for it and the format is less verbose and less complicated. There are extensions to JSON that can add features that xml has and the JSON spec doesn’t have. Overall the xml spec is bigger and has more features but that also makes it overkill for many of the cases that it would be used in.

They tried like hell to keep it off of the ballot in Ohio because they were afraid of what did happen. I can’t say if all of the dirty politics influenced people who were unsure how to vote in the opposite direction the GOP intended. Statistically speaking the final vote wasn’t even close. That is what they fear.

Have you ever driven through a small town and seen a police car sitting right where the speed limit drops? Those tickets and the kangaroo mayor’s courts are the only reason some of those towns are still alive.

I have one of the Voltera dev kits. It’s not bad. It probably runs at almost the same speed as the m1 mini or maybe closer to the dev kit. The x86 emulation is decent. It doesn’t do well when running old games like Age of Empires 2 HD. For doing light development it is okay. The nice thing is that it is far more efficient than anything Intel puts out. Whether Qualcomm can keep the performance per watt to levels like the M series chips remains to be seen.

That’s already happening. What’s more is that training an llm on llm generated content degrades the llm for some reason. It’s becoming a mess.

Baking recipes should be in weights for any dry ingredient. Converting them to volume measurements produces inaccurate results. One person may pack the flour in harder than the next. However baking requires precise ratios to be right. Change the ratios too much and that bread recipe just became a cookie recipe.

There is a school of thought that break and continue are just goto in disguise. It helps that these two are more limited in scope than goto and can be considered less evil. If you read the book Clean Code by Robert Martin (it should be required reading for all developers), you’ll see that he doesn’t like functions to be very long. I think his rule is no more than 4 lines. I try to keep mine around 10 or less with a hard stop at 20 unless it can’t be avoided because I’m switching over a large enum or something. If you put your loops into functions then you can just use return instead of break.

I did have a discussion with a teacher once about my use of early returns. This was when I had returned to school after many years as a professional programmer. I pointed out that my code has far less indentation than theirs and was simpler because of it and that it is common in the world outside of education. I got all of my points back he has deducted.

You’re going to hear some good and bad advice from your teachers. Once you have a job check out what the good developers are doing and just follow them.

There’s a thought that most of them are running for the vp spot. If Trump wins he’ll only be able to serve one term. Whoever is the vp has an advantage in 2028.

The only reason I can think of is for more on device ai. LLMs like ChatGPT are extremely greedy when it comes down to RAM. There are some optimizations that squeeze them into a smaller memory footprint at the expense of accuracy/capability. Even some of the best phones out there today are barely capable of running a stripped down generative ai. When they do, the output is nowhere near as good as when it is run in an uncompressed mode on a server.

If you’re following agile it is important for a team to agree on a definition of done for a story. If you don’t have one ask the scrum master to start that conversation or bring it up in a retro. One of the things that everyone can usually agree on is that the tests pass. Throw in a minimal coverage threshold as well. It’s not an indicator of good tests but it will tell you when there isn’t enough.

You mentioned that you’re doing this work for a client and that they will take over the code. Verify with management (in your company) if there are any quality measures specified in the contract. You don’t want your guy not performing up to the client’s expectations and you having to put in a lot of last minute nights and weekends to get there.

Story wise they didn’t leave much room for a sequel. It gets wrapped up nicely at the end. I didn’t play any of the DLC but the impression that I got was that a lot of possible sequel material was covered in them. The game was really good and definitely worth picking up on a sale price. It will give BotW vibes but don’t think of it as a clone. It’s got a good story and a nice little twist at the end. The boss fights were a joy if not painful at times. The puzzles were mostly good and not too obtuse. I think I had to use Google on a few of them. It is annoying with the extra clothing and style purchases that the game tries to get you to spend real money for. It tarnished an otherwise good game.