I worked remotely for 20 years, as developer, team lead and manager. The number one advice - communicate. It's better to overcommunicate than undercommunicate.

I worked remotely for 20 years, as developer, team lead and manager. The number one advice - communicate. It's better to overcommunicate than undercommunicate. A mediocre developer beats a genius if the mediocre one communicates and genius gets his task and goes under water for weeks and then suddenly delivers the masterpiece. I've seen so many such masterpieces not needed anymore after weeks of silence. If you ever question yourself: "should I comment on this JIRA ticket before I complete it, or not?", don't hesitate, comment. Don't even think about it. If miracle will happen and you'll actually overcommunicate - they will tell you. Number two: if you have a family, establish a comfortable working environment, define comfortable working hours and "go to the office". You're away, you can't "hey, could you please pick up some groceries, if you're at home anyway?". You're not at home, you're at work. It's hard for family, could be hard for you too. Especially if you have small children, your wife is very tired dealing with them, it would be very tempting for her to go out with girls while you babysit. The next thing which will happen is your production goes down, you're called to the meeting with all the brass, your ass is on fire, because it seems your commit caused the outage, you spend 3 hours on webex and phone and computer, your baby shits her pants couple of times, paints the whole room with shit, and then sits in the middle of this horrible mess crying because you forgot to feed her on schedule. And you do not hear her, because you're in the headphones where 20 people talk at once. (true story, btw).