A simple Google search could help you resolve these inquiries in the future.
419 karma · joined April 14, 2012
chill[at]degreesofzero.com
A simple Google search could help you resolve these inquiries in the future.
Seems highly unlikely that the situation this person described would result from anything other than dropbox being compromised in some way.
I think you meant "Having an unrealistic ..."
Outstanding. Made me smile. I appreciate the level of grandeur you are attempting to bring to bear on this discussion, but this is a discussion about Game Development by the way.
I suggest you not take all of this so personally.
Have you read the lecture that okal posted the link to? It's from the early 1970's and speaks to the early days of when abstractions were first being implemented for computers in general. Perhaps it is you who does not understand what abstraction means.
I still think it's helpful from time to time to think a bit deeper about the details of what's actually happening below the top couple layers of abstraction, though :)
To me, the OP's post is clearly a cry for help, guidance, a "wtf do I do next?"
Been there.. You know what you need to do? Treat life itself like a video game. Win. Stop what you're doing right now. Think really hard about what winning would be for YOU. Write that down on a piece of paper. Done? Good.. now figure out how to get there.
I, too, had a great affection, possibly obsession, with video games at a similar point in my life. I had these grand ideas for video games that I'd like to play, but didn't exist yet. So, I started figuring out what it would take to make them. Now, roughly 6 years later, I'm not in game development, but I am building complex web applications and doing a lot of very interesting things. And, you know what? I'm happy.
You have the drive. Make happiness happen. Don't wait for it to come to you.
I commend whoever reported this to the authorities. People who drive drunk are disgraceful human beings. You are not so important or special that you can endanger the lives of your fellow humans for no other reason than you are incapable of self control.
And yes, he was arrested not simply for posting the message. He was arrested because the police went to investigate, after receiving the tip, and discovered that his car matched the evidence from a reported hit-n-run from the same evening.
Well, anyways... I checked out the first game in the article's list of "great" HTML5 games (Contre Jour: http://www.contrejour.ie/#fbid=N0F1LHvfzzM). It was pretty good. Seemed to have relatively unique, interesting game mechanics, nice visuals, and I liked the music.
I will have to remember to check back in on this, to see what everyone came up with.
If you have to use a knife to kill someone, you are going to have to get very close to them to do it. You're going to have to be very aware of what you're doing. With a gun.. not so much.
Foreign and imaginary.
Often times programmers and the managers that drive them are way too quick to get going building or solving something with brute force. If they would just be patient and stop for a moment. Spending even a mere 30 minutes extra doing your homework on a problem can save hours or days in dev time.
Are you using Git for your source control? If so, you may want to start a new branch and work in it before doing any major re-factoring.
To start, I would try to find a small part of the application that you feel would be possible to re-factor in an hour or so. Before changing anything, I would load up the app locally in your browser and navigate to the portion that is dependent upon the code you're going to re-factor. Then I would re-factor things in as small a chunk as possible, constantly checking in the browser to make sure things still work properly. This is a rather bastardized approach to test driven development, but it can be quick and effective.
> The architecture of it all is very monolithic; based on our plans for the future business development, quite a few parts should be decoupled and made more independent of each other.
As a side note.. This type of thing I have seen way too much of in my time in the industry. It's very easy to get carried away and over-engineer a solution. I've found it's best to create a solution that solves only the problems you currently need solved. It's always easier to go back and extend while re-factoring than it is to try to re-factor a giant-freakin'-thing after the fact.
Why I like these words: It's not enough to be able to write code, or even to package up a module for a framework. Knowing that you can't do everything, and that you should not try to do everything, with a single module, is a promising sign in and of itself. Having a clear goal to reach makes getting there all the more possible.