Very positive outcome.
318 karma · joined September 2, 2010
Very positive outcome.
People on HN are happy to pull something apart if it's incorrect, they just do it in an even tempered manner.
Additionally: This isn't reddit or slashdot, a lot of people here are looking to gain funding or contacts, therefore HN has much lower anonymity. Therefore more likely to be civil and appropriate.
- Mindfulness, oddly enough. I always need to stop, notice that I'm getting tired or distracted (or burning up way too much energy on something), stop, re-evaluate, and go
I notice sometimes I might just be "screwing around" on something (shuffling CSS around, painting bits of a picture that aren't critical), so I'll focus again and do something thats adding value
Especially when you're tired - its easy to futz about doing not much at all while thinking "I'm so busy and productive". It takes effort to mentally stay on task after a day at work
- Cold showers and coffee
- Being more assertive / aggressive at work. I used to burn myself out trying to do everything and anything, and spent a lot of time bashing my head against walls because someone else thought it was of value (and I didn't).
The more confident I get with my freelance jobs, the more risk I'm taking at work. Quiet happy to tell someone that an idea isn't worth pursuing and push back when I've got too much on my plate.
Also, learn to argue (in a professional manner) without feeling like shit about it. Saves a lot of hassle.
- Just doing it. It's cliche, but nothing beats this: take off your work gear, shower, change, prep, shut the fucking browser, turn off the tv, and go.
Sometimes its almost comical what I have to do to break out of habits like idling online or gaming or etc. I will sit and literally yell at myself if I have to, to get myself back on task.
Small post-its work as well, like "get back to work" or "is this really worthwhile and enjoyable?" (that one's stuck to the PS3)
- Remembering that projects are fun. I feel way better about myself after a half hour working out or four hours building time on something than watching TV all night. It turned my mood around quiet a bit too - went from being quiet sullen to very content and positive about stuff.
- Catalogue what you've actually accomplished in terms of stuff created / learned / produced
- Hack it all up into "stuff I will use", "stuff I will reference" and "stuff I will archive"
- Set some hard lines and hard times against deliverables with actual boundaries / units of work - what will you finish, by what date, where does it fit, what's the next stage?
Finally, and the biggest thing for me was: if you can hardline at work, be a professional and produce lots of good stuff on a dealine (assuming you do), you can do that for yourself as well.
Sometimes (as a non-startup type guy) I found it easy to go to work, push past pain barriers, bust serious ass and make some pretty incredible stuff happen, then come home and have a completely different - lazy and shabby - attitude.
As soon as I decided to carry that attitude towards my own goals / projects, it turned a lot of stuff around. I had two or three projects that were half parked for nearly 8 months that I set completion goals for and cleaned up in about 2 months.
Felt great, and made me realise how much you can actually produce when you have a clear idea of what you want to get done.
There's very few people who are decent and / or successful who haven't had some seriously hard knocks involved in shaping who they are.
Edit for anecdote: I was a mid 20's guy with an average job and bad investments that put me close to 3/4 million in debt just before the crash. A lot of pain, panic and off the cuff decisions to save my own ass, but hell, was one of the best things to ever happen to me in hindsight.
It can be hard if you don't feel engaged with your co-workers but it happens. Set your goals and areas of ownership, develop yourself to support them and start pushing to see if you can progress your career. If they aren't a good baseline to compete with, you have to make your own structure.
If you have a baby on the way pretty soon you'll be in coast mode anyhow (I mean this - if you're still working, some days you'll barely have the energy to focus on your inbox, let alone productive work)
After this stage in your life, re-assess. Maybe your work / life balance is different, maybe you'll be more risk tolerant and change jobs / roles, maybe you'll just be happy. Mostly choice, and hard work.
In regards to the after hours stuff, it's doable as well. It sounds crazy to try and launch a whole side project until you actually do it (even with a baby on board). I noticed you knocked back a suggestion to do an off hours project / startup before, don't rush to close the idea off.
To give context: professionally I put in about 47-60 hours a week depending on what's on, and I brick in every single free hour around that (as stamina and life allows) on side projects. Before I started doing that, I said it couldn't be done, and would park my ass watching TV or generally doing nothing instead.
Figure out what you want, don't measure yourself on others, and go for it. =) If it's what you have now, there's nothing wrong with that.
Additionally, due to a generally positive bias (supposing we all generally like YC, HN and have a common positive attitude towards startup culture), the downvotes are more noticable / memorable than things that are frequently upvoted.
Same reason all you can focus on is that chip in your windscreen when realistically its only 2% of the entire window. =)
- A highly skilled professional
- A highly skilled, non-professional
Just because someone has a very well developed skillset, it doesn't necessarily dictate good conduct. Most art / illustration forums suffer from this problem - to generalize, they will have a subset of highly skilled people who ultimately aren't professional in their conduct and reply with some severely inappropriate responses.
It's the same scenario too - when a user submits content that is significantly below the general quality standard of the community (in earnest, being a legitimate effort on their behalf), two responses are generally provided due to the difference in these groups:
- Professionals tend to ignore the content or provide some indicators of which basics to cover
- Non-professionals flame and attack the user due to their level of ability
It's regrettable but the latter often has quite a negative effect. If you can look at someones work and recognise that they are highly skilled, but not understand that they are of poor professional character, you will take on board what they say as being correct or fair.
It's the kind of conduct that stunts a lot of people who aren't thick skinned about their trade.
It's one thing to interrogate if a link is valid on here (eg, by downvoting or through the comments), but taking the time to interact with the site itself and backreference HN is pointless, and damaging to the reputation of HN (regardless of if they are an accurate representation of the community or not).
I'd grind any bullshit for 22 hours a day if it was heading towards something I wanted badly enough. A change of product, codebase or setting isn't going to suddenly change your internal drive or other subjective factors. Even if you hit a startup thats on cool platform X, it will become background noise to getting something delivered / ploughing through the bug list / etc etc.
Your decision to quit isn't progressing because its arbitrary - you're not leaving your job for any specific reason or because you have a clear goal in mind. If you have a strong reason (eg, passion for a project, monetary goal, cancer, whatever), decisions like this normally happen pretty fast.
Take the properties to their extreme and you get what are essentially unseen behaviours (outside of research), like this. This video really left me in awe.
It's a better model then getting into something you know you're fully capable of and having no incentive to perform like hell. Comfortable but mind destroying.
I don't think I'm arguing much pro or con wise on the topic itself, just siding off into the topic of publication vs wider adoption in the target community. My case was the same, I'm sure my work was interesting and important, but it didn't exactly set the journals on fire. =)
Tracking the history on this is a bit slippery because "go" is such a genric term. To qualify this it is a case of finding out what peer review or engagement was undertaken and how far the idea of Go! (as in the non-google one) made it, or if further languages or research were progressed on the back of it.
Sit down where you need to do the work / Open the tool you need to do the work / Do the work.
I don't program, but I paint / illustrate outside of my day job and the only way I've ever, ever gotten over the 80% hump is to just physically be where I need to be and force a handful of actions to get moving.
Also, resetting the "done" point is important - sometimes you're lagging because you've actually finished, you just need to call it, clean it up and ship it, even if it means sacrificing some of the ideals / nice to haves you had planned.
It also ties in with other items here re: Design <> photoshop. Creating a graphic is to design what fitting a tyre is to performance motorsport - an element, an important one, but hardly the entire scope of what goes into it.
Always assumed you could always build X to solve Y, etc etc.