

I think I’ve never flown with that airline and this here makes it very likely that I never will.
I think I’ve never flown with that airline and this here makes it very likely that I never will.
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.
Don’t feed the trolls.
OnePlus probably.
Why is the headline in quotes?
You’re doing your part, but someone else isn’t. Everyone should learn as part of their upbringing that wasting food is bad - just like littering and thousands of other things. Unfortunately we live in a world where someone has to be fined for them to realise they’re doing something wrong.
Not even useful IMO, just idiots.
If you’re consciously and intentionally using JavaScript like that, I don’t want to be friends with you.
I’d be interested in how this documenting could be done. If you’re a manufacturer, you’d probably want to keep everything secret - except what’s needed for a patent for example - otherwise the competition might get an idea of the proprietary things you make in house.
I mean I’m all for it, I just don’t see it happening unless under very strict regulations.
Magic Lantern probably. Don’t know about compact cameras, but this thing was big with DSLRs 10-15 years ago. What’s pretty impressive to me is that it didn’t require flashing the firmware, it just booted from a memory card.
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.
Yeah, some of them like this one are not very well thought out, but I think for the most part they are - and when you put them in context, they should be searchable too. I’m saying this as someone who has never owned anything from Apple and who generally dislikes the brand.
Can’t not think of Apple who have been doing simple names like this forever. But contrary to this here, it seems to work in the Apple ecosystem because over there things like that mean one thing.
Left around the API drama times. I still visit, but haven’t posted anything for two years.
My only regret is that I still haven’t defaced my profile over there - I’m looking for ways to save my data and somehow link it to the original posts/comments, because besides the shitposting, I’ve posted some things that could be useful to myself too.