samus7070

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.

Agreed on the M1. Anything entry level for Apple is decent but not really meant to push the envelope very far. I had a 16GB Mac mini and it served me very well for software development. I had to run multiple ram hogging tools at the same time so it did have pauses when switching between them. Other than that it was a beast. It held up well compared to my higher end MacBook Pro i9 with 32 GB Ram. The M1s run very cool. You’ll wonder if your machine even has a fan except if you’re doing a long intensive processing job. The M2s from my experience run hotter. I have an M2 iPad that I’m betting becomes thermally throttled just by watching Netflix. Not that it stutters, it just becomes warm to the touch.

Keep in mind these things don’t really know anything. They’re good at saying things that seem to fit the situation because that’s how they’re trained. They are like that person you may know that thinks he knows everything and will just say stuff that sounds right to them. The only difference is the ai is a lot more practiced than the human. Google’s llm may have some filtering done on the output to at least make sure that all of the books it recommends are real though it wouldn’t surprise me if there’s a fake one in the list somewhere. These things are prone to “hallucinations” which some lawyers found out the hard way.

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.

Yeah, it’s a bit on the extreme side for me. 10-20 is what I prefer. I find that if I follow that rule the code is easy to come back to later because the things a function does are more clearly defined. I can look at a higher level function and it’s filled with function calls like readX, createY and doThis. I don’t have to look at as many blocks of code and try to remember what the intent was.

It’s a highly opinionated book but it is full of good advice that in my opinion goes too far. Using a metaphor here, I think he wanted to get people to the moon but knew that he needed to give guidance to get to mars because people would look at whatever he wrote and think it’s too much.

The book has several chapters discussing the SOLID design principles and showing how to apply them. You’ll be a better programmer for reading it. “Uncle Bob” the person can be a bit problematic so I don’t particularly like telling people to give him money. Try getting the book from the library or a second hand store. There are also videos out there of him speaking at conferences that may give a good taste of the material. He has a blog too.

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.

The answer is always “laid off”. They don’t usually verify because the former employer will only verify that you worked there and your start and end date. They don’t want to open themselves up to slander lawsuits.

Find a job you love and you’ll never work another day in your life. I believe that was Churchill.

I enjoy the line of work I’m in. I don’t always enjoy the companies that I do it in. Some are much better than others. It’s fine to like or even love where you work as long as you realize that you’re in what could easily become an abusive relationship at any time. Do your time and do it well but don’t go out of your way to do it. That’s what I strive for.

In my experience a PIP is just a nice way to say it’s not working out, go ahead and start looking elsewhere, you can stay on a while longer until you do find something else. With all of the tech layoffs over the last 18 months, they might as well just dispense with PIPs too.

While lua ships a standalone interpreter, it is very much designed to be embedded directly into an application. This is done by invoking some C apis to load the interpreter into the application’s memory space. OP wants to do that rather than invoking another process and reading the output. When embedding into a host, the host can provide its own objects to be manipulated by the user script allowing for a much better extensibility experience.