"When you are young, beginning new projects is easy and finishing them is hard. As you grow older, beginnings get harder, but finishing gets easier. At least, that has been my experience. I think it is true of anyone of at least average intelligence, creativity and emotional resilience. The reason is simple.
When you are young, the possibilities ahead of you, and the time available to explore them, seem nearly infinite. When you try to start something, the energizing creative phase, (which comes with internal brain-chemistry rewards on a fast feedback-loop), gives way to exhausting detail-oriented work, maintenance work, and unsatisfying overhead work. You need to get through these to bank distant external rewards (money and such) that only come with completion. It is then that you are most vulnerable to the allure of exciting new beginnings. So you abandon things halfway. You bank the internal rewards of beginning, but not the external rewards of finishing.
But with age, this changes.
As you grow older, the history of a few completed projects and many abandoned ones in your past starts to loom oppressively in your memory. The early internal rewards of many beginnings are now a distant memory that offer no pleasure in the present. The external rewards of completed projects, which tend to continue to yield dividends (such as completed degrees, financial rewards) loom larger all around you: wealth, strong relationships and perhaps most importantly, an earned ability to see the world differently as the result of having been through many completions.
When a new opportunity opens up at 35, you evaluate it differently than you did at 25. You are able to estimate how long it will take, what the journey will feel like, what the early pleasure and distant pain will feel like, and what getting it done will feel like. You are able to react psychologically to the whole prospect in the form of a narrative that extends beyond the finish line, as a systematic leveling-up of your life. You see the transient pleasures of beginnings diminish to nothing in the far future and the enduring rewards of finishing as a steady source of dividends extending out beyond the horizon."
Those who take on big goals are seen as naive and almost childlike, because the 'experienced' believe they already know the end results.
Those who don't take on big goals get to be in the audience and throw stones, but never really amount to anything other than gloating at a possible failure.
I think the experience works against you at a certain age. The projections are a lie, or possibly inaccurate at best. I've come to believe you don't know what will happen until you do it -- what your mind simulates is often only correct in the broadest sense, but way way off when it comes to the important details and compound ramifications.
In otherwords, keep taking on big goals and press on to finish them, while ignoring that pesky voice which thinks it already knows how this will all turn out. And ignore the people who do the same, their words are rarely helpful.
May be when you are older, you can see the end result with more clarity, and decide that is not worth the effort and the sacrifices that you have to make.
Is it better becoming a millionaire when you are 30 or when you are 50? If you do it at 30, you will enjoy the fruits for 45 years. If you do it at 50, you will enjoy them for 25. (Assuming expectancy_of_life=75) Also if you sacrifice a number of years it is a larger sacrifice over the rest of your life.
I'm not saying that's necessarily the case, but perspective can be gained with age and experience and that can colour your view of the world and how much you appreciate what you really do have.
But perhaps more to your point, what does my experience tell me about bold ambitions? Well, mostly I've learned that making big predictions is foolish. The older I get the more I discover how extremely subjective life is, and how dependent everything we know and take for granted is based on personal experience and perspective. I'm much less likely today at 35 to predict the outcome of a project than I would have at 25. My experience comes in at a smaller scale on more specific issues. Engineering choices for instance, I have a much finer tuned sense of where to balance hackery and YAGNI, or how to manage different kinds of business relationships. But I certainly am loathe to sit around making armchair prognostications about the medium to distant future. In short, experience does not make me think I know more, it makes me aware of how little I actually do know.
There are two necessary factors to great feats: The foolhardiness to start, and the stubbornness to finish.
I focus a lot more now on projects that I know I can finish, and work aggressively to keep them in scope, as hard as that can be. (There's always shiny features you want to implement, but too many of those, and your side project collapses under its own weight, in my personal experience, anyway.)
killnine: i hope not to be the bearer of bad news but it seems you've been hellbanned for 2 years. only users with "showdead" can see your comments, and no one can vote on them or respond to them. unfortunate because voting up your comment would have prevented me from leaving my own. :)
When I'm moving around my laptop, and pop into the "projects" folder and see what a graveyard it has become. Dozens of half baked projects that seemed brilliant at the time, that I either lost interest in, decided the concept was too difficult, or (and this is the worst one) let my self doubt convince me that it would never work. The really sad part is, every now and then I'll go back in and check out these projects and a lot of the code and design is actually pretty good. I ask myself, "Why did I think this sucked again?"
The best analogy I can make to this scenario is the self doubt that cripples many writers setting out to finish a book, screenplay, or novel. It's almost as if you tell yourself that the script sucks, to give you a reason not to finish it and move on to something cooler next week. As a writer, what's the best way to overcome this? Just FINISH the god damned first draft. Roll up your sleeves, commit an hour (or two or three) every day to working on this project, and slog through it until you type "FADE OUT" (or "The End") or (if you're coding) make that glorious commit to polish off your project.
No matter how much the project, script or book sucks, there are few feelings of satisfaction that match that.
I've learned the hard way that for me, by far the biggest risk in a side project is me losing interest before I have something up and working. So now I just keep that in mind as I'm planning and pruning features for the initial version. The risk isn't "what if I don't have feature X and people get mad?", it's "what if this gets too complex and messy to implement and I get bored and quit before finishing?"
Maybe it is good that we cannot finish all these projects, since they have no use anyway...
Nobody's forcing you to work on, or finish, a specific project. But if you are always starting new ones and never finishing anything, you have to identify why you don't care about something that seemed like a good idea when you first had it. Did you disprove some of the assumptions? Too lazy to knuckle down and code? Too scared of marketing it and putting your name to it? Not enough time? Prefer sketching wireframes? I've learnt a fair bit about myself from introspection here, especially when I consider the projects I do finish. Often, something I really want to just exist, right now, and without much of the baggage that's around the MVP-prove-iterate-market-blog-build cycle.
You're never finished until you stop what you're doing. A writer may "finish" a book but ei has to start another or they've "finished" writing. However for every book they finish how many incomplete, half-baked ideas do you think they've run through? Is every idea they have golden and worth pouring months and years of effort into? No.
Some ideas deserve to die.
But once you've found that one worth pursuing there's nothing to do but roll up your sleeves and put in the time. You will vacillate between euphoria and despair. You may come to regret ever starting and hate yourself. But if it means anything you will force yourself to press on through those darkest moments. And before you know it you'll be done... and ready for the next project. Creativity isn't the rush you feel when you have a good idea and dream about conquering the world: it's process and discipline. It's writing 1500, 2000 words a day no matter what.
I find it helps to have someone to nudge you onward. An editor, a mentor... someone you can discuss the project with who has an objective opinion. They will help you in that moment when you're thinking of giving up.
Then i realised what was the reason makes me not touching the project after a while...
The first steps are always known and can be done by almost everyone.
- Buy the domain
- Construct the idea
- Even, start coding the project
And here comes the reasons why you slowly starting not to touch the project anymore;
- You realise that you are not sure how to deploy this on production.
- You realise that you will need a business model and you are just a developer/designer and have no idea about those.
- Then comes the tax issues, and realisation that you need a company.
- You don't know how to licence your idea/project
I can list some more but these are just enough to make you feel that you need to find some people to help you which is not free but expensive unless you have friends that are expert in those areas.
Yep, you give up the project...
My advice for this is don't worry about it. Just hand install on a cheap shared web hosting place and manually copy stuff across to get it up and running.
When that gets too annoying, start automating. When your home grown automation scripts get long and unwieldy, look into Capistrano or Puppet (or Chef, or Ansible). The important thing is: make it work first, then make it beautiful.
> - You realise that you will need a business model and you are just a developer/designer and have no idea about those.
I feel you there! :-) Having an idea and trying to think of how to get someone to pay for it is daunting to me. I feel like a blank canvas and I have no idea where to start.
> - Then comes the tax issues, and realisation that you need a company.
Again, don't worry about it. If you make so much money that it matters—well, that is a good problem to have. You can always incorporate (or whatever) later. And if you're pulling in a lot of money you can afford a lawyer to just handle it all for you.
If you're making a web site or a app store app (binary distribution) then again, it doesn't really matter. If it becomes so wildly popular that people start abusing it somehow, and in quantities that matter—again, that's a nice problem to have (compared to no one using your site or app).
If you're releasing source, then pick MIT, BSD, or GPL (just choose randomly if you have no opinion). If the one you picked turns out to have side effects that you didn't foresee, then feel free to change it–it's your code after all, so you can do what you want (though if you get a whole bunch of external contributors, it gets hairier).
One thing I've found that really really helps—get a partner. Having another person around (and not necessarily physically) is a great way to help keep you from getting distracted. This is why companies get stuff done—there's always someone around working and you can't just slack off without losing face to everyone around you. It's really hard to sit around and read reddit all day when the 3 people in the room with you are all working hard…
How can i not worry about deployment?
What happens after people trusting and starts using my 'lets say' web app and after 2 weeks i get my database hacked? Companies have TechOps department just for deploying the applications correctly. I am not trying to argue but trying to explain how i think of this :)
Maybe i am being little bit too much paranoid...
Should i just set Apache/Passenger with some basic configuration and wish that everything is safe enough ?
You'll probably make mistakes. The biggest actual devops advice I can give is backup. Everything. Often enough so that if you lose everything since your last backup you can live with it. And again, it doesn't even have to be automated. Run mysqldump by hand and save the results away somewhere. Rsync your home directory away. If you have a dedicated server, rsync /etc, too.
Having a backup is the solution to almost any catastrophic event in the devops world. Disk crash? Get a new disk, restore from backup, continue on. Hacked? Figure out how, fix security hole in code (or wherever), wipe server, change passwords, restore from backup, continue. I'm sure there are more.
Having done devops work, most of the hard part is getting it to all run smoothly and automatically (big web sites have many many servers and slave dbs, and deploying to them all becomes complicated). But as a single person working on a small project, that's not the most important thing to optimize for, in my opinion. It's more important to get it done.
>- You realise that you are not sure how to deploy this on production.
>- You realise that you will need a business model and you are just a developer/designer and have no idea about those.
>- Then comes the tax issues, and realisation that you need a company.
>- You don't know how to licence your idea/project
As someone who isn't a very good designer/developer this seems like the easiest part to figure out. Coding the project is the single greatest struggle for me as I just don't have the experience/expertise but it's something I enjoy doing and want to do.
The problem i have is always with "The great idea I have".
- Deploying? I do integrations and devops-like stuff at work, and online discussions tend to overblow this topic given this probably matters among the least. The "correct" way is the fastest that will get the job done now so you can keep your momentum going. Until you go full hog hot-deploying to keep your uptime high, expect to destroy everything eventually, who cares if it's sloppy if it went into the trash? Just git receive hooks are good enough for toy projects like O(n^3) algorithms are probably fine for starting some random webapp.
-Business models are in abundant supply out given the number of times "ideas people" that "just need someone to make an app/site of it" have approached me. Unless you're undertaking significant costs or are on the edge of financial ruin, you shouldn't worry though given starting a tech company is the cheapest it's ever been and only getting cheaper (per Mark Cuban). However, you may want to do some quick market research so you don't waste too much time building something that nobody wants - your time is actually going up in cost at a rate faster than Moore's Law gives you savings! On the other hand, don't be like me and think that focus groups and all the stuff that big companies do for thousands typically for a waste of money applies for you. It seems common sense but we all do dumb things in hindsight and it can be hard to step outside your box. People with good prioritization skills do less dumb things wrt execution, that much I can assure you.
- Taxes are pretty simple for tiny companies in the US (this IS still a cheap place to run a business comparatively), you can probably hire an accountant to do it for a couple hundred bucks without paying a lawyer for even more. Everyone gets moved to Delaware or something later, just get that done hastily to check it off. It's the FUNDING that will make your head spin, taxes are trivial in comparison. Beyond that it's all good problems to have from everything I've read.
For me, I honestly think the hardest part is coming up with a coding project that keeps me motivated long enough without encountering some real hard blocks that just can't scale even though I know they're stupid easy for others. I get a small aneurysm having to deal with frontend design decisions & execution as a systems & backend stack guy primarily. Font choices, picking color palettes for an audience, ... am I making a business or planning my wedding again?
I've only shipped maybe a couple personal projects for the public to see though, so perhaps I'm full of crap and I wasted everyone's time. But if anything, I know how my own habits lead to ineffective output even with what seems like a lot of effort, so I think by telling people the opposite of what I do, it would give better results for others than saying what I actually do.
You have to do the work. There is no one else that can do it for you. It is entirely up to you; actually, it has only ever been you, because it is you that rolls out of bed early to bring it. No one is going to do that for you. If you want to do it, then you will figure out a way to make it happen.
Like some of you, I have a family. That makes things a bit challenging at times, and you will likely have to work even harder to find the time, to make the space, so that you can bring it. And, I will add, those that are parents, this is a great example to set for your children. You want to be, "The Daddy that brings it." You want to be, "The Mommy that brings it." Because, you want to instill in them that they can, too. It's a valuable life-lesson. In turn, it is psychologically healthy for you as well, to know that you are a parent that is firing on all cylinders. In addition, it is incredibly gratifying when your child sees your work. "Wow... that's the new game that you're working on! Let me try!" It will fuel you like a Saturn V launching to the moon.
You may look at your project and think, "I'm never going to make it. I'll never finish." Please, I urge you to set these thoughts aside and push through. Think about the analogy of building a wall. A wall is built one brick at a time. Watch a mason build a wall one day. You will observe that he or she lays one brick at a time.
This is how you have to view your project. Sure, it would be amazing to have an entire day, every day to devote to your project. However, the reality is that most of us simply do not have that luxury. So, strive to think of it as a mason: lay one brick at a time, and eventually the wall will be built. Every character that you type into Xcode, Visual Studio, etc. turns into a keyword, a variable name, etc... that subsequently turns into a line. Those lines build up, day by day, and before you know it, you have a program, and you look back and think, "Wow, why did I ever think I could not finish?"
Also, let go of "Internet Time." That is to say, we all read HN and see these impressive "Show HN" posts, and submitted stories about the Next Big Thing... and it seems like things are happening so fast, and we think, "Why even try?" Well, the reality is nothing is happening fast. It is an illusion. Most all of these stories have an incredible amount of time and work behind them, so let go of that illusion, get started, and stay focused.
"There's only this moment and the next moment. Every one of those moments is a test that you get to take one time and only one time." 
Strive to drive through each moment. Make it count.
You have to fight. This is paramount. I will say it again... you have to fight! What I mean here is fighting by engaging your Will. Engage your will to get up, to get moving. Engage your will to eat right, to exercise and go to bed on time so that you have the energy to get up and bring it.
What you are going through is what we are all going through; that is to say, we are all grinding, whether it be in a start-up business, or washing the dishes by day as we bootstrap a start-up at night; we are all struggling, fighting to drive our dreams into existence. We are all struggling in some way, whether it be through failure, health issues, personal issues, family issues, etc. No one is immune from the grip of suffering through his or her struggles.
You are not alone.
Embrace the grind. Vince Lombardi said it best:
"And in truth, I've never known a man worth his salt who, in the long run, deep down in his heart, didn't appreciate the grind, the discipline. The difference between a successful person and others is not a lack of strength, not a lack of knowledge, but rather... a lack of will."
You have to use the will to fight those thoughts that say, "I'm getting older. I'm failing. I'm not motivated. I can't finish."
The clock is ticking for all of us... fight! You never know where your work will take you. Do not forget that, you have to dream it first in your mind before you can see it in your life. And to see it in your life, you must work. You may not be able to see things clearly now, but you never know what doors could open for you that you did not even know existed.
Ang Lee, the Taiwanese film director and screenwriter that directed Crouching Tiger, Hidden Dragon and Life of Pi, discusses his struggles to break into film. I urge you to read it:
These are the things I am struggling with and they make fighting it a non-starter.
He responded by saying that he doesn't have more discipline - he just creates environments that decrease his opportunities to fail (ie. get distracted) and increase his likelihood to succeed (ie. finish the work).
The idea is to not trust yourself and not give yourself the opportunity to fail. A concrete example of how I've personally put this to great use in my life is how I made it a habit to go to the gym:
When I was in college, I wanted to go to the gym regularly. Unfortunately I found that when I was in my dorm room and needed to get ready for the gym, I lacked the motivation to get out of a comfortable situation. What I began doing was taking my gym clothes to class and going straight to the gym after class. This required significantly less motivation on my part because I was already walking around campus, sometimes even passing the gym by on the way back to my dorm. The step leading up to that also required very little motivation - putting clothes in your backpack. The result was that I created a sequence of events that each had a small likelihood of failure. 10 years later, going to the gym is my favorite hobby.
Another example related to getting work done came about when I was trying to work on my side projects from home. It never worked. I'd always want to browse the internet, watch tv, play video games, or spend time with my girlfriend. Starting work when my Xbox was in the next room meant summoning a monumental amount of motivation. Instead what I started doing was going to a local coffee shop or coworking space. It doesn't take that much effort to just go to a public space with wifi (and if it does, you can use the advice above). Once there, you have put yourself in an environment where everyone else is working. Aside from noise, there are fewer distractions. In addition, you'll look like an asshole if you're sitting in front of your laptop playing on Reddit for 4 hours while everyone around you is getting shit done.
If you can make a habit of completing those small triggers that lead to bigger outcomes, you'll eventually have gained a much more significant habit.
Some things I've noticed: Being physically fit helps and doing sport is a bit easier than overthrowing the world. Maybe ask a friend to go with you.
Sleep is also easily modified: Try out the effects of light, temperature, noise, sleep duration etc. Maybe use Melatonine or a sleep cycle alarm.
It's also a lot easier to do things when I don't have to do them. If I tell myself, I _have_ to run today in order to get fit I probably won't do it. But just going outside quickly for some fresh air? Sure, let's check the mailbox ... and now that I'm outside, why not run for a bit?
It's a bit like jumping out of the bed before the brain realizes what you're doing and has no time to scream "I don't want to wake up!" :)
Here's a good technique for training yoũrself to get up in the morning:
It's the same technique that you suggested: train yourself to get up as more of a reflex of hearing the alarm, not as a series of mental motivations and self-persuasions.
One can't overestimate this advice. Regarding willpower: What I find very useful to remember is that willpower is something we all can and have to develop. Also, it's important to understand that willpower is a limited resource. Similar to training your body it has a lot to do with energy management - strain and rest. One of the richest advices I've found is . I particularly like the 4 steps of development:
1. Avoid things that are not useful
2. Overcome in case they are apparent
3. Develop things that are useful
4. Maintain them
 http://swamij.com/podcast.htm see Developing Determination for Enlightenment
Yeah, I seem to get this false sense of these Show HN all being something that someone whipped up in the weekend, even though the magnitude of implies that that is very, very unlikely. It's like I think that since that they are all so easy to find, and they happen so often, the time that these seeming wizards made them is proportional to how much attention I have put on them, which is clearly erroneous. Looking at the projects they are often years old, maybe even years in the making.
I think I crossed the line of being more demotivated than inspired by those types of posts. I should cut down on this Web-thing.
Anyway, the way that I see it you have to do these projects for yourself, not for anyone else. You write them to scratch an itch, to see an idea blossom or wither, to enjoy the act of coding. Posting them online is the thing you do after you've done the thing you wanted to do.
I know when I originally started frequenting HN, I felt enlightened, educated, and sometimes motivated by some of the posts I saw.
Nowadays, I feel overwhelmed and discouraged from everything going on and what I seem to be missing. But I think you're dead-on -- it's all an illusion.
It's called PyLaTeX , it's a Python interface for LaTeX that supports creating documents and snippets. One of the coolest features I think is the conversion of NumPy matrices to LaTeX ones.
The HN new page  is just a bit rough on someone posting that doesn't know a lot of people that can upvote it, reddit  was a lot more forgiving.
I used a kind of accountability hack to get a lot of writing done last year — basically by setting a £100 penalty for any day that I didn't write 1,000 words.
I'll need a database (and thus a schema), and a REST API, and security considerations ... that's all fine. Start actually writing and testing and OH BOY another feature idea! Write it down for later, continue back where I was. But that new feature will require this change to the current design. And to do that now I have to change this other part and ... repeat until I give up.
tl;dr: feature creep kills me, even with my own ideas. I cannot just Let It Be and produce a 1.0 with minimal features.
I did find this article which is related…
The article argues that the satisfaction prevents us from actually reaching our goals.
Christ you are in for a shock if you think the immediate step after reserving social media handles is the hard bit...
My main project (CycleLive) is approaching two years old now, and I've got a small but loyal audience which I'm nurturing.
Actually I think CycleLove has a different problem — the "a blog is not a business" one.
Although it was never intended to be a business in the first place, I want to angle it in that direction, and that's the part I'm struggling with now.
yeah perhaps what you and I consider products are in different categories, so perhaps my words are not so relevant to you.
I enjoy making geeky technical things, but fail to find any users. :(
One day I will sort it out (maybe).
If the former, how do you know that?
The first is a static judgment I am applying to myself, and it's a definitional straitjacket. The second is simply an observation, and it leaves room and opportunity for positive change.
When we tell ourselves we "are" certain things or "always/never do" certain things, we are defining ourselves in a way that makes it harder to change, due to the reinforcement.
At this point, I pretty much automatically recognize negative "judgments" and do the translation... I think it helps a lot.
The few projects I've finished, they've always been for-pay. Either contracting or as an employee. For my own, almost none.
However. A little over two years ago, I started coding an edu-based app that a friend and I designed (he's the biz side). I was gonna become a father and I thought, what better space to be in since I'm going to be dealing with it in the coming years.
Typical story, coded nights, mornings, weekends. After the baby came, coded less but still the same schedule. We launched the site last fall. And then.. we started having having users saying our site was too complicated, the change log and bug list kept growing. So, this thing I had worked on for so long and pushed into existence by sheer will, just burned me out.
I walked away for a few months and even though we were making almost $1k/mo, I felt it not worth my time anymore. But now, in the past week, I'm changing my tune.
At my day job, we're going thru the final phases of closing on m&a suitors. At first I thought this was awesome, but then looking at the suitors jobs list and reading them, I realized none of them are interesting. Do I want to code day an night? No. Do I want to spend all my day at an office? No. Do I want to help push someone else's dream closer to IPO? No.
I realized after this that I already have the dream (work-wise). We have edu partners lined up, some good potential biz deals, and it's all hinging on just spending a few weeks and fixing things. But having a family, working for something for a long time and not really seeing the reward (yet) - it's hard to keep going thru it all. But, I visualized and thought about "what would it be like to sit at my desk (anywhere I want) and keep making the thing I built better?".
This is the only thing I have ever 'finished' (will it ever be) and I think looking back, I did it all for the right reasons and kept pushing forward. Regardless what anyone else said about it (almost all the responses about the site were positive).
For me, in the end it is about doing what you love, channeling your passion to reach the goal(s). Goal 1 - launching it - reached, done. Goal 2 - helping people enjoy using it - restarted.
Lesson learned: don't give up. Every hour makes a difference.
1) Break down your project into bits that excite you all the way through and imagine being excited while you're planning it. Have someone else be there with you with to plan this with you while you do it - helps with the planning. This chunking of the project itself is the battle. You beat this and you've conquered most of the problem.
2) Work on two - three manageable projects at the same time. This usually has worked for me my entire life. Alternate between them. When you get bored with one, pick the other one up and plan all of them out so you have interesting bits chunked out throughout.
3) Always work with high-energy individuals who would keep the energy up throughout the project. When you feel tired or bored, they will find a way to pick you back up again.
4) Always find projects that YOU can find some value in YOUR life.
So stop beating yourself up about finishing. Play in society and worry about things when you feel it's necessary, but if it's your private, creative work, that is the time to be bold and selfish. Don't try to fit in for the sake of it, do things because you want them. You shouldn't care about "finished", because you should be engrossed in the act of creation.
Are people really checking the availability on social media? I know that if I get the .com I want nothing else matters and the social media handles can be anything.
I know the feeling anyway! The initial excitement and the downfall.
If you start a project just to play with some new shinny framework/tech then it is likely that once the novelty wears off nothing of interest would remain.
If however you start a project because you are excited about some product vision that doesn't already exist or not in the form you've envision then the drive to bring that idea/vision to fruition can be a powerful motivator.
I wrote a blog post on this matter some time back:
I find this YT video on Steph Curry to be an amazing story of how success is built by they choices we make every day.
'Are the habits you have for today on par with the dreams you have for tomorrow?' Not yet... but its getting there.
For instance, I made a podcast downloader as a Haskell learning project. I haven't goften around to making it delete old files. Meh. The interface is good, it is reliable and fast. I'll just clean it out manually now and then. Or maybe get to it later if I feel like it. A few years ago this might have been hanging over my head as a failure.
I think the secret to a successful side-project is deciding on an MVP that can be built in a single weekend. I've found that I'm also much more likely to keep iterating on a project if it's already in a 'finished' state.
I seem to run out of steam or lost interest in my more ambitious side-projects, where working for a whole weekend will only get you 10% closer to a finished product.
an editor I own
a book I own
another book I own
the newer version of a phone I used to own (had s3, got s4)
a mouse I am going to consider buying
a keyboard that probably would have been my choice if I didn't get a kinesis
I've started to throw all my embarrasing, childish project onto github. If someone files a comment regarding how bad something is - great, then I have something concrete to fix.
And having a lot of projects open means there is always something easy to fix to keep the streak going. Suddenly projects move forward, albeit one small commit at a time.
This way I have actually completed more projects in years.
In any case, rushing after each new idea is a great way to spend time, but you need that time to be executing on the few ideas you actually choose to pursue.
I don't think "man, I'm so far from being finished." That's just a demotivating way to see your project. The big milestone is having something that's useful enough for people to be interested in, no?
Most projects die during the creation of the outer scaffolding without much of the envisioned functionality in place.
Disclosure: I'm not a leaguer.
That's why you need a team. Everyone has optimistic days and pessimistic days. On a good team you all wont have them at exactly the same time. You're team will push you through and help you finish.
A site where you take responsibility for finishing your project. If you don't, you will pay heavy price. Lets say we will spam your inbox with a thousands of letters that remind you of your promises.
But now I barely working on anything. I admit I don't like any work at all. Working for Google or SpaceX? No.
I think we want to finish something because we are not satisfied with our current life. If you feel your current status is okay, it's not easy to get motived to put yourself into some extra work.
This one has a reverse interest for most entrepreneurs, how do you get your product past the initial excitement and impending boredom of the customer?
One day a management consultant, Ivy Lee, called on Schwab of the Bethlehem Steel Company. Lee outlined briefly his firm's services, ending with the statement: "With our service, you'll know how to manage better."
The indignant Schwab said, "I'm not managing as well now as I know how. What we need around here is not more "knowing" but more doing, not knowledge but action; if you can give us something to pep us up to do the things we ALREADY KNOW we ought to do, I'll gladly listen to you and pay you anything you ask."
"Fine", said Lee. "I can give you something in twenty minutes that will step up your action and doing at least 50 percent".
"O.K.", said Schwab. "I have just about that much time before I must leave to catch a train. What's your idea?"
Lee pulled a bland 3x5 note sheet out of his pocket, handed it to Schwab and said: "Write on this sheet the six most important tasks you have to do tomorrow". That took about three minutes. "Now", said Lee, "number them in the order of their importance". Five more minutes passed. "Now", said Lee, "put this sheet in you pocket and the first thing tomorrow morning look at item one and start working on it. Pull the sheet out of your pocket every 15 or 20 minutes and look at item one until it is finished. Then tackle item two in the same way, then item three. Do this until quitting time. Don't be concerned if you only finished two or three, or even if you only finish one item. You'll be working on the important ones. The others can wait. If you can't finish them all by this method, you couldn't with any other method either, and without some system you'd probably not even decide which are most important".
"Spend the last five minutes of every working day making out a 'must' list for the next day's tasks. After you've convinced yourself of the worth of this system have your men try it. Try it out as long as you wish and then send me a check for what YOU think it's worth".
The whole interview lasted about twenty-five minutes. In two weeks Schwab sent Lee a check for $25,000 - a thousand dollars a minute. He added a note saying the lesson was the most profitable from a money standpoint he had every learned. Did it work? In five years it turned the unknown Bethlehem Steel Company into the biggest independent steel producer in the world; made Schwab a hundred million dollar fortune, and the best known steel man alive at that time.
> he was retained by John D. Rockefeller Jr to represent his family and Standard Oil, ("to burnish the family image"), after the coal mining rebellion in Colorado known as the "Ludlow Massacre". Upton Sinclair dubbed him "Poison Ivy" after Lee tried to send bulletins saying those that died were victims of an overturned stove, when in fact they were shot by the Colorado militia.
> Lee espoused a philosophy consistent with what has sometimes been called the "two-way street" approach to public relations, in which PR consists of helping clients listen as well as communicate messages to their publics. In practice, however, Lee often engaged in one-way propagandizing on behalf of clients despised by the public.
> Shortly before his death in 1934, the US Congress had been investigating his work in Nazi Germany on behalf of the controversial company IG Farben.
Very good read!