I remember some goofy ways installers would try to trick users into toolbars, including double negatives: "Do you not want to not install the Foo toolbar?" or "Skip the bypass of the Foo toolbar installation?".
When you send to somebody else, they also have a copy, which may end up saved, archived, forwarded, etc. Unless you are confident you can control all copies of all recipients, it's not realistic to assume one can control and delete all copies of sent content. If you miss enough, then you are caught hiding stuff. The conspiracy angle makes very little sense. More likely she never really gave the issue enough thought. That's still a "bad" thing, but one should probably invoke Hanlon's Razor.
If such worries cause more local buying, then it may not necessarily be a net loss in local sales, because purchases that would otherwise be from outside sources are done within the country. Reduced trade is not necessarily reduced total sales.
Embedding trojans into the software updates is still a potential risk that is probably on or near the same order of magnitude of likelihood as online hacking.
Not really, it depends on the person. Some value things like a window office, kudos (such as "developer of the month"), flexible work hours, a better parking space, "gamer breaks", etc. above more money (if forced to choose).
As a manager find out what each individual really values. If you have too little control over money, then try to use other "soft" rewards.
Slashdot - news for nerds, "got bought by dice.com"
I used to work for a "dot-com" startup, and getting bought out was considered a plus: founders get big bucks and some other shmuck gets the worries of making the contraption actually fly (i.e. profitable).
I actually tried a few startups on my own, some even semi-promising, but with a new family, I realized I needed a day-job to pay the bills and couldn't wait around waiting for such to grow big enough to sustain us.
Some lessons:
1. K.I.S.S. - Don't get feature-happy up front. Make "hooks" for planned additions if you want, but don't get carried away. 2. Low overhead - Don't buy junk you don't really need 3. Be adaptable - You will learn about the niche(s) as you go and will need to change to adjust to the knowledge 4. Have a Plan B. You may fail. 5. Keep the service super-cheep or free to attract customers at first. Few will pay top dollar for a new service.
It's one of the most influential early interactive digital video games. Atari got started with a clone of it. (Outside of colleges, users found it confusing, but the experience gave Atari a head start.) It also influenced Asteroids, which it has a lot of resemblance to.
One industry likely to suffer is that of auto insurance. Since the vast majority of auto accidents are caused by human error, having more autonomous vehicles on the road will almost assuredly result in fewer overall accidents...
While "traditional" accidents may go down, new kinds of threats go up, such as hacking risk.
"Mom, why we are going to Albuquerque, especially since the bridge is down that connects th.....aaaaaahhhhHHHH!"
If the poor could easily sell their kidneys for their family's benefit upon death, then the rest could afford them. Pay them up front even for the "rights". This is for those of you who worry about your family whacking you for profit.
Slashdot Mirror
Now I got the Foo toolbar AND the Puppy toolbar.
Yeah, but THIS looks more like real work:
Nobody will feel like paying you big bucks unless it looks hard to do.
We accept the coding challenge, what was the task exactly? Bring it on!
One thing I miss from PHP is optional named parameters. There are work-arounds to emulate them, but they are clunky. C#/VB.net does them fairly well.
https://www.youtube.com/watch?...
I remember some goofy ways installers would try to trick users into toolbars, including double negatives: "Do you not want to not install the Foo toolbar?" or "Skip the bypass of the Foo toolbar installation?".
Guilty until proven innocent?
When you send to somebody else, they also have a copy, which may end up saved, archived, forwarded, etc. Unless you are confident you can control all copies of all recipients, it's not realistic to assume one can control and delete all copies of sent content. If you miss enough, then you are caught hiding stuff. The conspiracy angle makes very little sense. More likely she never really gave the issue enough thought. That's still a "bad" thing, but one should probably invoke Hanlon's Razor.
If such worries cause more local buying, then it may not necessarily be a net loss in local sales, because purchases that would otherwise be from outside sources are done within the country. Reduced trade is not necessarily reduced total sales.
Ironically, her own server appears to have been more reliable than the gov't server she was allegedly supposed to use.
Seems the Roswell aliens had the same problem.
German hands caught in the cookie jar:
http://www.nytimes.com/2015/05...
http://www.spiegel.de/internat...
But what country that manufactures such equipment is likely free of similar problems? Where are the customers going instead?
Practical example? And what % of applications need such "tight" concurrency beyond the over-used example of online interactive texting?
I can picture you as a boss whacking your employees with a rolled-up newspaper: "Bad employee, bad bad bad employee!"
1. Get me pizza
2. Get me a beer
3. Suck my dick
Embedding trojans into the software updates is still a potential risk that is probably on or near the same order of magnitude of likelihood as online hacking.
Not really, it depends on the person. Some value things like a window office, kudos (such as "developer of the month"), flexible work hours, a better parking space, "gamer breaks", etc. above more money (if forced to choose).
As a manager find out what each individual really values. If you have too little control over money, then try to use other "soft" rewards.
I used to work for a "dot-com" startup, and getting bought out was considered a plus: founders get big bucks and some other shmuck gets the worries of making the contraption actually fly (i.e. profitable).
I actually tried a few startups on my own, some even semi-promising, but with a new family, I realized I needed a day-job to pay the bills and couldn't wait around waiting for such to grow big enough to sustain us.
Some lessons:
1. K.I.S.S. - Don't get feature-happy up front. Make "hooks" for planned additions if you want, but don't get carried away.
2. Low overhead - Don't buy junk you don't really need
3. Be adaptable - You will learn about the niche(s) as you go and will need to change to adjust to the knowledge
4. Have a Plan B. You may fail.
5. Keep the service super-cheep or free to attract customers at first. Few will pay top dollar for a new service.
Kind of like Comcast.
What about Spacewar!?
It's one of the most influential early interactive digital video games. Atari got started with a clone of it. (Outside of colleges, users found it confusing, but the experience gave Atari a head start.) It also influenced Asteroids, which it has a lot of resemblance to.
I'm creating the Flat-A-Tron to sell to the New England Patriots
While "traditional" accidents may go down, new kinds of threats go up, such as hacking risk.
"Mom, why we are going to Albuquerque, especially since the bridge is down that connects th.....aaaaaahhhhHHHH!"
If the poor could easily sell their kidneys for their family's benefit upon death, then the rest could afford them. Pay them up front even for the "rights". This is for those of you who worry about your family whacking you for profit.
Because God didn't create us for desk jobs. Sue him!
Derby burgers, yum!