BehindTheBarrier

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.

Try making a list without copying every time you add something. Mutability matters then. Imagine copying 10000 elements, or copying 10000 references to items every time something were to be added or changed.

It probably makes sense if the program they came from is a badcase, but at least ours don't go over board. It's always a "you are probably doing something wrong, but we will allow it if you want to" or a "please confirm you want to do this thing that may have huge consequences". With what they were learning, they were not touching anything related to the latter. So they probably were doing something wrong.

I was on-site for users learning our new program. Watched them do something, a dialog came up, and faster then i could catch what it was, they closed it. Dialogs are warnings or confirmations you know, and they did not know what it was...

So yeah, sometimes I do think there should be a wait time on the OK button.

I'm still a windows pleb, so no Zed for me. Fleet I haven't heard of before.

I'm also very much one that likes a lot of convenience. RustRover is know from experience with both pycharm and Rider. But my main points are convenient functionality, autocomplete, debugger, code navigation, formatting and cleanup and git diff readily available. RustRover might be big and heavy, but it let's me focus on writing and running my code without much issues.

The following isn't any professional advice or anything, I am writing HTML manually for my hobby blog code. I don't have much experience with HTML outside occasionally reading it.

I write a bit by hand, to layout my blog page, which is using HTMX. Generally I use RustRover since that actually gives details for attributes and such along with autocomplete. And apparently yesterday it asked if I wanted to enable HTMX support, which was even more intriguing. The main articles are however converted from markdown to HTML.

I do want a better way to design with preview of my page but I think it's a long shot to find something that does HTMX at the same time. Especially since that often means having segregated pieces of HTML mixed into one document at page loading.