Ask HN: Remote workers, tell us how you got started
21–30 of 33 posts
Re: Ask HN: Remote workers, tell us how you got started
#22I started as a trainee for Junior Software Engineer level working with a startup in Silicon Valley.
The best thing about it is that in just 3 months, I was able to learn HTML and CSS, Bootstrap, jQuery/JqueryUI, PHP, MySQL, OOP in PHP, MVC using CodeIgniter, Ajax, Ruby on Rails, Setting up Linux Server from Scractch, SVN, Git, Agile Project Management and a lot more. My mentor is really good teacher and at the same time "to struggle is to learn".
After two years, we have 9 more team members, an office. We have built our own LMS to train more people remotely. We have bootcamps running in MV and Seattle. We also have consulting projects. We are working with other entreprenuers and helping them with their startups.
Gmail, ASANA, Skype and screen sharing tools make the world flat for us. Gives us the feeling that we are working in one place.
The best advise that I could give to others will be 3 things:
1. Have focus and Love your work. If you don't love what you are doing remotely, chances are you will not focus. 2. Company is about the people not the revenue. This is very critical in a remote setup, you must value your teammates as if they are your family. 3. "What Gets Measured Gets Managed" - Peter Drucker. We have daily reports, we measure hours spent and assigned story points to each task.
Re: Ask HN: Remote workers, tell us how you got started
#23Re: Ask HN: Remote workers, tell us how you got started
#24Advice: * Transparency(what you're doing, when it will be ready, when you're online, etc) * Discipline(isolate yourself from interruptions and keep commitments from the above)
Re: Ask HN: Remote workers, tell us how you got started
#25Re: Ask HN: Remote workers, tell us how you got started
#26I worked for a racing-to-IPO software dev company in upstate NY that collapsed in 2002, and the connections from that spun out into subcontracting, initially for various local clients (and thus already mostly remote, sometimes on-site). Then I moved to Michigan, but kept doing the same work. Then I moved the France; ditto (included one trip to launch a project on-site, living in a hotel for 10 days... ugh).
It was tricky, working from so far away (esp. when working with a team of developers who were on-site), so I worked solo for a few years (my wife published a well-reviewed first novel, which helped a lot); we had a kid in 2009. In late 2010 I found a dev job with a Cambridge, UK-based startup, here on HN. Now I'm the CTO. All of the developers here are remote.
My in-laws are in Malaysia, so I'm working (and parenting; we have two daughters now) in Kuala Lumpur all this month.
I like this setup; it's sometimes really hard (mixing in parenting is the hard part, really).
More details/advice available if there are questions, when I have time tonight.
Re: Ask HN: Remote workers, tell us how you got started
#27Earlier quoted context omitted.
This is great advice, especially about getting out of the house and having a routine. I am on my second remote position and having a daily routine is essential to not falling into productivity hell. I am renting an office in a coworking space so I can have a place to "go to work" rather than working from home. It adds a routine, it gives me separation between work and home, and it's nice to have human contact over th…
Yea I used to rent an office for a few years. I learned some important things - particularly making sure that you have the right office environment for your productivity. I unfortunately rented a space before the 'coworking' revolution and got kind of trapped in an office with non-tech guys much older than me constantly bugging about IT advice, a rent barter agreement when my finances couldn't swing the overhead that…
I currently have a full time job, and enjoy the periods where I am left to get on with my work, but all to often the non-technical users will not read error messages, and ask me stupid questions to "fix their excel". It makes it impossible to work on certain things, like learning a front end framework when you are being bugged with trivial tasks like this every half hour. (The fact we are still using excel as a data import solution bugs me as well, as I have complained about the lack of reliability for a long time now).
So freelancing would hopefully allow me to do the sort of work I want to do. I know there is a whole load of other stuff I will need to manage, but it must be better than fixing formatting issues in excel.
Re: Ask HN: Remote workers, tell us how you got started
#28Other than a few odd contracts, my real beginning in remote work was when I worked at one place for a long time, became indispensable, and explained that I had to move away. They had little option but to allow me to work remotely. After that succeeded for many years, I had my experience and things became easier for the next time ... and onward.
I agree with everyone's else's comments here on the challenges and benefits, but would emphasize very clearly that it's not for everyone.
Re: Ask HN: Remote workers, tell us how you got started
#29Earlier quoted context omitted.
Yea I used to rent an office for a few years. I learned some important things - particularly making sure that you have the right office environment for your productivity. I unfortunately rented a space before the 'coworking' revolution and got kind of trapped in an office with non-tech guys much older than me constantly bugging about IT advice, a rent barter agreement when my finances couldn't swing the overhead that…
Productivity is one of the reasons I want to make the jump to freelancing. I currently have a full time job, and enjoy the periods where I am left to get on with my work, but all to often the non-technical users will not read error messages, and ask me stupid questions to "fix their excel". It makes it impossible to work on certain things, like learning a front end framework when you are being bugged with trivial tas…
Re: Ask HN: Remote workers, tell us how you got started
#30I started doing contracting work in Rails while I worked full time in .NET (while going onsite everyday). I also networked a lot within the local Ruby community. When I was ready to jump to Rails full time, a friend through the community was staffing up an early stage startup with remote devs spread across the city. This was a good way to dip my toes into remote work while still maintaining local connections.
After a year of that, I jumped to a larger company to join their remote team of Rails developers (currently about 10 of us are remote). Now I'm pretty adjusted to the remote lifestyle and it would be very hard to let go of it since the impact to family life is so positive.
My advice would be to do as many others have done and start with remote contracting to see how it works. Then you can either convert to full time or find another full time role later if you need benefits. However, if you can remain as a contractor I would generally advise people to do that if your financial situation allows for it.