With that much hassle, mailing them the document back and forth would be a better way.
learningduck
joined 2 years ago
That's clever. Now Zig or any language that wants to compete with Rust would want to to come up with a better project to take the fame.
Does this mean I can have a body harvest farm? Cut their livers out, resurrect. New livers ready to be harvested.
It's the DDG's throwaway email plugin. It detects any email field and will show the icon automatically. If you press it, it will fill the email with a throw away email that will forward any email to your actual inbox.
If you use Firefox Relay, it will do the same.
So cool. Curious, Why do they need to specify that the project has to be implemented in Rust?
lol. My bad.
Yup. Have to ensure that you use "no" if you don't want yaml to equate it to false.
A robotic vacuum cleaner. I just have to clear the dust bin weekly and manually mob some spots that the robot couldn't clean
Especially for a pet lover or a parent.
My daughter fell asleep as we were reaching a destination. I could just leave the AC waiting for her to wake up on without causing any noise nor carbon dioxide.
Reading the 3rd paragraph and I see myself 😄. Glad that you and the team managed to add another layer of testing successfully.
You run E2E test before each merge. So, you don't merge very often?
How about running an integration test before each merge instead of a full fledged E2E and mocking out external dependencies (other services) during the test, then do E2E testing on a schedule like nightly?
I prefer it this way, because mocking out external dependencies cut out network instability and bugginess from dependencies. So, we can merge faster. Agree that test scenarios are overlapping, and if your E2E is very stable then it is probably not worth it, but unfortunately it's not so stable in my environment.
FAX machines is still a thing in 2023!