3 ms·
Seem like too many rules for you? Use this as a reminder about why it's important to ask probing questions whenever you interview for a job. Find out what the
by kevinconroy 13y ago
Seem like too many rules for you?
Use this as a reminder about why it's important to ask probing questions whenever you interview for a job. Find out what the culture is like and if it is a good fit for you. I know several developers who thrive with the environmental conditions listed here and would love having the company have rules to enforce these conditions. I also know several developers who would burn out.
It's vitally important to find something that's a good fit for you. No need to hate on their rules if it works for their team.
Edit: Also, if you don't like this list, what would rules does your team have in place to ensure an effective, productive remote work policy? Does it scale up with the team?
- seiji 13y agoAfter looking at it again, it isn't a crazy number of rules (some are overly demanding, like video chat), but the rules seem to exist because they are trying to codify behavior of people not completely gelled into their teams. When I've worked with teams where everybody gets along, there's always updates or chats flying around with everybody telling everybody else when and where they'll be doing what for how long without any guidelines, prompting, or pompousness.
- tghw 13y agoVideo chat seems trivial, but we found out the hard way it's pretty important for team communication.[0] Think of all the impromptu meetings you have on site, just popping into someone's office to ask them about something, pulling someone else in, and ending up having an important design discussion. It's much harder to do in a chat room. [0] As mentioned elsewhere, I was Fog Creek's first full-time remote dev.
- seivan 13y agoYay for context switches. Because we all know how much developers love being interrupted for something that is probably documented - if it isn't probably should be.