Does anyone else do this thing when they work 90% of the time remotely and sometimes travel for a day meeting? This addresses some of the issues discussed.
This can also work for informal communication, to a degree.
121–128 of 128 posts
Does anyone else do this thing when they work 90% of the time remotely and sometimes travel for a day meeting? This addresses some of the issues discussed.
This can also work for informal communication, to a degree.
A) dating or casually fucking with coworkers. I've seen this multiple times and it never lead to a happy ending.
B) reducing your social circles to your coworkers. My sister fell into this problem where her co-workers took over the friends, and they worked, ate, did sports and outdoor activities together. She hates her job but was afraid to leave because she was about to distance from her friends. This turned ugly when point A) happened, and she left with emotional turmoil and the need for therapy.
Coworkers are a 9-5 business relation to me. I do not hand out private phone numbers because I don't even want to talk to them outside of work. When it happened, discussions rotated around work, even in the pub. Not my definition of a good time.
Earlier quoted context omitted.
Microsoft, in consulting services, yes. https://careers.microsoft.com/students/us/en/microsoft-aspir... https://careers.microsoft.com/students/us/en/job/795772/Full... Unfortunately it looks like we are back to requiring college hires to colocate for a year, even if their day to day teams are remote/distribute. Industry hires can live anywhere. Travel can be up to 100% depending on the project (although not right now…
What about jobs for non students who are self taught and working in another industry but have experience with JavaScript?
The biggest thing we (my division) look for in industry hires is an ability to interact with customers and master new skills quickly. On the technical angle, we do want to see knowledge beyond just on area of development (full-stack to cloud, o365 integration, sys admin experience, analytics work, etc...). Direct knowledge of the MS stack helps, but we hire plenty of people who know AWS and them teach them Azure (for example).
In terms of setting yourself up to get hired, I recommend trying to start a product/business. I’ve done three side companies/projects over the years, all done on nights and weekends, all of which never really did anything. I wasn’t very committed to them, they didn’t take up THAT much time, never really cost money (never had payroll, biggest expenses was a small factory order of light up dog collars at one), and I expected them to fail, but I learned a ton of new stuff to make the MVP and business systems happen.
I suspect loneliness/isolation is the biggest issue for most. At the moment it's great because I'm at home with three housemates/friends. But I think I'd get lonely pretty quickly if it was just me. Co-working spaces might solve this a bit (never worked in one so don't know how much people socialise).
Online meetings seriously suck still. It's harder to form real relationships with coworkers (some would see this as a plus, but I think it depends on the company/team culture). But the biggest change is forming trust. How do we come to trust in each other and in the mission if we never interact physically? It certainly takes a different kind of leadership.
Earlier quoted context omitted.
That's essentially what I've been doing, and I've been posting it in our daily status slack channel. I need to do a better job of adding more details, but it's a balancing act between spending time on logging work vs doing work, plus if I'm the only person on the team doing it, it looks weird.
I have a public (within the company) github repo called "worklog" where everyone can put theirs (it's by name), one file per year. I usually have 4-5 lines per day, where some days have 15 (rare, but there are those big days). I don't give the report in slack, since github has track of when stuff was committed (I commit at the end of the day), if people need it, it's on github. It's great for standups, because I usua…
Can you explain what you mean by company tax reductions? I'm confused how that relates with keeping a worklog.
Earlier quoted context omitted.
I have a public (within the company) github repo called "worklog" where everyone can put theirs (it's by name), one file per year. I usually have 4-5 lines per day, where some days have 15 (rare, but there are those big days). I don't give the report in slack, since github has track of when stuff was committed (I commit at the end of the day), if people need it, it's on github. It's great for standups, because I usua…
> It's also great for some company tax reductions, so it's appreciated! Can you explain what you mean by company tax reductions? I'm confused how that relates with keeping a worklog.
I absolutely think you lose something from lack of face-to-face contact. Some of the most productive leadership and decison-making sessions I've had came from sitting around a table or sharing a meal or a drink with a team, and going back and forth about something. Additionally, casual contact helps too. I put a couch in my office, and people would come just sit down and talk. The setting set the vibe. I had some gre…
Yep, if I had an office with a door that closed, big enough for a couch, I would also enjoy working in an office.