Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (64)

Strategic activity mapping for software architects May 25, 2025 On the role of Distinguished Engineer and CTO Mindset Apr 27, 2025 The future is bright Mar 30, 2025 2024 Reflections Dec 31, 2024 My giant follows me wherever I go Sep 20, 2024 Are developer jobs truly in decline? Jun 29, 2024 Some thoughts on recent RTO announcements Jun 22, 2023 One size does not fit all: neither cloud nor on-prem Apr 10, 2023 Should today’s developers worry about AI code generators taking their jobs? Dec 11, 2022 Working from home works as well as any distributed team Nov 25, 2022 Why you should question the “database per service” pattern Oct 5, 2022 Good developers can pick up new programming languages Jun 3, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Peloton could monetize these ideas if they only listen May 15, 2022 Good idea fairy strikes when you least expect it May 2, 2022 Best practices for building a microservice architecture Apr 25, 2022 TypeScript is a productivity problem in and of itself Apr 20, 2022 In most cases, there is no need for NoSQL Apr 18, 2022 A year of COVID taught us all how to work remotely Feb 10, 2021 Making the best of remote work - Coronavirus blues Mar 16, 2020 TDWI 2019: Architecting Modern Big Data API Ecosystems May 30, 2019 Using Markov Chain Generator to create Donald Trump's state of union speech Jan 20, 2019 The religion of JavaScript Nov 26, 2018 Let’s talk cloud neutrality Sep 17, 2018 Fixing the Information Marketplace Aug 26, 2018 What does a Chief Software Architect do? Jun 23, 2018 I downloaded my Facebook data. Nothing there surprised me. Apr 14, 2018 Nobody wants your app Aug 2, 2017 Node.js is a perfect enterprise application platform Jul 30, 2017 Design patterns in TypeScript: Chain of Responsibility Jul 22, 2017 Singletons in TypeScript Jul 16, 2017 Rather than innovating Walmart bullies their tech vendors to leave AWS Jun 27, 2017 Architecting API ecosystems: my interview with Anthony Brovchenko of R. Culturi Jun 5, 2017 TDWI 2017, Chicago, IL: Architecting Modern Big Data API Ecosystems May 30, 2017 Collaborative work in the cloud: what I learned teaching my daughter how to code Dec 10, 2016 Don't trust your cloud service until you've read the terms Sep 27, 2016 In search for the mythical neutrality among top-tier public cloud providers Jun 18, 2016 What can we learn from the last week's salesforce.com outage ? May 15, 2016 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 JavaScript as the language of the cloud Feb 20, 2016 OAuth 2.0: the protocol at the center of the universe Jan 1, 2016 Our civilization has a single point of failure Dec 16, 2015 IT departments must transform in the face of the cloud revolution Nov 9, 2015 What Every College Computer Science Freshman Should Know Aug 14, 2015 Ten Questions to Consider Before Choosing Cassandra Aug 8, 2015 On Maintaining Personal Brand as a Software Engineer Aug 2, 2015 The Three Myths About JavaScript Simplicity Jul 10, 2015 Book Review: "Shop Class As Soulcraft" By Matthew B. Crawford Jul 5, 2015 Attracting STEM Graduates to Traditional Enterprise IT Jul 4, 2015 Your IT Department's Kodak Moment Jun 17, 2015 The longer the chain of responsibility the less likely there is anyone in the hierarchy who can actually accept it Jun 7, 2015 Big Data is not all about Hadoop May 30, 2015 Smart IT Departments Own Their Business API and Take Ownership of Data Governance May 13, 2015 The Clarkson School Class of 2015 Commencement speech May 5, 2015 Building a Supercomputer in AWS: Is it even worth it ? Apr 13, 2015 Ordered Sets and Logs in Cassandra vs SQL Apr 8, 2015 What can Evernote Teach Us About Enterprise App Architecture Apr 2, 2015 Microsoft and Apple Have Everything to Lose if Chromebooks Succeed Mar 31, 2015 Software Engineering and Domain Area Expertise Nov 7, 2014 Wall St. wakes up to underinvestment in OMS Aug 21, 2014 Software Engineers Are Not Doctors Aug 3, 2014 Cassandra: Lessons Learned Jun 6, 2014 Java, Linux and UNIX: How much things have progressed Dec 7, 2010 Eminence Grise: A trusted advisor May 13, 2009

Working from home works as well as any distributed team

November 25, 2022

I worked remotely in some shape or form for the past fifteen yearsMost of my career involved remote work.



A blanket statement like "Elon Musk Eliminated Remote Work Because Working From Home "Doesn't Work"" is a logical fallacy in a modern work environment. "Work from home" is not inherently different from "remote work," which in turn is no different from "distributed teams." If working from home doesn't work, then neither do remote work or distributed teams. And yet, as of now, Twitter has dozens of offices in Asia, Europe, North America, Oceania, and South America. Tesla has 16 offices throughout the US alone.



Luay Rahil starts his article with the immediate logical fallacy:




If remote work is the answer, why are most tech companies laying off people?




Could the problem have more to do with the flawed business models at most tech companies rather than remote work? By this logic, if remote work is the answer to flawed business models, then all managers should let everyone work from home rather than solve their failing business models.



Luay continues:




Musk doesn't mind if you want to work from home, he wants you to work at least 40 hours at the office, and you can work another 40 hours at your house if you desire.




My advice to any self-respecting software engineer: if your manager says something like that, get a new job. I once worked for a company with such a culture — trust me when I say it's not worth it.




Elon Musk puts an enormous number of hours into his work, famously working over 120 hours per week and sharing his opinion that founders need to work 80-plus weekly.



He defends his extreme devotion and dedication to his work by saying, "If it wasn't for me working 120 hours per week while everyone" at Tesla worked 100 hours per week at times this year as Tesla would have failed."




The future is yet to unfold. Tesla pioneered the EV market and paved the way for competitors, and there is no doubt about that. As of 2022, Tesla is one of many players on the market, and consumers have increasingly broad choices now. Tesla stock lost almost half its value this year.




So before you criticize Musk's stand towards remote work, take some time to examine his successful business records and see how other companies are faring against him. For example, Salesforce Chief Operating Officer Marc Benioff stated that he has a specific plan to cut many jobs based on performance, and if I have to guess, most of these people are working remotely.




I would have stopped the above statement at "based on performance" and avoided making wild guesses and using "these people" to describe otherwise loyal and high-performing employees. Salesforce products enable telecommuting in the first place.



Luay continues:




So, after examining their profit and loss statements, many CEOs are coming to the same side as Elon Musk. For example, Netflix CEO Reed Hastings doesn't "see any positives" to working from home. Hastings told Wall Street Journal, "Not being able to get together in person, particularly internationally, is a pure negative."




Netflix has a problem with customer retention, not working from home. Just like Tesla is no longer the only EV-maker out there, Netflix is not the only movie streaming service, and there are others with competitive content and better options. Forcing Netflix employees to come back to the office won't fix the fact that Netflix is not as unique of a content provider as they once were — just like Tesla is well on its way to not being special.




It is purely negative because you can't build a sustainable company working from home. Parag Agrawal, the old Twitter CEO, allowed his employees to work from home, and Twitter was losing $4 million per day, so stop talking about productivity.




Twitter was losing millions of dollars per day due to an outdated business model and lack of vision that had nothing to do with where employees worked.




Apple's chief executive officer, Tim Cook, told his team to come back to work, "I hope everyone is feeling as energized as I am and that you are looking forward to seeing your colleagues in person again in the weeks ahead. I can't tell you how much I am looking forward to being together again."



Cook explained that he wants people in the office on Monday, Tuesday, and Thursday and work "flexibly" on Wednesday and Friday. Of course, some people are mad, but Cook doesn't care, and his company is doing better.




Ah, now we are coming to the crux of the matter: flexibility and personal relationships most people seek, not some hard choice between full-time telecommuting or office work. I will come back to this in a moment, right after I dissect the remainder of Luay's post.




James Dimon is an American billionaire businessman, and the JP Morgan Chase CEO doesn't see any value in remote work either.




JP Morgan has offices in India, United States, France, Germany, Italy, Spain, Switzerland, and many other countries. If "remote work" didn't work for JP Morgan neither would geographically distributed teams and certainly not outsourcing, and yet somehow JP Morgan strives — better than Tesla, I should add if you compare their recent stock performances.




Some of you will say that technology allows us to communicate with each other efficiently. I tell you this, "Stop confusing digital connections with real relationships. Nothing can replace a real conversation with someone you care about, and if you don't care about the people you work with, it is time for you to find another job."




I will revisit the concept of "real relationships" momentarily. If digital communications don't work for you, then neither do offices across timezones and geographical locations nor outsourcing.




It is harder for companies to build and transfer institutional knowledge when employees are working 100% remotely. So, as soon as someone leaves, the organization will suffer greatly.




Again, this is another logical fallacy. If someone is working for a US company out of their Hyderabad office, for example, this person is in fact, working 100% remotely. How is that different from the same person working out of their home office?




Another benefit of spending time with coworkers in the office is that it strengthens the sense that you share a common mission. But, again, if you don't feel a sense of belonging, quit your job. You deserve better.




The crux of the matter is the human need for meaningful connection and a sense of belonging, which brings me to the topics I promised to circle back to.



There is scientific evidence that our social network is a network of triads, and the largest median number of meaningful relationships a human brain can maintain is around 150. It means that any meaningful sense of belonging at work is based on no more than being around two closest colleagues (to form a triad), and the largest meaningful, cohesive team can be at most 150 made up of 30 interconnected triads.



In a purely "remote" company, such as a startup, it makes sense to have clusters of 3-4 employees in each geographical location who can meet regularly in person and collaborate. A large company can have centers of excellence larger than that, of course, but any meaningful in-person relationships that yield innovation and spark new ideas will involve gatherings of at most three or four.



Since we know remote work does work, and a sense of belonging requires a clique of no more than 3-4, and there is evidence that meetings much larger than that are unproductive, there is no technological, managerial, or sociological reason why flexible work arrangements and telecommuting (including working from home) cannot work. In fact, remote work is so effective that Luay Rahil also wrote a post about how remote is so effective that all knowledge will be outsourced to cheap countries. In other words: remote work works.