![]() ![]() Why would your company be the one exception? # The understandable fear of change What I’m asking is that you would at least be honest with yourself and your employees, and take a long hard introspective look at why you don’t think remote work is good for you. Still, pretending that “it’s just not for us” is a bullshit excuse. Change is difficult, and frightening, and scary. I sure would be afraid as heck too if I was managing dozens of employees. Managing a company is hard and stressful. And don’t get me wrong, I’m not throwing any stones here. The truth is that CEOs and CTOs are afraid. “We don’t have the infrastructure for remote work” - what prevents you from putting it into place? Webdev is one of the easiest jobs to migrate to remote. ![]() ![]() “It’s great, it’s just not for us” - For a web development company, this is most of the time just not true. I heard all the excuses from CEOs and CTOs. Worse, how many companies had great remote work success during the pandemic, but will shift back to mandatory on-site work once this is all over? Even worse, many did not even wait for the end of the pandemic before doing so. How many companies were forced into remote work by the pandemic, and realized it was actually great? How many of them used to categorically refuse remote work beyond maybe a couple days a week? And why was that? A wisdom that companies consistently refuse to apply. What works somewhere might obviously not work somewhere else.īut there is wisdom in those books, and on this approach to work and to life. # The understandable fear of consequencesĭon’t get me wrong, I’m not saying every company should copy-paste the Basecamp model. The problem with Basecamp books is the following: it’s great advice, everyone knows it, everyone agrees on it, but no one actually wants to apply it. Their company culture? The best! No, we won't change ours. Basecamp’s advice on project management? It’s great! We won’t change how we do things though. Remote work? That’s amazing, and great, and the future. Most of the CEOs and CTOs I talked to actually read most Basecamp books.Įveryone I talked to, and I do mean everyone, agrees with the amazing content of those books, and on the necessity to follow such great advice. That’s when I realized something peculiar. “Shape-up”, “Remote work”, “Rework”, “It doesn’t have to be crazy at work”, “Getting real” - All great books filled with great advice. They wrote a series of equally famous entrepreneurship books, advocating for a shift in the industry towards a culture closer to their own. # What are the Basecamp books?īasecamp is a famous project management startup. Of course, I would often quote the famous "Basecamp books". I discussed with CEOs and CTOs about their visions for business, project management, and company culture. All successful businesses, the crème de la crème of the FrenchTech, looking for experienced developers to consolidate their tech teams. Last year after finding myself between two jobs, I interviewed with a bunch of start-ups in Paris. # The problem with the basecamp books, or Why our work culture sucks. Test all your GET routes in rails with 20 lines of code.Filter Anything in a Rails request in 10 lines of code.Upload Files from Vue.js to Rails with ActiveStorage.The Marie Kondo guide for the Clean Developer.Diversity in the workplace: the emperor has no clothes.The understandable fear of consequences.The Technical Debt explained with a kitchen analogy.Explaining Ruby's Singleton Class (Eigenclass) to confused beginners.How to Start Learning CSS without hating yourself.Dramatically increase your productivity with Atomic Git Commits.□ Productivity and Well-being, A summary of what works. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |