1. Yes, the approach is right. You don't need to start a company, particularly if the project could be open source. Even talking about the project in local meetups (assuming there are meetups by the time you are ready to talk about the project) can also help.
2. Do you need to quit working? At least, do you need to quit working immediately to start on the project? Wait until you have something concrete. Work in your "garage" until it's absolutely essential that you quit your current job.
It does seem obvious that short of having your own copy of something purchased (in this case, a movie), this will happen. Purchasing the right to see a movie, listen to a song, on a service, will never be the same as holding a physical copy. I wonder if it's even legal for Apple to maintain a copy of the movie in iTunes for customers who've already purchased it once they have lost the right to host it. Clearly, most of us don't appreciate the difference between what it meant to purchase something, and what it means today in the digital, subscription world.
So, if you really want to own a movie or a song, buy a physical incarnation of it, or make a digital copy of it.
All too often premature optimization is brought up as the antidote to carefully think about what you're implementing prior to actually opening up the IDE and start coding tests madly.
Thinking is hard, and takes time, and we want to get the feature out now, immediately, and worry about performance later. If at all.
And, sad to say (for an engineer), it's not clear that from a "business" perspective it's wrong. Hard to argue when accumulating features seems to matter more than crappy software. We have a lot more software these days, to run all of these bright new pieces of hardware, and perhaps because I'm an old-timer, the general quality seems to have degraded significantly. But the novelty of the stuff certainly has exploded, and I'm continually delighted by the twists and features that folks are coming up with, while being saddened by crashes, slowdowns, need for restarting, etc.
At least one form of Roman concrete was better than anything we moderns had been able to come up with until we rediscovered the formula a few years ago.
What do you do today about parents who sell their food stamps for liquor or other drugs?
This is, of course, the huge problem with this plan. Not that this isn't the right thing to do; but because the media and public will seize on the few morons who do stupid things and therefore malign a program that would actually help most.
Just imagine the headlines: Addicts Caught Buying Crack With Your Money.
It doesn't matter which party pushes it. If the Democrats pass it, the Republicans will scream about this; if the Republicans do, then the Democrats will scream how this justifies government as a warden.
Basically, if you accept that your first 10 games will suck, and you don't try to make your first game fantastic, then your first 10 games will suck. Worse, you might get good at developing sucky games. For most developers, not just game developers, it's likely that their first some number of projects will suck.
I always thought that the mantra about your first 10 games will suck was a way to take the pressure off you and get you to develop a game. The problem is that we psych ourselves out; we don't develop anything because we're too fearful about making a bad game, and we procrastinate, and we hem and haw and never develop anything.
I am curious: are documents in Google Sheet scanned by Google's software bots to determine stuff about me? I can't seem to find a Privacy Policy document specific to documents in Google docs. How about if I pay for the service (can I pay for the service)?
Because you'll come out of the experience a MUCH better programmer; MUCH, MUCH better. In fact, until you've written a low level device driver and understood the complexities involved, you cannot really understand how much better a programmer you can be.
1) You get better because you learn to manage complexities that are simply not found in MOST application level programs; exceptions are stuff like high-performance database servers and their ilk. You should come out with a really good understanding of how to write multithreaded code, for example;
2) You learn to manage a really big project with lots of related, but complex interconnections;
3) There really is a huge benefit from learning just how a system works at the low-level in becoming a master programmer. Things like cache-issues, virtual memory management, are topics that you may not use everyday, but knowledge of how and what goes on gives you a whole new level of insight.
Anyone who wants to become a master programmer should implement a toy operating system (we can't all be Linus) and a toy compiler. Even better, implement a compiler and then implement the operating system using that compiler.
And the final reason: because it's amazing FUN. That is, if you really like programming. It's so complex, so much hard work and hard thinking, that when your first application program, just Hello World, actually runs to completion, you get high.
I use Apple's Numbers to track weight, blood pressure, intensity of workout (number of meters rowed, time, number of push-ups and pull-ups).
I have tried apps from time to time but nothing gives me the flexibility of a simple spreadsheet. For example, I can add notes to explain odd circumstances (ie. indulged in drinking, slept late, etc.)
Since you're comparing gun crimes to all crimes, doesn't that mean that non-gun crime rates are also falling lower than crime in general (includes with or without firearms)?
Public perception is being driven by a media with an anti-gun agenda.
I have 2 27" monitors (an iMac and an Apple display) next to each other, and it's fantastic for programming. One display has Xcode using up almost all of the screen; the other display has Safari showing documentation and other reference documents. What would make it ideal is a usable keyboard with a usable trackpad built into it, like the laptops do; moving my hand to use the separate trackpad is just as irritating as using a mouse.
I use a standing desk, and find that I am far enough away from the monitors that head movement is not an issue; moving the pointer can be but you can increase the tracking speed setting to make that a non-issue.
What I am considering switching to is using the display attached to my laptop. Xcode would be on the laptop screen and the display would be used for showing reference material.
How does he get to use those logos before he paid for them? Sounds like multiple copyright violations per contest to me. I understanding that the artist may not be in a position to legally contest anything, but it's clearly unethical.
This is what's in 99Designs faq:
"On 99designs, designers agree to upload only original artwork, so each designer owns the rights to their design submissions.
This is true until the contest holder chooses one of the designs as the contest’s winner. Then, and only then, can the designer agree to transfer his or her rights to that particular design to the contest holder."