I am confused by this statement or it is going against what I understand.
If you have created a Type B variable, and you also have a new interface called A, and B implements A, then why would Type B variable's values be passed to A's values. 'A' is only an interface.
But yes, values inside B specific to type B will not be able to be accessed when manipulating the type A.
I go on site 3-5 days per month, and I always connect more (more than 0) with people outside my team and happens, even on work related topics which enable new interesting findings and what not.
It helps that the company where I work has a culture that make people want to go to the offices even if they are not required to do so. There are pics days when the office is full because people want to see each others, then they are free to remote work any time it is wanted/needed.
Also we should recognize that the waiter is often looked down at, it is not a very nice job, and as a human being, having a poor experience with some customers will probably pass on to other customers, etc...
I'd go as far as having a job with "wait" in the name, and having to wait, calmy and happily or else you don't get your tip, is not so far from slavery.
As it is, it's bashing the problem with regular expressions, and doing so badly. I mean, some of those words actually have completely different, non-offensive meanings in certain communities & contexts. (One of a few I spotted: Last time I used "retard" was in the context of ignition timing...)
Why not just say the truth "I could help you, but it's not my job, so I'm not going to"
Maybe, but most Git GUIs don't provide clear error messages. This is the case of VSCode, which my teamates keep using. When you use Git CLI you can just have the original error message and know what's wrong.
I was also burned by sourcetree some years ago where it lost part of my code while doing a merge I didn't even understand.
I am not a Git expert. But I can remember the 5 commands needed to do my job every day: `commit`, `push`, `pull`, `rebase`, `checkout`. (you can also add `add` and `status` to the list if you want)
They're straighforward, except for `checkout` which is adressed by `switch` for the main usage.
If you use it wrong, Git CLI will tell you in most of the cases, and even tell you how to do what you intented to do. Git GUIs will probably tell you something wrong happened and left you at that or try to be more intelligent than you are and do something wrong.
> Isn't that just being incredibly lazy.
-> this is what I'd answer to do those Git GUIs.
> Isn't that just being incredibly lazy.
-> this is what I'd say to people who won't write these 5 commands on a sticky note or something and keep it for a month before realizing it wasn't hard to remember once you _commit_ to it and that Git is not hard, minus exceptional problems but Git GUIs absolutely won't help you with these exceptional problems.
Also, Eclipse Theia could be the name of the last version of the Eclipse Java IDE since they named every major release of their IDE until recently.
Maybe they should have gone with Theia by Eclipse, or just drop the Eclipse in the name altogether.
Even in our connected world, there is no reason to provide blanket network access to every app on the device.