1. 13

    The cynical (but true) answers:

    1. Work on “greenfield” projects. Never maintain anything. The first line written in a module is always 100000x more code than an empty file.
    2. Promote whatever you write. Any person you get to use your code is a justification to continue working on that.
    3. Write your own requirements. It is easier to meet deadlines if you are supplying what you already have.

    The true (but hard) answers:

    1. Do not develop fast, develop correctly.
    2. Code, like art, is never finished, it is only abandoned. Think about the person who is going to extend/modify your code after you abandon the project.
    3. Get a lot of feedback from the person that is going to sign off whatever you ship. They are the ones that can say if you “shipped shit” or you did not. Much more telling than JIRA, in the end.
    1. 2

      When I read the title I thought you were looking for languages that were designed for remote work, but on opening the question I saw you are looking for languages that are in demand for remote work …

      I actually think that the former question is more interesting. What would a language look like, if it was designed specifically to address remote work?

      And to answer your question, I was working two years in remote mode, for a team that was around 600 km away from me. We used Python almost exclusively, but it was not web development: it was a backend service for a mobile client. I love Python very much, but that experience showed me that using it in a distributed team requires a lot of discipline and a lot of code conventions. It is not easy to convey complex requirements over a phone line.

      1. 1

        You’re right, that would be a more interesting question. Slightly less practical for my present need though :)