Hacker Newsnew | past | comments | ask | show | jobs | submit | cycojesus's commentslogin

If I may diverge from the main topic but to your point. I'd venture to say that the act of putting reminders and thinking about smoking is the reason you failed.

I stopped smoking with the same book but the it worked (as I understand it now) is that it breaks down every excuses you gave yourself to smoke while it actually encourages you to keep smoking while reading. At the end of the book you just have no reason left to smoke. What happened for me when I closed the book is that I just continued my life as if I was not a smoker, never actually thinking about it. No withdrawal of any kind but I didn't remind myself that I used to be a smoker, never. I know it but it's not something I think about


Sorry, I wasn't clear enough. The book and the reminders are why I actually quit smoking after over a decade of a pack a day. During all my failed attempts to quit I tried to use willpower combined with trying not to think about smoking.

Giving myself permission to think about smoking was a huge factor in actually quitting. "Don't think about the colour black" is a great way to fail...:)


That's hibernating you're describing. Suspend wakes less time than it takes to open the lid and the laptop is directly usable.


Strangely I came to comment because I had the opposite reaction. I couldn't read the article because I find the presentation way too noisy (and in general can't stand vertical scrolling much.)


Fixed selection of titles with no possibility of putting one's own content... Indoctrination much?


How about a commit hook that warns when it looks like you're about to commit a secret key?


Did something similar, just built a module for our CI tool that checks against sensitive information (secret, salts, hashs, hidden feature), pretty efficient as every dev (myself included) can get lazy and use keys directly in scripts, instead of our Config loader that safely retrieves all that.

Not bad in itself, sometimes all you need is a dirty script, but as other have said, they tend to stick around, a key part of our CI module is actually putting expire date on scripts, or check dates. I will receive an email telling me to check and a warning on the CI at build time. It's been great to keep our code clean while allowing us to still do things dirty when required.


Sounds like a good plan to me!


I'd say of you have to give hints for a joke then the joke's not good.


Given the number of Bentley, Lamborghini, Ferrari, and cars in general roaming the streets of Hanoi I'm not sure that's a valid point.


Who's your 'us'?

I'm coding in Ruby full-time for some months now and it's the most friendly language I've encountered, everything feels natural.


"Error (509) This account's public links are generating too much traffic and have been temporarily disabled!"


Yup, same here..


+1. (Me too.)

I suspect De La Soul hit some sort of quota limit and Dropbox will either (a) hit them up for a bandwidth bill, or (b) decide to raise the limit as a goodwill/marketing gesture, later in the day.

Edit: Downloads working now, 46 minutes after release time.


Is it just me or the perspective of that image looks very wrong?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: