hiddentao

Happy to say that as of now no new "Company confidential" job ads will appear on the site (existing ones will still remain until they expire). Company name and URL are now mandatory.

Just saw that myself, thanks for noting it. One feature I want to add at some point is the ability to "flag" a job ad as either misleading or inappropriate - but this would have to be implemented in tandem with basic CRUD functionality, in case the creator made an innocent mistake. In this case I shall contact them and find out whether the ad criteria needs to be adjusted.

That's a really good idea, thanks :) it's on our todo list now.

Yeah, sorry about the lack of search and the hotlinking. I wanted to build this quickly and validate it before going any further. As for the job types, yeah I know - I have to admit that when I build this job board I initially had remote web developers such as myself in mind.

Hi, what version of FF are you using? And thanks for the feedback. Yep, search is on the todo list.

"RemoteCoder" sounded shorter and sweeter as a name which is why I went with it. So it was really about marketing, no offence to developers/programmers (I'm one myself after all ;)

Very interesting points. To be honest I created this board out of similar frustrations (applying for a "remote" job ad only to find out that it meant within the USA only). I like your point about how job listing should work both ways - I think that SomewhereHQ comes close to doing this.

Also, good job on getting RemoteTechJobs.eu up and running. Another reason I built the job board (and built it quickly in 2 weeks) was to force myself to get something done and ship it on time. It's great to see other people doing the same.

Very sorry about that, should now be fixed and working.

Thanks, this should now be fixed.

Thanks. It's good if companies are respecting that checkbox. On other job boards I've used (e.g. weworkremotely) remote often turns out to really mean "remote within country X" or "telecommute". This was one of the frustrations that led me to build this board (plus, I thought it would be a fun thing to build!).

Thanks, that is on the todo list. I was trying to get this done in a short space of time - and because the initial list of jobs was going to be short I felt that I didn't need it for now.

Very true. I was limited by time and also didn't want to add in more integrations until I obtained some feedback. At the moment RemoteCoder is a small experiment - now that I'm getting feedback I can take it in a more fruitful direction than I would have been able to otherwise.

Thanks, this should now be fixed.

Very true. I also have another angle I wish to pursue with respect to this. But it's good to know that there's interest in such a job board. Furthermore, my focus with this board is on developers and developers only. WeWorkRemotely focus more broadly than that.

It's focussed purely on developers (hence the Github integration that some jobs require) and it provides clarity on whether a job is truly remote anywhere or remote within a specific region.

Thanks, you're right. I was aware of this issue when I was building it, and I do have a few ideas regarding traffic building which may or may not work.

For now I just want to see if such a job board would be of any interest in the first place, especially given that there are other job boards (e.g. nomadlist, weworkremotely) that overlap it. I really wanted to see if some the differentiating factors (e.g. Github auth, remote region specificity) would be of interest to anyone.

Sorry, that seems to be a problem on other similar job sites too. I haven't yet thought about how to solve that problem, any ideas are welcome! Plus, with contract work I've sometimes had to negotiate with a client - I thought it would be better to therefore leave that detail to when the employer is having a conversation with the candidate.

One of the key differentiators is the ability to see which jobs are truly remote (like nomadlist does) vs. remote within a particular region. The other is that this job board is focussed solely on coders (whereas weworkremotely also caters for designers, business admin, etc). Hence the optional Github authentication.

Thanks. Yep, that's on the todo list. Time was short and I predicted that initially there wouldn't be so many jobs so I prioritised other features over search.

You only need one if the employer has specified that you need one when creating their ad. It saves them having to ask you for your id in your application - better yet, it allows us to verify your github profile for them and even send them a short-line summary of your work.

I added that in for 2 reasons: 1) I usually get client work based on my github profile, i.e. they like what they see there, and 2) nowadays almost every job ad I see looking for remote web developer asks for a github id.

I appreciate that not everyone has or even cares about Github which is why it's an optional item when posting an ad. However, one of the differentiating factors of RemoteCoder is that it provides for tight Github integration in case an employer is interested in your github work. But perhaps this feature should be off by default? (at the moment it's on by default).

Yep, I always knew this would be a problem. Nevertheless I felt it would be worth putting it out there to gauge the interest in something like this. I'm happy to say a lot of people are interested (and new jobs are showing up on the board too) so I think there's scope to solve this problem. I have a few other ideas with respect to increasing traffic which I hope to apply to it in the near future.

Sorry about that! I built this in 2 weeks in between doing other stuff (travelling, attending events) so I had to make some hard choices about the essentials. And editing was left out of that. However, I'm surprised the actual rendering looks that different - which job ad did you post? (see my HN Profile for the email). I can edit it manually for you.

Glad you like it. I've been working independently for about 5 years now and never plan to go back unless it's something really special (maybe SpaceX's Mars project :). Even then I'd want to be able to work remotely.

Point taken regarding company anonymity. Seems a lot of people have issue with that. I added that "feature" in just because I saw it on other jobs sites (e.g. authenticjobs) and felt that not having it would exclude certain potential companies from posting an ad. On reflection though, I agree with you that knowing which company you're applying to would be better so I'm going to make company information mandatory from now on.

Hi, this is my first potentially revenue-generating project, that I built in 2 weeks. There are still a few features missing (e.g. CV upload) but the general functionality is there - including the Github authentication. Would love to hear what people think :)

SEEKING WORK: Remote (from the UK, currently in Taiwan)

I am a full-stack web developer with 9+ years experience backed by a Computer Science degree from Imperial College London. I mainly work with Javascript/Node.js (as well as Angular, Ember, Bootstrap). I also have some experience doing continuous deployment setups (using Docker, Jenkins, Drone, etc).

In the past I've worked in C++, Java, PHP and Python - I can quickly pick up new technologies and tools as and when needed.

Some of my work:

* https://showca.se - Client web app, node.js, Bootstrap

* http://purveu.com - Client web app, node.js, Ember

* http://squeljs.org - Open-source project, node.js and browser

* http://waigojs.com - Open-source project, node.js using ES6 generators

Contact me: ram@hiddentao.com | https://github.com/hiddentao | http://uk.linkedin.com/in/hiddentao

On the topic of using callbacks, promises + generators will enable you to do the same job with almost the same level of performance (see http://spion.github.io/posts/why-i-am-switching-to-promises....) whilst avoiding callback hell and having to perform error handling in multiple places.

A good Promise library (like https://github.com/petkaantonov/bluebird) even provides mechanisms for writing functions that both return Promises as well as accept callbacks, allowing your API client to choose how they wish to use it.

Also, beware of making a function "asynchronous" by simply having it accept a callback parameter, e.g.:

  function myFunc(v, cb) {
    someOtherObject.v = v;
    cb();
  }

  myFunc(5, function(err) {
    if (err) return console.error(err);
    console.log('call done');
  });

  console.log('call started');

In the above code, you'll see "call done" before you see "call started" because myFunc() isn't really functioning asynchronously.

This is yet another reason to use a good Promise library like Bluebird, as it ensures that even if you wrap a synchronous function inside a Promise the resulting execution will flow as if it was asynchronous.

Great work. I love seeing how the renderer quickly draws the basic details and then ever more slowly over time fills in the finer points. I know that's pretty much how ray tracing is working but still cool to see.

And in looking through the discussion around this article (see link in parent) they seem to view separation of ethnicities (into homogenous countries) as the solution to their problems.

I agree with the points people here have brought up. For my part, I think it would be good to at least have a seamless OpenPGP interface with at least signing enabled for all mails (if encryption not always possible), and I'm working on https://autonomail.com to that end. Other folks (like https://whiteout.io) are also working on similar solutions.