That’s so weird, I wonder how that works. If I’m the first to make a map or a street or any geographic object in France, it can’t be featured on any other map, unless so license it?
No, I get what they're saying, especially with older dialects such as C64 BASIC. It may be approachable to beginners, but the thought of trying to maintain software written in it isn't incredibly pleasant.
On the C64, I find even 6510 / 6502 assembly to be easier to follow than C64 BASIC.
As nice as this is, I would not want to wait 6 months for a dishwasher. Give me the cheap LG that will be here next week, I will buy that fancy Miele when they sort out their supply chain issues.
I'm an executive in the music industry and I'm familiar with the details of the situation. I can't talk about the specifics, but I can tell you that your guess is very close to the reality. There is one additional twist, but you really have to understand how the music industry works to guess it.
That being said, sometimes a good abstraction can really simplify a complex problem by dividing it up to a set of smaller sub-problems. In such cases, the abstraction is worth it even if there is no reuse. As always, rules like this have to be interpreted in a context.
It doesn’t look like this will stop supermarkets from tracking people, this will just require them to share that information with the government, so this tracking will be in addition to the existing tracking, not replacing it. I would say that’s objectively worse.
Eh, some software engineers are good at product. Some are even good at charming clients. You got to understand the people you work with and adjust the processes and roles to match that, not the other way around.
says who? accessibility is not that hard to achieve if you know what you're doing and make efforts from the very beginning to build your product in an accessible fashion
If you have to change one of the underlying values, you only need to change it in one place. Of course, you could just use constants, but then you’ll just have a const enum with extra steps.
This is speculation, but maybe it catches unintended infinite recursion earlier? I’m willing to bet that the vast majority of stack overflows happen due to programming errors rather than genuine uses running out of stack.
Also, you know, specs can and have bugs. You can have the most comprehensive requirements and specification and a 100% correct implementation of the spec and still end up with software that just doesn’t work, because the spec and the requirements had incorrect assumptions, or worse, had internal contradictions baked into them. Happens all the time. Best to just accept it as inevitable and design the process so that it can cope with it.
At least on iOS what worked for me to stop this from happening is airplane mode + wifi enabled. It probably won’t stop it from jumping to another network though.
> The car manufacturers sell their cars through the dealers. If every time they make an EV, the dealerships don't order them and steer every customer away from buying them, that's just as much a problem for the car manufacturer.
But that's not how cars are sold, at least not in the United States. Manufacturers don't leave it up to the dealers to decide what vehicles they can push and what vehicles they can steer customers away from.
Dealers get a vehicle allocation. Some of the allocated vehicles are cars that are easy to sell. Some of the allocated vehicles are cars that aren't easy to sell, but the manufacturer wants to push them. If the dealer wants to get more of the cars that are in demand allocated, they need to push the models the manufacturer wants them to push.
This is very common in the entertainment industry. If you think the story of Viacom and CBS is crazy, look up the story of the Victor Talking Machine Company and its many descendants and “relatives”, including RCA, HMV, JVC, EMI, Capitol Records and many others.