Hacker News new | ask | show | jobs
by fatihacet 3065 days ago
I am working remotely for the last 5 years and currently working at GitLab which is a remote only company. Here are my humble advices for you.

- Always check in with your manager. Let them know your status before they ask.

- Make sure to deliver your stuff on time. If you can't do it, let your manager and other related team members before it's too late. Explain the reasons why you failed and learn your lessons. Try to avoid the same situation happen to you again. If it's your fault, accept it and move on. Try to do better next time.

- Share big and important updates with your team. It can be something simple like "Hey everybody, I did this and here you can take a look". If you use Slack you can post this to a public channel or you can send it via email.

- Add screen recordings to your Merge Requests. You can use Gif tools like, LICEcap or recordit.co.

- Be responsive to your mails, issues, TODOs, Merge Request comments etc.

- Always make sure that you have assigned with something to work on and you know what to do next.

- Try to be available when someone needs your help.

- Last one, maybe the most important one is doing a weekly meeting. If you don't have a weekly team meeting, you should tell your manager to start doing one. It's the most easiest and productive way to share important updates and sync up with other team members. At GitLab, we have a shared Google Doc and everyone can add their items to that list. Then people talk about their items then pass it to next person. You can also do daily stand-up meetings. It should be something quick and every team member should have 1-2 minute to talk about their updates and answer the questions below. You can also do this in async way by posting answers of these questions to a Slack channel.

I. What did you work on yesterday?

II. What will you work on today?

III. Is there any obstacles?

1 comments

I wish some of my remote team would read this message. Though I'm not sold on this one:

- Add screen recordings to your Merge Requests. You can use Gif tools like, LICEcap or recordit.co.

Also, that last meeting you talk about is usually called a stand-up meeting and when using Scrum project management it is supposed to be every day. I don't think I've ever heard of it being done once a week. Not that it is abad thing, I'm curious if some other companies are only doing it once a week.

Security firm here, we do weekly meetings solely because our tempo is different. An individual researcher, analyst or pentester might have his own engagement to take care of that is relatively independent.

For us, weekly meetings are more of a phoning home than a game plan meeting. I can see situations in which stand up meeting might be useful, -> when there is mutual overlap between engagements.

In answering your question though, the need for stand up meetings, imo, is dictated by the size of the group working on the same project.

> I wish some of my remote team would read this message.

To be fair most workers are never going to do on their own what the business wants or what is good for the team. They don't understand it well enough as they are neither business people nor managers and it's not up to them.

I know it's four days later but this might be one of the most condescending arrogant things that I have every read on Hacker News.

Really? Business is so magical that someone with a Computer Science degree couldn't possibly understand business.

As a manager or CEO it is your job to make sure everyone in the company understands the mission and what is needed to get there. And that everyone is empowered to act on a daily basis to move that mission forward.

A leader realizes that the people on their team have insights and knowledge that they do not. A good leader empowers not dictates. You sir, have some lessons to learn.

There is a reason so many great companies are founded by software engineers. Based on your logic those should all fail because Software Engineers should just stick to coding not thinking about what is best for the business.

Yep I don't feel comfortable with that one too - I much prefer the idea of virtually attending scrums (just make sure they are brief!)