Here's what I did:

1) In the months leading up to my move I worked my ass off and always volunteered to help out wherever my boss needed me most. This gave me experience on a lot of our different projects and made me less replaceable.

2) I told my employer one month before my move, and made sure they knew how much I enjoyed working for the company and how I really wanted to continue working for them remotely. However, I also made it clear that I was fully committed to moving with or without my job (in fact the following weekend I was flying out to find an apt).

It seems somewhat selfish and counter intuitive, but I believe that it's better to give less notice time than more. This creates more of a sense of urgency for your employer. A friend of mine tried the same thing but gave five months notice and was told that he couldn't work remote, but "come talk to us in five months before doing anything drastic (aka quitting)".

However, regardless of when you tell your employer, the most important thing is that you must be 100% committed to your move and willing to lose your job and start over in your new location.

To answer your other two questions: Working remotely has it's pros and cons, which I won't go into detail on, since this post is already getting rather long :) But you can find lots of info in other places about this. Overall though, it has worked out very well for both me and my employer.

So far in four months of working remote I haven't been back to the office yet (it's a four hour flight). But from what we've discussed I'll probably be back in the office for one week per year.

Best of luck to you!

https://gist.github.com/cspags/93f18a2fe505bf4f1686

However, I eventually want to make the move into freelancing. So I'm thinking this is a good opportunity to pitch them to let me leave fulltime employment, but continuing working with them as a freelancer.

Anyone have any experience/advice doing this? Thanks!

Comments URL: https://news.ycombinator.com/item?id=8458563

Points: 4

# Comments: 3

http://www.amazon.com/Apollo-Catherine-Bly-Cox-ebook/dp/B003...

I find this motivating, especially when I'm feeling down.

Kind of hard to explain in words, but hopefully that helps!

He's a very likable guy and I consider him to be one of the top devs on our team and in our company, so I definitely don't want to see him leave. Unfortunately though, we aren't very close personally, so I'm not sure if I should bring it up to him. For all I know he wasn't even looking at jobs for himself...

I appreciate any advice you all have on whether or not I should bring it up to him, project manager, etc. And if so, how to go about doing it. Thanks!

Comments URL: https://news.ycombinator.com/item?id=7268401

Points: 8

# Comments: 14

I'm assuming that this was due to a caching issue but I'm not sure. Is there anything HN could have done to prevent this?

Thanks!

Comments URL: https://news.ycombinator.com/item?id=7024817

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=6946688

Points: 1

# Comments: 0

On the flip side, what makes a good job post? How do you make your company stand out to potential employees?

Thanks!

Comments URL: https://news.ycombinator.com/item?id=6887574

Points: 4

# Comments: 6

Current - Interesting idea but I found it difficult to mouseover a particular portfolio site due to the small hitbox for each covered one. Also don't like how the navigation seems crammed in an odd spot.

02 - This one isn't bad but I didn't like the home page. Not sure if it was just broken in my browser or if I was supposed to see just one sentence until I clicked on it.

04 - By far my favorite. Although I wish the navigation was at the top instead of the bottom.

Three things really helped me get it to the finish line:

1) I listed out all the possible features of the project, then marked only the features I absolutely couldn't launch without as MVP. I used https://workflowy.com/ to do this because I liked the hierarchical structure and the ability to cross off features as I implemented them. Whenever I worked on my project I'd have workflowy open in one of the browser tabs.

2) If I didn't feel like working on the project I'd open up the feature list, pick one of the simplest items, and implement it. I found that if I started writing even just a few lines of code it was enough to motivate me to keep at it for hours. This was especially helpful as I got closer and closer to the finish line.

3) As others have mentioned here, launch your project as early as you can, even when you still feel "embarrassed" by it, and tell people about it! Looking on Google Analytics and seeing even just a handful of people using my site was incredibly motivating! It made me want to continue improving the site just so that those few people would have a better experience.

Comments URL: https://news.ycombinator.com/item?id=6392494

Points: 2

# Comments: 0