“learn Rust” in this case is learn it to a level where all of the little behaviour around cross language integrations are understood and security flaws won’t be introduced. Expert level.
It’s not “I did a pet project over the weekend”.
…and people worry about the name of a git branch.
I’m trying to understand Git, but it’s a giant conceptual leap.
To start with, start with just using git locally. Don’t worry about GitHub or similar. Then git and SVN will work very similarly. The main difference is that you need to git add files with changes inside before you commit them.
Once you’re comfortable with using it by yourself, then I suggest running something like forgejo locally to be your own code server. Then you can play and learn how the two parts work together.
Generally, you need to give yourself a little time. You need to do the work. Be efficient…sure, but don’t try to force it to be quicker than the time you need to learn.
Right, so you just have a single step and then hand over to a proper script. I’ve seen many people try to put much more complex logic in there before handing over to a proper language.
Config is fine, but Yamls biggest problem is people use it to describe programs. For example: playbooks. For example: CI steps.
If YAML wasn’t abused in this way it would have a lot less hate.
Sometimes your longest serving engineers can be your biggest anchor. Good engineers are (justifyably) highly opinionated about what can be done, but sometimes it turns into “what I do works, so all other ways are wrong”. At that point the best move for them might be to go learn how somebody else does it. Wish them well, and back a different horse.
Often the money if far more than the individual realises.
Depending on the country, there may be taxes or other benefits which rise to the same degree or more.
Members of the team or grade need to be paid amounts which are within some range so that everything is fair.
You may feel you’re worth more than the majority of others, but it’s rarely the truth.
A VP was brought in at the company I used to work for that claimed “I need to offer candidates substantial increases or else I won’t attract top talent”. He started hiring people at a significantly higher rate. (I left at this point) Soon, the other engineers found out and all hell broke loose. They demanded equal pay.
The company is currently in financial difficulties. The salary bill got too big. They’re now struggling to complete the projects underway because they’ve had to cut staff and the 40yo company is probably going to be swallowed up.
Is that an armadillo? Forgetting how my own code works is my forte.
Oh, “incident post-mortem” was ambiguous. I read “Incident that happened after death” not “analysis after incident”.
I thought OP had a necrophiliac blowjob fantasy.
With batteries that would have a multi-day cycle like these ones, you’re going to be trying to flatten out the demand curve (and supply, but the two are related).
The US generates 4.2 PWh a year, and so averages a consumption rate of about 480GW. So, in an ideal system we’d only need this level of generation capacity and if it was higher sometimes and lower others the batteries would smooth it all out.
I’m going to take your 560GW figure as representative of normal demand above the 480GW average. I’ll say half of every day is 80GW above average (when we’d be draining batteries) and half is 80GW below (when we’d be charging). The real curves are much more nuanced, but we’re establishing context. 80GW for 12 hours is 960GWh, so let’s call it 1TWh of battery capacity needed for the whole USA to smooth out a day.
That’s 117 of these installation, which frankly I find amazing that it’s so low.
I have a lot of respect for this project. I lurk on the discussion forum and issues and I’ve always seen mature discussion even though the project was born out of issues which could have been quite emotive.
It’s also a lot nicer to run than any other git forge that I’ve had experience with.
The most difficult part is to keep track of the big picture because it is so verbose. Otherwise it’s a handful or two of instructions you use 90+% of the time.
It’s a long time since I wrote any assembly in anger, but I don’t remember this being an issue. Back then Id be writing 2D and 3D graphics demos. Reasonably complex things, but the challenge was always getting it fast enought to keep the frame rate up, not code structure.
As you say, I think you just establish patterns to decompose the problem.
Only the most very basic compilers. C compilers are in C mainly.
Or you could make your life a lot easier and use Forgejo
Lucky it was set in America.
No. They are not renumbered. Your 11 is always the same commit. It’s consistent locally (which is what I mean by “local only”) otherwise they’d change under your feet. You just can’t share them with others and expect the same results. You have to use the hash for that.
You and I both clone a repo with ten changes in it. We each make a new commit. Both systems will call it commit 11. If I pull your change into my repo your 11 becomes my 12.
The sequential change IDs are only consistent locally.
No the old commit is always there, marked as obsolete with the information of what it became. No holes in history. (Assuming you use the obsolecense markers)
How about “To learn it to that level will take 10,000 hours I don’t have”? Does that make more sense to you?