"".to_string()
probably
BehindTheBarrier
I feel this is related, and hightlight this even further, look at all the ways to initialize something in C++.
https://www.youtube.com/watch?v=7DTlWPgX6zs
If you are really lazy, have a look at making an int at around 7:20. It's not horrible that alone, but it does show how many meanings each thing has with very little difference, added on top of years of legacy compatability accumulation. Then it further goes into detail about the auto use, and how parantheses, bracket, squiggly bracket all can be used and help with the mess.
None of those issues for my main IDE, though Rider on some occasions do get stuck marking some spelling errors after they are fixed.
It has stuttered a few times, but pretty rare. But it does have a bug where it think it is building a project, but isn't. And requires a restart to fix... Easy to trigger if you try building a project while it's loading the project...
Visual Stuido with Resharper is the one where things would randomly stop working though. Especially hotkeys would sometimes stop working until I restarted it. Slow and stutter too.
In my country the consultant company i work at shifted to only going for hiring experience / senior people once interest rates went up 2023-2024. The economy being worse reduces investments, and naturally consultants are less desired during those times. So we didn't even meet hiring goals for 2024, we barely grew. I think expectations are a bit better this year though, if that is a indication that also applies to your country/place.
It's a strong contrast to where I, with Master degree in non-tech areas, got a developer job shortly after university at this company. Things were pretty desperate "hire, hire, hire" back then. It also helps that my country is less bad on interviews and such compared to the US.
Not sure if this advice really applies, given i haven't used Git for any reports myself and I don't know how you are doing the text based project. I did pretty much all my uni reports in a online latex document site which allowed shared editing, so there was some history but all edits were live to the main doc.
But with the power of latex at least, you can have the main file do import and usages, and maybe some setup. And then combine other files representing anything you want. Such as one for front page, one per chapter or one for appendixes.
Then just can do changes/new sections in feature style branches, and it's up to you if you want things to go to the main branch, or have a dev like branch where further refinement can happen if your work is structured and not all over the place like my report writing was.
A worthwhile note is also that pretty much all US car manufacturers have dragged their feet doing EVs, excluding Tesla. So naturally US car manufacturers are struggling a lot with the massive costs related to adopting EVs now, and struggle competing with a country that spent this money getting established a good while ago.
The subsidies are still a problem, but the 100% tax is in my view a massive handout to domestic manufacturers that never bothered to try until they were behind. That 100% price increase in Chinese will probably mean high margins on EVs for yet some years before cheap alternatives come along.
The article goes into the first point though.
Using those services on your behalf is, potentially (in a legal sense) use of your data. By providing some information to a third party, even if Firefox itself doesn't itself use it. This may come from the fact that you don't directly agree to terms with the third parties when you start using the browser, with safe browsing for example. So Firefox is in a sense using/sharing private information. And in the changing legal landscape this usage may fall under modern privacy laws, such as the one mentioned in the article.
I agree the old wording was bad, but I do see the reasoning behind the new one.
I'd expect modern cars to use proximity detection which means the fob only needs to be with you.
Like my Peguot has a fairly large fob, but it's just in the pocket of my jacket. Never leaves it. I guess it's a problem if you don't have a semi permanent thing like a jacket you use every day though.
Github actually does that too, in some cases at least.
https://trufflesecurity.com/blog/anyone-can-access-deleted-and-private-repo-data-github
There's GUIs for it though. Obviously not for everyone, but I made my own.
That it can download virtually from any site is pretty useful, assuming you know what to give it.
My solution to most things, make it a chore.
Like, if you don't buy it, you can't drink it. If you have it, put it in an inconvenient place so you you won't see it or bother getting it.
I know my product managers don't use chatGTP because they end all sentences with
...
, every damn time. And I'm fairly sure their habit developed independently, given that one of them is from a relatively recent purchase of a company.