rajat

The description says that this GUI is based on the rendering algorithm of Clay. What, exactly, is Clay, in this context?

Redox.

Probably worth doing regardless of brouhaha or not. Different design choices, etc!

Lifting weights, kettlebells. Very important to do face pulls, in my opinion, given how much time we spent at a desk and over a computer.

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.

The JetBrains IDEs are implemented using Java. Is there Java available for iOS?

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.

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.

That's why they want a union. Raise the minimum wage and reduce or eliminate the risk of the job being eliminated.

I second this. I'm beginning to hear more an more of this problem, and while this is anecdotal, it does seem to be increasing.

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)?