I actually just did this. Started a new job in June last year, ended up moving across the country in Dec, but really liked my job and wanted to keep it and work remote full time.
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.
Here's a fairly simple strategy for beating challenges 1 - 5. Basically drop off people in the elevator according to whoever's floor is closest. Then once the elevator is empty go to the closest floor that has people waiting to be picked up.
I was able to get 2048 building off of your solution. As you said, always keep your highest number in the top right corner. Try to build the next highest numbers up along the right edge, so that you have say, 256, 128, 64, 32 along the right edge. Always keep 4 numbers there, and only use up/down/right. Then just focus on building whatever number you need next to double the bottom right number, so that you can "chain up" numbers along the right edge and double your highest number in the top right.
Kind of hard to explain in words, but hopefully that helps!
The only reason I still use Google over DuckDuckGo is the keyword suggestions as I'm typing. I find that to be very useful when I'm searching for something but not quite sure how to phrase it. I would for sure switch over if DDG added that!
One thing that I like about Knockout is that you can easily drop it into a legacy site, allowing you to have some pages that use it and others that don't. Forgive my naivete, but is this something that is easy to do with Ember or Angular as well?
01 - Found it a bit confusing as to which link I should click first. Add fuel to your business? Let's get started?
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.
I've dealt with this same problem for many years as well. Recently I just completed a side project (http://www.randolunch.com) for the first time ever.
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.
Hi all,
Randolunch finds random restaurants for you to try based on your location. I'm a .NET dev, but I began learning Rails a few months ago and this is my first Rails site, so I'd love to hear any feedback. Thanks!
Great suggestions! I'd also add Octopress (http://octopress.org/), which is built on Jekyll and works well with Amazon CloudFront (haven't tried CloudFlare, but I'd imagine that works just as well).
Completely agree. The other problem I've seen with getting stuck on the same project for X years is that you'll have a very limited portfolio to show for it, unless you're working on side projects as well.
I've been dealing with similar issues for a couple of years now. At the worst point I was unable to talk in groups of unfamiliar people without my heart rapidly pounding and face flushing. Not sure if it's quite that bad for you, but I'd recommend googling social anxiety. After learning about that I ended up working with a therapist and taking a year of improv classes. This was by far the best thing I've ever done and really helped my conversation skills. It'll also help with your confidence, which will in turn reduce your nervousness.
Feel free to message me if you'd like to talk more.
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!