sorter_plainview

If they have measurable thickness in sideview then it is not 2D. 😎

The problem is not when I have to rebase. I know how to handle it. But with juniors they approach us only when things are in a really bad situation, where they cluelessly applied some commands they found on internet or from an LLM. Then it is very annoying to sit down and untangle the mess they created.

And regarding the pushing without fetching, it is usually a different branch. So they won't incorporate the new changes in the main branch into their working branch, but just push their work into a branch. Again not a big deal. Just annoying.

That is a very weird setup. I have no clue why that flow is needed in the first place. Branches should be something disposable easily. What was the logic behind the setup? Any idea?

See all this is fine for someone with good experience in git. They know how to solve the screw up. But wih junior devs, who don't know much about it, they will just get confused and stuck. And one of the senior has to involve and help them solve. This is just annoying because these can be avoided very easily. Until they understand the pattern of how everyone operates with git, it just creates issues.

To me first time causing this issue is completely fine. I will personally sit with them and explain then what went wrong and how to recover. Most of them will repeat it again, act clueless and talk like they are seeing this for the first time in their life. That is the difficult part to me.

May be I'm just old school, and a grumpy old person, even though I'm not that aged.

So this workflow is needed if you are working on a public, i.e. multiple devs collaborating on a single branch, scenario. But it is much better to avoid this as much as possible. Usually it is a 'scoping' issue, where you create a branch that is too broad. For example 'api-for-frontend', which is a massive thing.

But let us say you absolutely have to get multiple devs on same branch, then this workflow is totally fine. There is nothing wrong in it.

In our org we prefer to delete the branch after merge. In a way it says 'this branch is closed'. This is to encourage devs to define smaller and more logically scoped branches.

I want to take this opportunity to say that, branch is just a label on a commit, with some additional functions. Once you start focus on commits and lineage of the commits, then branches become some what irrelevant.

Yeah.But many of them are extremely annoying. Specifically screwing up rebase. It is recoverable, but very annoying.

That said I have seen juniors make two other common mistakes.

1. Pushing your commit without fetching
2. Continuing on a branch even after it was merged.

I'm fed up with these two. Yesterday I had to cherry-pick to solve a combination of these two.

After 2003, the only set I liked was 2018. Even the current iteration looks like a bad evolution.

That is a much difficult question than I initially thought. I think it is the high saturated slightly dark orange. Mainly because I do some design works, and it is bloody difficult to find a matching color. So far I found only white or black.

Disclaimer: I hate this guy and all the stupid things he did in the past.

I don't understand the issue here. Assuming what he is telling regarding the safety features are true, this is not more dangerous than a stunt scene in a movie. If they had hired someone who is not a professional stunt man, I would classify this as 'dangerous'. But I can't really see the issue of shooting a 'stunt scene' with professionals, just like any action movie will do.

That said, I think this is just manufactured outrage, which will create more views for that video. Probably thile response to the video was underwhelming, and they wanted to drive up the views to ensure revenue.

Hey, kiddo.. Remember how we used to say college will improve your chance of employment and quality of life? Turns out that is not true, because too many of you got educated. So now we don't have people to do all the menial jobs and act as a servant for the upper class. Therefore stop learning. And be uneducated, and you will be rewarded by employing you with the most rich people on earth. (Clarification: as servants)

I wonder how it will be if there are no elites? And all are equal?

The important question is what is the ToS violation stated in the comment. Proton is on the right side, if the CERT actually provided evidence for the violation of ToS. Believing what the journalists said, one of the accounts that is still suspended was being used for disclosures.

All Proton had to say was "we have clear evidence from the complaint that there is violation of ToS".

On the other hand if they acted solely on the words of a CERT, because it is under a Goverment, we have a very different issue at hand.