71–80 of 194 posts
Earlier quoted context omitted.
If you’re building software there’s really no reason you have to share working hours with anyone. When I'm doing UI work, it's far more efficient to have a real-time session with a designer rather than multiple rounds of email/Figma comments.
Then one of you needs to work on your written communication skills.
Earlier quoted context omitted.
Maybe this works as an IC that has no collaborative aspect to their day-to-day but as an IC leader async adds material pauses and latency into projects. If everybody is ok with everything taking longer at the start and end of projects then cool (the middle implementation phase is less impacted) but taking a day to answer a question that could have taken minutes is not a bonus.
Asking a quick question that only takes a few minutes is a nice bonus for you, but for the person you asked it was an interruption that cost them 20 minutes or more of focus. That might be ok if the person you asked has a job that is designed to be interrupt–driven (aka a manager), but if this was another engineer then this wasn’t a net benefit. But the other side of the coin is that if you do need to ask a question…
Some types of tech work well with remote, largely unalignable staff. Some don’t. I’m finding that where I can build small modules, by myself, that allow lots of flexibility to make final integration possible, I’m getting a lot of work done. When I need to collaborate with a bunch of people and get small pieces of code landing in different places before I can start to see results, then I’m finding the remote angry ner…
There is so much nuance lost in pure digital (especially email/chat but also video calls) that it puts up communication barriers/friction. As a result people communicate less, or even "come out swinging" (i.e. angry/forcefully) if they feel their work/decisions/etc are being questioned.
I am sure pure remote works well when requirements are 100% understood, there is a perfectly groomed list of prioritised bugs/features to fix/implement, and the design/architecture is both correct (now and in the future) and understood by all engineers. If not then I don't understand how you can easily and efficiently resolve these problems in a remote way without taking hours and hours or even days and weeks for chat or stilted video calls. Sometimes nothing beats just getting in a room with everyone for 90 mins and talking things through around a whiteboard or whatever.
Earlier quoted context omitted.
Maybe this works as an IC that has no collaborative aspect to their day-to-day but as an IC leader async adds material pauses and latency into projects. If everybody is ok with everything taking longer at the start and end of projects then cool (the middle implementation phase is less impacted) but taking a day to answer a question that could have taken minutes is not a bonus.
Asking a quick question that only takes a few minutes is a nice bonus for you, but for the person you asked it was an interruption that cost them 20 minutes or more of focus. That might be ok if the person you asked has a job that is designed to be interrupt–driven (aka a manager), but if this was another engineer then this wasn’t a net benefit. But the other side of the coin is that if you do need to ask a question…
Earlier quoted context omitted.
I like the concept of async work but I’m also scared of how transactional that would make work. Most companies that preach async now have a very strong, “friendly” culture. If async catches on more widely I’m worried it would be the final push to make software development purely transactional and performance/pay would be directly tied to metrics. I enjoy the human component of work. I don’t like _all_ of my coworkers…
I like most of my coworkers and are friends of some offline. But I see work transactional by definition.
Earlier quoted context omitted.
I am beginning to think that many remote developers will eventually become 1099 contractors who can pick up random gigs. Because let’s be honest, the reason most of these folks are doing this is because they don’t give a crap about the specific company or anything like that. They just want to build cool shit that other people spec out. As long as the pay is competitive one day they might be building a healthcare mobi…
Is one supposed to be anything but a mercenary? Should I believe in the product for the sake of making the CEO a billionaire? People should care iff they are given meaningful equity, as in life changing, otherwise they should be professional, like accountants and lawyers, but jump ship whenever it’s convenient.
Earlier quoted context omitted.
Asking a quick question that only takes a few minutes is a nice bonus for you, but for the person you asked it was an interruption that cost them 20 minutes or more of focus. That might be ok if the person you asked has a job that is designed to be interrupt–driven (aka a manager), but if this was another engineer then this wasn’t a net benefit. But the other side of the coin is that if you do need to ask a question…
Seems like there are two very different modes of development being mentioned here. You seem to be describing a mode where you just need to concentrate and bang out your lines of code for the day. The previous comment seems to be referring to creative, collaborative development. The industry probably needs both, but I’m much more personally interested in the latter, and I’m worried that async/remote is disastrous for…
Bad analogies are not very persuasive
Of course this is happening. I’m coming up on year 10 of working remotely, and year 2 of completely async. The only forced-commute job I ever had was for 6 months right out of college. I’ve been preaching remote work for almost the entire time I’ve been doing it. I thought it would catch on much sooner, but it’s here now. I think async is the next thing that will happen. If you’re building software there’s really no…
Incompetent engineers need to share work hours, otherwise they will get stuck and not get much done if nobody has overlapping times to help them. Not all engineers are high caliber.
Earlier quoted context omitted.
I am beginning to think that many remote developers will eventually become 1099 contractors who can pick up random gigs. Because let’s be honest, the reason most of these folks are doing this is because they don’t give a crap about the specific company or anything like that. They just want to build cool shit that other people spec out. As long as the pay is competitive one day they might be building a healthcare mobi…
Is one supposed to be anything but a mercenary? Should I believe in the product for the sake of making the CEO a billionaire? People should care iff they are given meaningful equity, as in life changing, otherwise they should be professional, like accountants and lawyers, but jump ship whenever it’s convenient.