This has mostly to do with not leaving them everywhere, but if they’re randomly left in the parking lot, some people will happily steal them. Plus this was in the same notion of not trusting people to do what’s expected.
This has mostly to do with not leaving them everywhere, but if they’re randomly left in the parking lot, some people will happily steal them. Plus this was in the same notion of not trusting people to do what’s expected.
Wait until I tell you about the coin-operated shopping carts.
I know my I am, same thing here, but even when I do, if it’s a bag previously bought from the same place, they usually want to verify. Maybe the system’s watching for the store logo on the bag. Most likely they have cameras watching the self-service checkouts to make sure you don’t do anything funky, i.e. weighing apples and selecting carrots on the screen.
Either that, or I have to wait for an employee myself for the stupidest reason, i.e. that I’ve brought a canvas bag that they have to verify I didn’t steal.
Plot twist: they used a script to generate that code.
Version control should take care of it either way, but I’m talking about principles.
Notice how it’s suggested to cut instead of to copy the file.
Imagine you’re writing a front end and that the backend that will be serving the data is not ready yet, or it’s down for whatever reason, but you know how the data will look like. In that case you can write a test with hardcoded data as if it’s coming from the actual backend, and test several possible cases of the front end logic.
Another example is this: say you have some functionality that’s behind some UI that you have to click through; you make a change, the page refreshes and you have to click a bunch of stuff again - until the next change when the page refreshes again. If you have to do this over and over again, things get inefficient. Instead, you can write a test to make sure the functionality handles the data properly and only then go through the UI to maybe test this or that edge case.
Plenty of other examples, but yeah, depending on what you’re doing, you might not need tests at all.
That’s overly broad.
The only appropriate reaction for this I have right now is “Bruh”.
Why is the headline in quotes?
I don’t know why you expected me to expect it to look like Terminator. I never said that.
AI has its merits, but in this instance I’m commenting on the fact that it would sometimes trample over the silliest little things.
AI will take over the world /s
If you’re consciously and intentionally using JavaScript like that, I don’t want to be friends with you.
I disagree.
While AI might help at systemising and/or summarising already existing information, I wouldn’t rely on it at all for any creative thought. And what’s worse, the more people spare content like this, the more tolerant they’ll become to it, bringing the overall quality down.
While we’re at it, can we also talk about things that look like chat notifications, but exist only to draw your attention? Those are misleading as fuck and IMO should be ruled out as well.
Tried it, it’s not that.
Any half-decent editor/IDE/command line tool will scream at you about this; plus there’s version control which should help you spot it as well.