samus7070

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.

Most of the DC ones could. They tend to be OP. Marvel tends to use less powered characters but certainly not always. Hulk and Thor come to mind immediately. Really the answer comes down to how much plot armor are they equipped with?

I thought this was going to be another story about a developer being banned for life. I’m glad it was only the app. Be on your best behavior now OP. Google has ways of linking old and new accounts and then banning all of them. They’ve even been known to kill business accounts that hired banned developers whether those developers were still employed or not.

I’ve used SwiftUI nearly exclusively for the last 2 years now. Most things work great and I have little desire to switch back to UIKit. I do wish it was more backwards compatible (not going to happen) and there are certainly rough edges where it integrates with UIKit.

In Ohio we refer to him as Gym Jordan because of his role in squashing a major sex abuse scandal of OSU athletes. The man was no good even before he jumped on the Trump train.

I generally have a view model per screen. I define a screen as a view that takes up most or all of the screen at one time. Each of your navigation items is one screen. Each bottom sheet I would count as a screen. There’s some flexibility in the definition. For instance if you have a dialog or bottom sheet that just has some small amount of information, it may not be worth creating a full separate view model. In the other hand, I find it useful to create mini view models for list items. YMMV there.