Divide by 2 and check for a decimal point.
I mean, it ain't wrong.
We have a client which is MAD cause the project is riddled with bugs, but the solution somehow is paying more attention. Except that it clearly isn’t feasible to pay more attention when you have to check, recheck and check again the same thing over and over…
By definition, automated testing means paying more attention, and doing it so well that the process is automated.
They say it’s a waste cause you can’t catch UI (...)
Show them a working test that's catching UI bugs. It's hard to argue against facts.
but they somehow think they are smarter than google or any other small or big company that do write test
Don't sell a solution because others are doing it. Sell a solution because it's a solution to the problem they are experiencing, and it's in their best interests to solve it. Appeals to authority don't work on everyone.
What does this GitHub Action offer anyone that one of Microsoft's official Docker images doesn't provide already?
Is there a simple way to do a http web server or socket?
What's your definition of http web server or socket? Most frameworks nowadays provide you with tools to get a fully working project up and running with just a couple of clicks.
For instance: https://start.spring.io/
So is it just Amazon getting hit for this? Or will they be going after the manufacturer as well?
Nowadays it's hard to tell the difference between Amazon and Ali Express. Even if it's a third-party dropship business selling through Amazon, it's still Amazon doing the listing, selling, and transaction processing.
Even if you argue that the same store can sell stuff elsewhere, Amazon is still the one selling those. At best, you'd need to argue that after hitting Amazon, other stores should follow.
You should also check out git commit --fixup ... paired with git rebase -i --autosquash ....
Superb tip. I'm reading up on the feature, and it sounds like the process I've just learned but on steroids. Thanks for the pro tip!
As a followup to this post, I've started including git rebase -i in my workflow when working on local branches. Basically things went like this:
- I start working on an issue in a dedicated feature branch.
- I commit small changes such as "Updates this feature in this component", "fixes this glitch on this function", "removes this dead code".
- I keep going until I'm done.
- If I stumble upon small nits, I just commit them right at the head.
- when I'm done I run an interactive rebase and move these small commits around to sort commits that belong together.
- nits and followup fixes are squashed together,
- cleanup commits are moved to the start of the branch to line them up to be pushed as a separate pull request,
- push a PR for the issue
To me this really paves a way to a far better workflow and faster turnaround times.
I don’t think you mean ‘merge’ - that’s a specific operation. I think you mean ‘squash’, which combines multiple commits into one.
Yes, you are right. I apologize for the terminology mixup. I was referring to how it's possible to join two changesets so that they can be considered in the commit history as a single commit.
Once you get familiar with rebasing, you could try out stacked git.
Thanks for the recommendation, but I'll take a pass. Vanilla Git does the job well.
appears to be a weak patch.
It's not a patch. It's eliminating an attack vector, and the one which is more pervasive and easier to exploit.
Security-minded people pay far more attention to what software you run than what hardware you have.
But we often hear about ‘corporate lobbying’ and you’ve described things mostly carried out by individuals or nonprofits.
No, I'm describing lobbying. The definition of lobbying doesn't depend on your market capitalization or revenue. A corporation does lobbying, just like unions do and industry representatives and community groups. If you have personal interests and want to raise awareness with stakeholders then you reach out to them.
I mean, Wikipedia's article on lobbying also refers to it as advocacy. From Wikipedia;
In politics, lobbying or advocacy, is the act of lawfully attempting to influence the actions, policies, or decisions of government officials, most often legislators or members of regulatory agencies, but also judges of the judiciary.
"Attempting to influence" is the operative principle.
And so is "lawfully". Which is not the same as the corruption you pinned on "Eastern countries".
I dare say anything from the GNOME project.
I'd love to see benchmarks testing the two, and out of curiosity also including compressed JSON docs to take into account the impact of payload volume.
Nevertheless, I think there are two major features that differentiate protobuff and fleece, which are:
In the end, if the world survived with XML for so long, I'd guess we can live with minor gains just as easily.