131–140 of 145 posts
[2] http://lifehacker.com/281626/jerry-seinfelds-productivity-se...
Like others here, if I lose steam on one, I switch to another. The novelty effect is real. To support switching though I have to use a notebook. As I get to the point where a project is feeling more drag than energizing, I write down everything about it that I have in my head at that point into my notebook. Then I find another project I had left in that state, read the page(s) on it, and spin it up. Still, my biggest…
This is good advice, and I agree! Anything larger than a small project will need to be put aside for a while from time to time (for whatever reason), and I've found that making it easy to pick it up again is one of the most important things you can do. My strategy for this (admittedly most suitable for software projects): 1) Write down your large, fantastic vision for the finished, complete project. 2) Write down the…
What is MVP or BDD? Could you provide an example of your process?
Would it be similar to this example? 1. I want to put out a rpg for iOS. 2. Implement a pokemon style battle system -> when health < 0, NPC dies. 3. Not sure where automation fits in? 4. Code it and test until it works. 5. Move on to adding experience when killing an enemy, etc.
Earlier quoted context omitted.
"I turned my side project into a unicorn job. It only took about 10 years of hard work...but I did it the hard way." Sounds fascinating. Could you give more details? What was your sideproject? What did you do to turn it into a unicorn job? Thanks in advance.
Yes, as user "scroy" points out I am talking about Voxel Quest. Bits and pieces of my story are scattered around, but here is the full thing (grab a pillow): In around 2000-2004, I was working several jobs while attending UCSB, as a gardener, a lab monitor, and a freelance web designer. I got by working the first couple years but the last year was hard and I was disqualified from engineering. I wanted to quit school…
Earlier quoted context omitted.
This is good advice, and I agree! Anything larger than a small project will need to be put aside for a while from time to time (for whatever reason), and I've found that making it easy to pick it up again is one of the most important things you can do. My strategy for this (admittedly most suitable for software projects): 1) Write down your large, fantastic vision for the finished, complete project. 2) Write down the…
I'm a bit confused by this approach. Is it related to some established design approach or principles? What is MVP or BDD? Could you provide an example of your process? Would it be similar to this example? 1. I want to put out a rpg for iOS. 2. Implement a pokemon style battle system -> when health < 0, NPC dies. 3. Not sure where automation fits in? 4. Code it and test until it works. 5. Move on to adding experience…
MVP occurs a lot on Hacker News, in that context meaning Minimum Viable Product, or the least amount of work you must do to make it useful for users/customers.
BDD in the software context means Behaviour-Driven Design and is an opinionated way of writing tests.
With regards to step 3 in your example: Sometimes it can be challenging to design automated tests for certain functionality.
For a game, it could be scripting "fake" user input that is supposed to have a certain end result, and then verify that that end result actually occurred. E.g., the player makes a few good moves, then a few bad moves that should cause health to drop below 0, then check that the player actually died.
Automated tests are a life saver, and often it pays off in the end to learn how to write them for almost any functional requirement.
I hope I answered your questions!
Earlier quoted context omitted.
Thank you :) (recognize the username) Both of these are things that I (massively) failed to address early on and am actually now striving towards. I'm actually pretty happy at this point. If my wage were raised just slightly, and the threat of running out of (non-investor) money was not looming, I would be 100 percent happy. Wouldn't take millions, but nonetheless its good to aim high. :) Currently working on putting…
The project is really impressive, you have some truly beautiful examples in the gallery. I see what you mean that user content creation doesn't seem easily accessible enough to hit Minecraft's level of self-marketing. But there is tremendous potential I think once you reach a more fleshed-out demo. Hope to see that soon.
Earlier quoted context omitted.
Yes, as user "scroy" points out I am talking about Voxel Quest. Bits and pieces of my story are scattered around, but here is the full thing (grab a pillow): In around 2000-2004, I was working several jobs while attending UCSB, as a gardener, a lab monitor, and a freelance web designer. I got by working the first couple years but the last year was hard and I was disqualified from engineering. I wanted to quit school…
Looks quite impressive, but I was wondering what language do you use to build your Voxel Engine? And the motivation for such a choice? Looking forward to your feedback.
Earlier quoted context omitted.
Yes, as user "scroy" points out I am talking about Voxel Quest. Bits and pieces of my story are scattered around, but here is the full thing (grab a pillow): In around 2000-2004, I was working several jobs while attending UCSB, as a gardener, a lab monitor, and a freelance web designer. I got by working the first couple years but the last year was hard and I was disqualified from engineering. I wanted to quit school…
Hey, I'm interested in what you mean by "reprogramming" your life. I'm kinda of in a similar boat and looking for advice etc...
Treat your life like an imperative programming language. Determine your goal, and start breaking it down into the simplest steps to achieve that goal. Many time you can simply replicate the steps others have taken (this does not mean exactly). Nothing will change until you start making the changes. Find everything you dislike in your life and determine a way out of it. There are certain things you can't do (not everyone can be an NBA star), but there are a multitude of other options. Also, be shameless. It is ok to depend on other people, promote your work, ask for favors (just don't spam). 99 percent of the time you will be rejected but don't be disheartened. More than anything else, develop some skill towards perfection so that you are less likely to be rejected. Alternately (or at minimum, in addition), find out how to market the hell out of yourself and your work. This does not mean buying ads, it means capturing minds. Find people who are better than you and take genuine interest in their work, and strive to make your work as good as theirs (they will take interest, and others will by association). Be honest in everything you do, dishonesty can destroy your future chances at anything. Be genuine, don't try to sell something you are not interested in. Don't get caught up in your own made-up principles, do the things that are proven to work.
There is no easy or guaranteed path to success, but every failure tempers you against future failures. Most successful people go for years before they produce anything successful (a common number seems to be around 8-10 years). People, like me, will say to do XYZ, but in the end even going against common advice can make you successful. Listen to everyone's advice, but weigh it against your own instinct.
Much of the advice people gave me I ignored, and it worked out for the better. This does not mean to act like you are smarter than everyone else - listen to what everyone has to say, it may help you as well.
I view my side projects as the main work, and anything else as merely a way of supporting them. Also, I have enough side projects that if I lose interest in one I can switch to another.
I do the same but I feel like a fraud for not putting my full loyalty, energy and passion in the company I'm working at.
Only reason you should ever feel guilty is if your side projects are meant to directly compete with the work you do at work. In that case, I would say it's a bit unethical.
Perhaps a better (or at least related) question is: how does one find the time to put into side projects on top of staying competitive as a programmer in an environment where 45-55 hour weeks are customary and expected, and also achieve some kind of work/life balance involving significant others and children? I challenge anyone to show that the math for this works out. Everyone I know who has put effective effort int…