beer. Back to my beer.
beer. Back to my beer.
$ git --version
git version 2.6.3
$ brew update
$ brew upgrade git
$ git --version
git version 2.8.1
Back to my
I read the bill. Disclosure of security threats is completely VOLUNTARY for individuals, private companies, local/state governments, utilities, etc. ("non-Federal entities"). There is no mandate. There are no demands for back doors. There is no provision for unfettered sharing of network traffic, only a mechanism for voluntary sharing of information about detected threats. Even then, they must be careful to strip away any unrelated personal information.
I'm a BIG believer in personal privacy and 4th Amendment protections, but I'm a little disappointed by the "Chicken Little" rhetoric about this bill compared to what is actually contains.
Tax breaks by local or state governments to win construction projects NEVER make sense, and should be outlawed as a form of unfair treatment under the law.
Small businesses hire FAR more employees and put FAR more back into the local economy than large companies who have the political clout to win abatements. Every tax abatement won by a company deciding to do business somewhere is an effective tax INCREASE on every other business and resident of that jurisdiction.
When a company moves into town, they are taking advantage of the roads, sewers, fire and police protection, schools, and other appurtenance of civilization, and they should pay their fair share for that infrastructure.
Speaking specifically about data centers -- they hire relatively few people, take up a large land mass, add stress to the local electrical grid, create buildings that drive down surrounding land values (who wants to live next to a windowless building with huge air conditioners?), etc. etc.
I'm not saying they are "bad" neighbors, but they certainly don't deserve a ticker tape parade, and they should pay their fair taxes like anyone else.
Well said. And while I agree it shouldn't have been done, I'm significantly LESS concerned with the *government* looking at *government* computers used by *government* employees than I am with the government spying on people without probable cause who are *not* their employees and on computers that they do *not* own.
One corollary of Metcalfe's Law is that, since most people are cheap, it is difficult to create suitable network effects based solely on users who are willing to pay a fee to participate.
I would pay for an ad-free, censorship-free Facebook-style service, but most of my friends and family wouldn't.
I took COBOL -- late 90's.
The one job interview I went on where I could put that skill to use showed me why I *wouldn't* want such a job.
The issue wasn't the language per se, it was the fact that most companies still using COBOL are also trapped in chronically underfunded and undervalued IT departments, holding old machines and apps together with bailing wire and duct tape.
Congresscritters and the bureaucrats who make the decisions are completely incapable of understanding transmission rates and why 4 vs. 10 matters in the real world.
Instead, we should just tell them that any definition of "broadband" should at *least* pass the smell test of meeting the recommendations for Netflix's service, which is 5Mbps for HD and 25Mbps for Ultra HD.
A Netflix stream of course isn't a standard unit of measure, but it's at least an analogy they might understand.
This is one of the most comfy chairs I own, reproductions are affordable, and they are gorgeous. The recline is comfortable while still allowing non-desk work (the Eames is *too* reclined for my taste), the arms are wide enough to curl up in, and the back is high enough to support your head. Many reproductions allow adjusting the recline tension.
You'll need to supply your own power and a stand for the laptop.
1. Integrate the documentation with the application. Treat it like code rather than as a separate document.
2. When new features are proposed, plan them by FIRST forking and changing the documentation, THEN implement the change based on the change in the story. This not only guarantees good documentation, it ensures the developers are all on the same page about what the changes should/shouldn't do.
3. Focus documentation on the common tasks, software limitations, and side-effects. Far too much documentation wastes reams of paper telling people "to create a new widget, click the New button." If the "New button" is hard to find, difficult to click, or does something other than creating a new widget, that is a failure of the UI, not the documentation.
In my experience, the word "Enterprise" usually means a shitty piece of uselessly generic and hopelessly complex software combined with an expensive consultant team who spend 5% of their time configuring/using the software as intended and 95% of their time hacking around its limitations by glomming on little "tumor" systems to shoehorn it into your business.
But I admit I'm a little jaded.
I love C#. I program in it every day. It's plenty fast, and it's a great language.
However, there are two reasons I would suggest looking to another language.
First, the hottest market for gaming right now is mobile. While it's possible to compile C# for iPhone or Android using Xamarin (along with Windows and OS X), it's not exactly a native experience.
Second, C# (like O-C, C++, etc.) is a general programming language -- it's not in any way specific to the domain of game programming. So, while it's *possible* to design complex games in any modern language, you're probably going to spend *way* too much time dealing with silly stuff like tracking graphics resources and animation loops and simulated physics. You'll have a higher chance of success if you use a language and platform that is more game-specific out of the box.
I would suggest looking into Swift -- it'll give you access to the lucrative iOS market, it's C-like, and it has features that are game-specific. Sure, it's a new language it doesn't compile to Android, but by all accounts it looks like a great language with first-class support for gaming, so you can focus less on infrastructure code and more on the game.
An Samsung Galaxy S3 is almost $600 unlocked as well.
Instead, Apple should SQUASH the black market by making it easy for customers to report a device stolen. Once reported stolen, Apple should brick the phone remotely and contact the service provider to have the IMEI blacklisted.
AT&T and TMobile just started blocking blacklisted IMEIs last month. As other carriers follow suit and companies like Apple make it easier for the average consumer to make the report, thieves will eventually learn that the devices are worthless.
If you don't have a lawyer, get one.
People actually do go to school to learn how to wrangle with international corporations, torts, contracts, etc., and the vast, vast majority of the good ones don't program on the side, or if they did, would give legal advice on an Internet forum.
This makes as little sense in the modern age as those "virtual reality" helmets we're all supposed to be using by now.
Companies like Leap are making much more advanced technology that requires nothing attached to your hand and uses motion sensors to track your hand movements with incredible precision. Comparatively, this guy's mouse-finger contraption looks as silly as Doc's brain-wave reader in BttF.
(I don't represent Leap, I just remember hearing about their tech awhile back.)
The truth of a proposition has nothing to do with its credibility. And vice versa.