Prayer != Meditation except for very narrow and atypical interpretations of both words.
MSDN lets you download software to develop and test against. I need to test some Microsoft software on various cloud providers. But before I do, I think I'll take a peek at my license agreements: http://msdn.microsoft.com/en-u...
"Qualified MSDN Cloud Partners. To run software on third party shared servers you must:"
Does your company / marketing dept. want to put a Windows Logo on your product? Check your license, you might have to dumb down your Android or iOS version to get it approved.
It goes on, and on... Yes, most companies ignore these, but they are still in the agreements. At its heart, Microsoft hasn't changed yet.
Or just use: https://s3.amazonaws.com/s3.do...
Seconded. Brother was my last pick based on lots of reviews, I wanted a B&W laser with duplexer, page feeder, scanner, fax over Ethernet for Windows and Linux in SOHO setting - got MFC 8480DN. Extremely happy with this printer, reminds me of how HP used to build.
While I won't argue about the convenience of Netflix (for movies and shows that appear there, once they do do appear), since I don't spend a great deal of time watching TV, its more practical for me to take my money that would otherwise go to Cable and/or Netflix and buy movies and TV shows on DVD or BD. That way, while the fine print does state that I'm only licensed to use the "video device" for personal non-commercial private viewing, I do have a growing library of insured high quality digital copies I may watch immediately anytime I want that cannot be revoked or disappear in an annual licensing negotiation, nor count against the steadily more constrained bandwidth available in most of the US. And someday when the courts uphold that the DMCA anti-circumvention clause may no longer invalidate the "space shifting" precedent, I'll be able to legally rip it all and have a legal mobile digital library of same content. (I know, I can dream...)
Yes, but manufacturing processes are often also obtainable documents. Any company who has set up good process control around their manufacturing lines has probably documented almost if not everything needed to recreate their subset of the secret sauce. Due to subcontracting these constitute a more distributed set of targets, and probably have local IT staff better capable of locking down their small networks than a megacorp oursourcing model would, but its probably all still there...
Having spent about 10% of my career in embedded, I would agree that domain knowledge is of far higher importance in the embedded world. The knowledge base for tool chains and platforms needed to write production quality code on most embedded platforms is significantly than most desktop / server / web app worlds...
Writing as someone coding professionally since the early 80s, in project teams sizes from 3 to 10k, and at the highest primarily engineering position I can achieve without becoming a non-coding manager (Systems Architect)...
As engineers age, they may gain experience, but productivity does often drop. We also have those pesky families and/or work-life balance goals. And an unfortunately repeating pattern for engineers is reaching a point where they now think they know everything they need to, and learning grinds down, sometimes to nothing. If they only work on legacy code that might be OK if no innovation is required. Domain knowledge is difficult to quantify the value of, and varies greatly by organization and project, and I would argue that all seniors should work hard at making sure this is clearly documented AND passed down.
Most companies are happy to keep a few older experienced engineers around to try and direct teams of young high productivity programmers (no family / life, willing to work 60-100 hour weeks) and attempt to mentor them to make less mistakes. Increasingly these teams are in low cost regions, most commonly India.
I would begrudgingly agree that in most cases, in terms of a cost / benefit analysis of 'value to the organization / stockholder', which is what really matters, this is true a statistically significant percentage of the time.
Of course, most of the time comments like this are merely the result of a HR directive to cull expensive engineers to reduce payroll and make room for more low cost region 'resources', driven by a suit that doesn't understand the full value of their older engineers. Unfortunately we live in a world where most important decisions are made by MBAs without a clue. Older engineers must learn to make sure the layers above them understand their real value to the organization.
I would imagine that if this evolves it will end up having constraints attached to it along the lines of the prohibitions on retransmitting or relaying information from other protected radio frequencies. While there are useful reasons to translate and distribute general flight tracking information, I'd be willing to bet that either these services are forced to omit law enforcement transponders altogether, or there will be automated gag orders on such sites regarding to drones under certain circumstances such as pending activity (selective availability on drone tracking data?)
In any case, I would imagine that if you want accurate local drone data you'll have to collect it yourself.
As others have now posted this is possible on the cheap: RTL-SDR software over DVB-T dongles based on Realtek RTL2832U (supposedly as cheap as $20) provide a receiver, and GNU Radio with gr-air-modes gives you decoded ADS-B data streams on a decent PC.
If domestic drones will be allowed in domestic civilian airspace as long as they carry active ADS-B transponders, then there are a number of receiver+software packages that would enable them to be tracked by anyone with some tech skills.
Google "ADS-B receiver", one example: http://www.scannermaster.com/ProductDetails.asp?ProductCode=28-661518
I read the linked paper, and while interesting, it typifies one of the critical flaws in the extreme Libertarian model - there are a set of cases where for-profit private enterprise is a bad solution, such as where it is not practical to provide an reasonably large number of easements to setup competing infrastructures. Where constraints exist that facilitate natural monopolies, history has shown that it IS in the public interest to preclude predatory practices, as unchecked for-profit private enterprise will always seek maximum return on investment, leading to predatory practices. While it is true that modern government bureaucracies have demonstrated themselves to be extremely inefficient managers of infrastructure, they are arguably better than an unchecked predatory monopoly. Legal mechanisms like the Sherman Antitrust Act, while anathema to an extreme Libertarian, have proven highly valuable in the past. And circling back to the original point, given the critical nature of roads, and the time period required to execute a a negative feedback cycle through the legal system, I personally believe that unfettered privatization of all roads would be a good way to grind a modern civilization to its knees.
I understand the argument, and frankly I agree. However, given the political nature of the non private space programs, I also believe that other than a real push to Mars, the US program is destined to remain like the Shuttle and ISS - little more than jobs and pork delivery. Think of how little science has been accomplished by STS and ISS programs, and few actually reusable components other than the STS RS-25 and SRB, which are still restricted to US government program use.
If we fund a moon base or Lagrangian station, we're basically out of public money for space and stuck on this rock.
Going to Mars will not only inspire people again, it gives us somewhere we shortly place self-sufficient humans to live, which is far more important long term to the species. Publicly fund a Mars Mission and private money will quickly follow you there. You want a 'space faring society', Space X is a better program to orbit, Bigelow has something interesting to put there, and programs like VASIMR are exploring how to move us out further.
Anyone who thinks this is a good idea to get to Mars needs to read Zubrin's "The Case for Mars" or read up on the "Mars Direct" approach. All this talk about moon bases or staging in orbit or at an Lagrangian point originates in NASA designing the Mars mission via lots of committees, in which various teams and [sub]contractors got to insert dependency on their pet projects. Mars Direct presents a very well thought out and fully vetted approach, nothing but politics at this point is standing in the way - if NASA as an agency was still primarily interested in space exploration instead of pork disbursement and fiefdom preservation, and Congress had to provide slightly longer term budget commitments with less constraints and strings atached, we'd already have a permanent presence on Mars.
The modern American Software start-up business model is simple - rush to market, and hope to either: 1) Be acquired by someone with a large enough patent portfolio to provide defensive cover, or 2) become highly profitable quick enough that you can afford to defend yourself by the time a predator notices you.
Note that #2 is becoming more difficult as the big patent predators like Intellectual Ventures are moving their way down the food chain, hoping to capture a larger share of start-up capital before companies die due to market pressures.
Left unchecked, the current patent system has begun the end game of grinding small companies and start-ups into the dust, and with them most of the innovation (and jobs) that used to occur. Apple v Everyone was just the first really big play, while IV tries to remain under the radar while tuning a process intended to eat most of the small fish before anyone realizes the pond is almost empty.
Wonder what Thomas Jefferson would think of the monster he helped create...