But you have to trust these odd startup companies with your cash. I don't trust them. Everyone's spying on everyone, and since they're startups the security is abysmally bad. Too many people are just far too trusting with new technology. A little bit of Luddite paranoia is a good thing.
It means that when you give your grandkids a few euros for Christmas, it's going to be a lot less impressive. "Hej, Anders, I deposited twenty euros into your phone, God Jul!"
I did spend cash when I was in Finland. It has many advantages that a credit card does not have. It intrinsically limits your spending (a good thing). It's fast, faster than a credit card in m experience. There is no hidden 2% fee to use cash. Pulling out a credit card for a $2 purchase is just silly in my view. There are things credit cards are good for also, but I wouldn't want them to 100% supplant cash.
The value is in the trust the general populace holds in the dollar. Same for other currencies. When trust is lost in some currencies then this can lead to massive inflation, something we've rarely seen in the USD. Cryptocurrencies have so extremely few users that I would so that the general populace trusts them.
Trust means more than "I trust that no one can steal my currency". It also means you can expect a reasonable level of stability in price, you can expect to be able to use it easily in your daily life, you don't have to convince a second party that your currency is good before you start a trade, and so forth. And cryptocurrencies are lacking in these. You can't walk down to the store and buy a loaf of bread with cryptocurrencies.
It is better that the dollar is not tied to the corresponding amount of gold, the economy greatly improved after these were untied from each other. The value is strengthened because we have a diverse economy with a very large population. This is similar to diversifying investments, a US state with a poor economy and one with a great economy all use the same dollar.
Development everywhere is a bit of a mess. It's just that some people mistakenly think that other successful companies are well organized. Ie, our own company's development may resemble the zoo's monkey house, but at least those big name companies know how to do things right... After all, they have thousands of developers, big buildings, free cornflakes in the morning, etc. Except that successful companies are also penny pinchers who don't hire as many people as they need (or outsource them) and have a slavish devotion to artificial deadlines.
I develop on the Mac, but not for the Mac or iOS, and not using xcode. We wait MONTHS before doing major upgrades, and weeks before minor upgrades. Apple is notorious for screwing things up. I'll do security patches but the updates always come with issues.
Having to update the day of a release is just silly, and if Apple is requiring this for certain domains (iOS 11) then that's bad to the point of making Microsoft look like a humanitarian organization. Though it does confirm my theory that Apple treats the Mac only as an iOS support system.
A patch rollback is not so easy on OSX. Just like with Windows, their world view is that no one ever rolls back. So, make a full backup before clicking the button that says there's an OS update.
It's probably just a bug. But Apple has not responded on this issue, there is no evidence that they're working on one. There are a whole lot of anonymous posters at DisplayLink forums who are bashing each other for being either Apple or DisplayLink shills. The longer that Apple ignores the issue the worse the blood feud is going to get.
No, if the spec said it was supposed to be a wildcard, then someone should have strongly questioned this. Ie, a bug in the spec. A dev saying "I just follow orders" isn't a good excuse. That's like saying you're just a programmer and thinking isn't a part of the job.
You can pass two laws that disagree with each other. Then the courts get involved. Laws do not negate prior laws unless explicitly written that way. And most laws are written to be murky. That's just with normal legislated laws, there are also treaties have full force of law in the US as well, and the US constitution, which makes it all very complicated.
So you're very often going to get two different opinions on a law, both of which have a solid legal framework supporting those opinions. When there's serious money involved, someone's probably going to sue about it.
Sadly, in this age of lobbyists infesting the cracks in the capitol, every issue is a political issue being bought and sold. And the whips in the two major party make sure their legislators all line up exactly as they are told.
I dunno, I know a lot of workers who I'd describe as having a very low EQ which causes severe problems. As in the expert in a domain who loudly thinks he's the expert in every domain and has alienated everyone at the company who actively avoid meetings that he is in.
A UI needs an expert and specialist. Customers will see that front end, so you really don't want a novice being the one to design and implement it. A problem is that people want someone who knows what the current toolset/framework is, and will bypass people with lots of training and experience in UIs over someone who knows the tools the company uses.
I know many really smart people who lack experience. They make the same mistakes as novices. Sometimes it's worse because they know they're smart and will work on something beyond their abilities. Sometimes the company knows they're smart and have a PhD and promote them beyond their abilities as well.
In Finland, I met people surprised that foreigners would even want to learn Finnish. Nokia did most of it's business in English, even in Finland. They spoke better English in their McDonald's than they do in the US, the taxi drivers speak English, etc. In Europe, speaking a second language is a necessity of life.
I don't do any web stuff or mobile stuff. I do embedded software and in some ways that's full stack, everything from assembler to build to application. But there are things where you do want a specialist, like security.
I think many of these skills I mostly learned on my own. But I had a CS/CE background with graduate schools, and every class came in useful for background and foundation, knowledge that I could apply years later.
I doubt I will be out of a job, the skills are in high demand with low supply.
If someone does come in to fix a problem, they should get an extra day off without it coming out of their vacation.
Sometimes I do come in, rarely, but that's usually because if I don't there will be giant headaches and extra work when I do show up. It's very very rare because everyone knows that it pisses people off to call them in at night or on the weekend, and if you piss off workers then you lose workers.
I don't even know who's calling me anyway, I don't know the boss' phone number and he's not in my contacts. There is sooooo much spam and robot calling now that I don't answer the phone anymore. If they leave a voice message that isn't spam then I'll call back. The modern telephone is now useless for phone calls because of this.
And even if I did have my boss's number show up on caller ID, I could still just claim I didn't know who it was. Time outside of work is MY time.
Hire extra workers for the night shift then. You can't legally force people to work 24 hours a day in the US, and being on call is essentially working for 24 hours. The companies are abusing the workers here and they need to stand up for their rights.
Also, as the article mentions UK workers, they already have lots of workers rights. Often you'll get a security guard upset if you are staying at the office late as it can annoy the unions. If they asked the same question in the US, I suspect there would be more who would take the call, and so many work long hours anyway as they've been brainwashed to think that this is "normal in the industry".
Back in early 2000s, the solution was to have two computers at my desk. One for doing work, and the other for Outlook or the occasional Word document. Just swivel in the chair to multitask.
Except that once you have Linux, why would anyone want to use Visual Studio?
It sounds like this might be a reasonable alternative to OSX, which is Unix along with being Office compatible, so that you get a convenient development environment but can still use the crappy enterprise mandated applications. The drawback is that you have to have Windows 10 with all its faults. Might be better to just start with Linux and run Windows from a VM image.
You can reimplement the code without violating copyright. You can't copyright the ideas of an implementation, only the implemenation itself. Oracle is trying to claim in a roundabout way that you can't make your own implementation. Since copyright doesn't do that, Oracle is abusing copyright law by claiming that you can't use the function declarations themselves without permission. Oracle is indeed doing the equivalent of saying you can't use the line "int round(float);" in your code without permission.
Slashdot Mirror
But you have to trust these odd startup companies with your cash. I don't trust them. Everyone's spying on everyone, and since they're startups the security is abysmally bad. Too many people are just far too trusting with new technology. A little bit of Luddite paranoia is a good thing.
What if you can't afford a phone? Smartphones are damn expensive.
It means that when you give your grandkids a few euros for Christmas, it's going to be a lot less impressive. "Hej, Anders, I deposited twenty euros into your phone, God Jul!"
I did spend cash when I was in Finland. It has many advantages that a credit card does not have. It intrinsically limits your spending (a good thing). It's fast, faster than a credit card in m experience. There is no hidden 2% fee to use cash. Pulling out a credit card for a $2 purchase is just silly in my view. There are things credit cards are good for also, but I wouldn't want them to 100% supplant cash.
The value is in the trust the general populace holds in the dollar. Same for other currencies. When trust is lost in some currencies then this can lead to massive inflation, something we've rarely seen in the USD. Cryptocurrencies have so extremely few users that I would so that the general populace trusts them.
Trust means more than "I trust that no one can steal my currency". It also means you can expect a reasonable level of stability in price, you can expect to be able to use it easily in your daily life, you don't have to convince a second party that your currency is good before you start a trade, and so forth. And cryptocurrencies are lacking in these. You can't walk down to the store and buy a loaf of bread with cryptocurrencies.
It is better that the dollar is not tied to the corresponding amount of gold, the economy greatly improved after these were untied from each other. The value is strengthened because we have a diverse economy with a very large population. This is similar to diversifying investments, a US state with a poor economy and one with a great economy all use the same dollar.
Development everywhere is a bit of a mess. It's just that some people mistakenly think that other successful companies are well organized. Ie, our own company's development may resemble the zoo's monkey house, but at least those big name companies know how to do things right... After all, they have thousands of developers, big buildings, free cornflakes in the morning, etc. Except that successful companies are also penny pinchers who don't hire as many people as they need (or outsource them) and have a slavish devotion to artificial deadlines.
I develop on the Mac, but not for the Mac or iOS, and not using xcode. We wait MONTHS before doing major upgrades, and weeks before minor upgrades. Apple is notorious for screwing things up. I'll do security patches but the updates always come with issues.
Having to update the day of a release is just silly, and if Apple is requiring this for certain domains (iOS 11) then that's bad to the point of making Microsoft look like a humanitarian organization. Though it does confirm my theory that Apple treats the Mac only as an iOS support system.
A patch rollback is not so easy on OSX. Just like with Windows, their world view is that no one ever rolls back. So, make a full backup before clicking the button that says there's an OS update.
It's probably just a bug. But Apple has not responded on this issue, there is no evidence that they're working on one. There are a whole lot of anonymous posters at DisplayLink forums who are bashing each other for being either Apple or DisplayLink shills. The longer that Apple ignores the issue the worse the blood feud is going to get.
That's part of the marketing. "Don't cause this baby to have died in vain, buy your new iPhone today!"
No, if the spec said it was supposed to be a wildcard, then someone should have strongly questioned this. Ie, a bug in the spec. A dev saying "I just follow orders" isn't a good excuse. That's like saying you're just a programmer and thinking isn't a part of the job.
You can pass two laws that disagree with each other. Then the courts get involved. Laws do not negate prior laws unless explicitly written that way. And most laws are written to be murky. That's just with normal legislated laws, there are also treaties have full force of law in the US as well, and the US constitution, which makes it all very complicated.
So you're very often going to get two different opinions on a law, both of which have a solid legal framework supporting those opinions. When there's serious money involved, someone's probably going to sue about it.
Sadly, in this age of lobbyists infesting the cracks in the capitol, every issue is a political issue being bought and sold. And the whips in the two major party make sure their legislators all line up exactly as they are told.
I dunno, I know a lot of workers who I'd describe as having a very low EQ which causes severe problems. As in the expert in a domain who loudly thinks he's the expert in every domain and has alienated everyone at the company who actively avoid meetings that he is in.
A UI needs an expert and specialist. Customers will see that front end, so you really don't want a novice being the one to design and implement it. A problem is that people want someone who knows what the current toolset/framework is, and will bypass people with lots of training and experience in UIs over someone who knows the tools the company uses.
I know many really smart people who lack experience. They make the same mistakes as novices. Sometimes it's worse because they know they're smart and will work on something beyond their abilities. Sometimes the company knows they're smart and have a PhD and promote them beyond their abilities as well.
In Finland, I met people surprised that foreigners would even want to learn Finnish. Nokia did most of it's business in English, even in Finland. They spoke better English in their McDonald's than they do in the US, the taxi drivers speak English, etc. In Europe, speaking a second language is a necessity of life.
I don't do any web stuff or mobile stuff. I do embedded software and in some ways that's full stack, everything from assembler to build to application. But there are things where you do want a specialist, like security.
I think many of these skills I mostly learned on my own. But I had a CS/CE background with graduate schools, and every class came in useful for background and foundation, knowledge that I could apply years later.
I doubt I will be out of a job, the skills are in high demand with low supply.
"Warning, this label may cause paper cuts, which has been shown to lead to sepsis in laboratory animals."
Just don't go anywhere called "A Cup of Moe".
If someone does come in to fix a problem, they should get an extra day off without it coming out of their vacation.
Sometimes I do come in, rarely, but that's usually because if I don't there will be giant headaches and extra work when I do show up. It's very very rare because everyone knows that it pisses people off to call them in at night or on the weekend, and if you piss off workers then you lose workers.
I don't even know who's calling me anyway, I don't know the boss' phone number and he's not in my contacts. There is sooooo much spam and robot calling now that I don't answer the phone anymore. If they leave a voice message that isn't spam then I'll call back. The modern telephone is now useless for phone calls because of this.
And even if I did have my boss's number show up on caller ID, I could still just claim I didn't know who it was. Time outside of work is MY time.
Hire extra workers for the night shift then. You can't legally force people to work 24 hours a day in the US, and being on call is essentially working for 24 hours. The companies are abusing the workers here and they need to stand up for their rights.
Also, as the article mentions UK workers, they already have lots of workers rights. Often you'll get a security guard upset if you are staying at the office late as it can annoy the unions. If they asked the same question in the US, I suspect there would be more who would take the call, and so many work long hours anyway as they've been brainwashed to think that this is "normal in the industry".
Back in early 2000s, the solution was to have two computers at my desk. One for doing work, and the other for Outlook or the occasional Word document. Just swivel in the chair to multitask.
Except that once you have Linux, why would anyone want to use Visual Studio?
It sounds like this might be a reasonable alternative to OSX, which is Unix along with being Office compatible, so that you get a convenient development environment but can still use the crappy enterprise mandated applications. The drawback is that you have to have Windows 10 with all its faults. Might be better to just start with Linux and run Windows from a VM image.
Oh sheesh, who core dumped all over the carpet?
You can reimplement the code without violating copyright. You can't copyright the ideas of an implementation, only the implemenation itself. Oracle is trying to claim in a roundabout way that you can't make your own implementation. Since copyright doesn't do that, Oracle is abusing copyright law by claiming that you can't use the function declarations themselves without permission. Oracle is indeed doing the equivalent of saying you can't use the line "int round(float);" in your code without permission.