As a counter point. Every time I've seen people get themselves into trouble with git has been when they are using a GUI tool. I have yet to see a gui tool that they can use to get themselves back out of it. There's a lot of value in knowing your way around the command line side of git even if you regularly use gui tools to interact with the repository.
We use slack internally where I work. There is a somewhat unwritten rule that you should not use @here or equivalent as a general user. There are a few cases where it's ok to if you really have something for everyone in the channel ( Aka don't run this it's broken type stuff ...) so some channels leave @here enabled. Still, I go From mildly amused to feeling sorry for the unsuspecting newbie who didn't look at the size of the channel and think: Do 4k people really need to hear about my problem?
Be an expert with the ability to generalize in your back pocket when you need to. A generalist skill set does not mean you have to do generalist jobs either.
Both of those statements convince me even more that this is a bad idea. While the author's past experience is important, it has little bearing on the current PR. Same for similar code change. In code review, the skill/history of the developer is only really relevant when writing comments. You should look for the same potential mistakes and logic errors in a Senior or Junior developers PR. Adding the developers experience as an input could easily lead to the model deferring to experience. In my mind, that makes the signal this is providing potentially harmful, not helpful.
Without something that semantically understands the code under review ( which all but requires general AI or at the least a strong static analyslzer) doing anything more than adding noise to the process or worse leading to certain groups of developers effectively being given a free pass.
I highly disagree with their definition of different from each other. Usage together does not make the words similar. If they'd said something about words you would not find together in a sentence then I'm certain you'd get very different results.
Honestly, this looks like spam. I have no idea what a token is, how you get them, or how to use them. The token ui stuff in the site doesn't tell me any of this in a way that I can understand. The site needs a lot more background on why tokens are something I care about before I could take it seriously.
What really matters is where that 5 thousandths is ... If it's in the wrong place, that could compromise all kinds of things. Maybe not immediately, but definitely down the road. Watch a few May Day Air disaster episodes, some of the most innocuous sounding things can cause a crash a decade down the line ...
They aren't taking away anything, they would be diluting the 51% shareholder's shares. They're giving themselves the option to fend off a hostile take over by making the pool bigger so that no one can get to 51% ownership.
If this is real, that's a big step. The beginnings of something like shell people in Anne McCaffery's The Ship Who Sang. I wonder if the technology will actually go anywhere.
I'm having a very hard time getting past the fact that the "wrong" code is wrapped very badly on both a mobile device and laptop. That inherently makes it harder to read ...
There was a period of time where the TS3+ was completely unavailable. Our IT people were saying that the manufacturer couldn't get parts to build them. :( I was lucky enough to get one before that happened and can say it works great. I'm using a SUW49DA from Viotek. The only issue I have is that something keeps waking the monitor up overnight but not sending a video signal. This eventually causes the monitor to shutdown and stop waking up until it's physically power cycled ( i.e. unplug/replugin). Otherwise, it's been great.
Personally, I use NO_COLOR or other techniques to disable color when I'm logging output or using a CI/CD pipeline. Color codes tend to create all kinds of garbage in your logs otherwise.
“By the time I was fourteen the nail in my wall would no longer support the weight of the rejection slips impaled upon it. I replaced the nail with a spike and went on writing.”
Grading the homework is not the same thing as providing feedback. A big red X tells you that something is wrong, but not what you can do to fix the problem or even why that thing is wrong.
> His answer was that I may just not have the "mathematical maturity" for the material. I was so discouraged that I dropped out of the program.
There's a problem with making a statement like that and not following it up with what you need to do gain the needed "maturity". Even adding "maybe you should take this course over here and come back to this one in a semester..." could make a world of difference.
I built a little toy that watches for node changes in k8s and adds them to haproxy load balancer. Mostly because I wanted ipv6 and digital ocean didn't have a load balancer that supported it.
I wonder what the limits of this are? From a naive point of view there has to be a point where training/skill/physical endurance/etc. come into play. The bed experiment seems to fit a fixed rate, assembly line style of work. While I would agree that numeric/performance ranking is mostly meaningless, everyone knows that one somebody you go to when no one else can fix a problem.
Not everyone can use them. I have sinus allergies and astigmatism. The combination makes it hard to fit me with lenses that actually correct my vision well enough to be useful and makes those lenses very uncomfortable almost immediately.