Hacker News Reader

Comment by sdfjkl | Hacker News Reader

After about 20 years of computer stuff, I've found a new interest - sailing. I spent most of the money gained from computer stuff on a boat, learnt how to repair it and sail it (repairing being the far more extensive subject), and am about to set off for a long trip. While doing this I've been using my newly gained skills and combined with my existing skills (computers, networks, electronics) did some work in the marine sector (mostly for the odd dinner, some of it paid) - turns out boats are full of special purpose computers and most of the "specialists" fixing them are uhm, not the best. My skills found quick appreciation. Might continue down that road once I run out of money.

I guess my advice is to do a bunch of things and see what you enjoy, new opportunities will happen as you do. Having an IT background is helpful almost anywhere, and more valued outside of core IT areas.

View on HN

Having an IT background is helpful almost anywhere, and more valued outside of core IT areas

I tested this theory by getting an IT job at a food company. I was treated way better as an employee but the tech was too old (almost treated as the factory machinery). It was painful to leave that job but I felt I wouldn't be able to get a job anywhere else, that my skills would stagnate. I guess this constant anxiety is another argument for quitting IT.

Maybe working in non-pure IT setting AND being in charge of tech might be the answer. A small consulting company for non-IT companies comes to mind (if clients trust you, new exciting tech wouldn't be so difficult to introduce).

Check out Hold Fast by Moxie Marlinspike, "…a video zine three friends and I made about finding a derelict sailboat, fixing it up, and sailing from Florida to Haiti." https://vimeo.com/15351476

You ever watch svseeker on youtube? He's a DBA building a boat; I've been watching him for years now and he touches on how his job is just a means to an end in his goals.

Nope. I do watch a few sailing vlogs though: DrakeParagon, Untie the Lines, La Vagabonde and Sail Life. Each have a very different approach to the subject, ranging from extensive preparation and fitting redundant systems (Drake), to buying a beat up boat and just casting off on a round the world trip, figuring it out as they go (La Vaga).

Can confirm somewhat. Handle IT for various law firms and get to build sites and come up with solutions with any stack I believe fits best. Of course, I lay out pros and cons with attorneys but usually they defer to my judgement. Lots of pressure but I enjoy the freedom.

Where'd you learn how to sail?

In the English channel, off the coast of Sussex. I learnt programming by doing it and then reading about it. I learnt sailing by reading about it and then doing it. This is because when programming it hurts less when you screw up, when sailing it's best to have a basic understanding of things before you set out so you're not a risk to yourself and others :)

The actual sailing bit isn't really very difficult. If you have a basic understanding of physics, you'll soon grok it. Navigation is a bit more involved, but not for a programmer, especially if you've done any GIS coding and remember your basic geometry. Oh, I also had to do a very simple radio exam.

Now picking the right boat, that is difficult as hell ;-)

I've always wanted to sail, but everyone I know who's actually done it said "you think it's going to cost X, but once you've spent X you keep spending and spending."

That is certainly true for boat ownership (although you can save and learn a lot by doing everything yourself). But you don't have to buy a boat just to sail. Plenty around already!

Reply on news.ycombinator.com