I’d rather just more farscape. Or a whole new IP. My biggest pet peeve with scifi is that they keep hinting at trying new ideas by leveraging old IP just for name recognition.

It’s good for business but bad for creativity.

I’ve had questions like your 3rd bullet point in relation to why somebody’s friend is having trouble with connecting a headset to a TV.

No idea. I don’t know what kind of headset or what kind of TV. They are all different Grandma.

As a senior engineer recently turned manager I hear this type of mentality from most of my junior all the way up to senior devs.

The only thing I’d suggest to you is spend some time digging into the tools you’re building outside of the project you’re working on. Just to get a general understanding of how the pieces fit together. Definitely do it during work hours, though. I’m in no way suggesting outside of work, here. Once you’ve spent enough time digging, you’ll surprise yourself in how effective you get at answering questions.

Internationalization isn’t about the translation. It’s about not hard coding the strings that display. Putting them somewhere that is easy to swap out would allow users to provide their own if they wanted.

If he’s getting to the first round of technical interviews then it’s likely not a languages issue. That’s the round that many companies put you in front of a mid-level dev who arrogantly asks you a code-kata question and refuses to answer questions. It may be that he’s not inherently good at solving the toy box problems on the spot. That’s the issue I tend to have in these rounds.

Though I guess it could be a languages issue if the mid level dev doesn’t know the language you’re doing the problem in and marks you down for that.

Overall, I think I prefer elixir, but is probably choose go as well.

Not just ease and performance but popularity. I could be happy in only go for the rest of my life. Currently a Rust dev and I don’t know if I can spend the rest of my life with lifetimes. They are an emotional challenge…

It’s only worth it if you’re planning to work in Java or one of the other JVM languages.

If that’s what you are striving for, is worth it to spend the effort ahead of time. If your goal is more agnostic to tech stack, learning Spring Boot won’t be worth it until you land a role that uses it.

It might be worth dipping your toes in the water anyways. But frameworks like that shouldn’t be bothered with without inherent interest or need.

Personally, I’ve no interest in working in Java, Scala, or Kotlin so I’ll skip it.

I figured it was something like that. I don’t think anybody in the industry believes kubernetes is even close to a great solution (it is a good one, just not great), but it’s mature enough that it solves most business needs well and there aren’t any good alternatives that I’ve seen.

Curious. Are you seeing those resisting k8s provide an alternative option for large scale orchestration of containers?

Lucille Ball was a comedian first and an actor second. That’s why.

This Is the 1701, Kirk’s. It only had 430 people on it.

Even some of these issues ORMs are solving can be solved without them by caching a view of the data in structure of the object. Relational DBs are extremely well tuned for looking up and caching data in an easy to view manner.

Somebody else pointed out the problem is bad devs not learning their tools. I’d go so far as to say DB knowledge can (and was due a while) be a specialized field full of skills that will fall by the wayside for most devs because we aren’t doing super complex things in a single DB anymore with the preference going toward microservices. There’s no need to flex those skills and they depreciate over time.

He could sense his son.

While true of OP, I was responding to the idea that I’ve could skip the entire first season on the first watch.

The first season is rough but it sets up a lot of things that are touched on in later seasons.

While definitely true for the most part, I feel like the first episode is pretty important for a number of other reasons and there are things in season 1 that are explored for Data that are referenced throughout the series.

This one is problematic. JavaScript has many flaws but it’s design of continuing to run through errors is beneficial to front end web development where the developer has no control over the environment.

If the only difference between two classes or structs is hard coded config, rewrite to be a single implementation and pass the configs in.

If it’s more in depth than that it may not be worth refactoring but future copies should be designed more generically.

I think Golang had the potential to take over just because it’s so easy to pick up and start contributing.

My last position was Golang focused and our hiring was never focused on experience with the language because we knew that if you understood programming concepts you would succeed in Golang.

Today, I’m working on Rust and while I enjoy it for what I’m using it for (Systems level instead of Web Services) I’d be hesitant to suggest it for most backend application just due to the ramp up time for new developers.

tl;Dr Golang will have an easier time hiring for because no language specific experience is required.

I’ve never heard of any of the brands that come up so I can’t recommend any of them. I just searched for “RJ45 90 degree adapter” and found a number of options.

No experience with them, myself. Just a quick look and I found CAT-6 cables with a 90 degree connector, a 90 degree male to female adapter, and a 90 degree adapter that has a short cable to move the female connection so that is easier to reach.

I’d get all 3 styles and try them out separately to see if there is any performance impact. I can’t imagine any significant impact on performance occurring but it’s worth double checking. The biggest issue I can see is just build quality of the part.