#dailyoperations — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dailyoperations, aggregated by home.social.
-
Sponsorship opportunities are available for specific topics, whitepapers, tools, or advisory insights.
Read more 👉 https://lttr.ai/AsAcW
-
Sponsorship opportunities are available for specific topics, whitepapers, tools, or advisory insights.
Read more 👉 https://lttr.ai/AsAcW
-
As AI takes on more tasks, the skill sets required for human employees are shifting.
Read more 👉 https://lttr.ai/Ao7FN
-
As AI takes on more tasks, the skill sets required for human employees are shifting.
Read more 👉 https://lttr.ai/Ao7FN
-
@aj @mike805 @zbrown @worik @timbray
#SoftwareCosts don't end at deployment.
2001: An engineer adopts a French #OpenSource bulk mailer, running on mostly unsecured SMTP. Over the years it's extended ad hoc — eventually managing security group permissions. The company grows; the #software (now at 100× planned #capacity) falls over daily.
2009: After the original engineer leaves, a contractor-turned-hire inherits it. Memory leaks fixed, algorithms rewritten that had pre-cached the universe for "efficiency." Redundancy established and tested. Deployment documented. The upstream package has been rearchitected twice since 2001, and after being pulled off the project twice to restart, the replacement engineer maps all integrations to the new architecture with a proper API — replacing direct database queries. The max supported mailing groups turns out to be tied to filesystem limits: 32k+ groups (now at 300× original capacity thanks to fixing the memory leaks and hourly restarts) each with a directory, capped by hardlink counts on the inode. A campaign encourages responsible use and better security. Archiving aligns with retention policy. And nearly daily, a manager insists someone didn't get their email, so the engineer traces it by SMTP ID.
Then the company moves to Gmail, which won't tolerate internal mailers forging external domains. Data and management migrate to Google Groups with a new front-end preserving the old permission controls. Legacy API users are tracked and urged to migrate before "the end." And the heart of corporate communication for 15+ years is decommissioned.
Every stage has real costs:
• #Maintenance
• #Upgrade
• #CatastrophicFailure
• #DailyOperations
• #Decommissioning -
@aj @mike805 @zbrown @worik @timbray
#SoftwareCosts don't end at deployment.
2001: An engineer adopts a French #OpenSource bulk mailer, running on mostly unsecured SMTP. Over the years it's extended ad hoc — eventually managing security group permissions. The company grows; the #software (now at 100× planned #capacity) falls over daily.
2009: After the original engineer leaves, a contractor-turned-hire inherits it. Memory leaks fixed, algorithms rewritten that had pre-cached the universe for "efficiency." Redundancy established and tested. Deployment documented. The upstream package has been rearchitected twice since 2001, and after being pulled off the project twice to restart, the replacement engineer maps all integrations to the new architecture with a proper API — replacing direct database queries. The max supported mailing groups turns out to be tied to filesystem limits: 32k+ groups (now at 300× original capacity thanks to fixing the memory leaks and hourly restarts) each with a directory, capped by hardlink counts on the inode. A campaign encourages responsible use and better security. Archiving aligns with retention policy. And nearly daily, a manager insists someone didn't get their email, so the engineer traces it by SMTP ID.
Then the company moves to Gmail, which won't tolerate internal mailers forging external domains. Data and management migrate to Google Groups with a new front-end preserving the old permission controls. Legacy API users are tracked and urged to migrate before "the end." And the heart of corporate communication for 15+ years is decommissioned.
Every stage has real costs:
• #Maintenance
• #Upgrade
• #CatastrophicFailure
• #DailyOperations
• #Decommissioning -
@aj @mike805 @zbrown @worik @timbray
#SoftwareCosts don't end at deployment.
2001: An engineer adopts a French #OpenSource bulk mailer, running on mostly unsecured SMTP. Over the years it's extended ad hoc — eventually managing security group permissions. The company grows; the #software (now at 100× planned #capacity) falls over daily.
2009: After the original engineer leaves, a contractor-turned-hire inherits it. Memory leaks fixed, algorithms rewritten that had pre-cached the universe for "efficiency." Redundancy established and tested. Deployment documented. The upstream package has been rearchitected twice since 2001, and after being pulled off the project twice to restart, the replacement engineer maps all integrations to the new architecture with a proper API — replacing direct database queries. The max supported mailing groups turns out to be tied to filesystem limits: 32k+ groups (now at 300× original capacity thanks to fixing the memory leaks and hourly restarts) each with a directory, capped by hardlink counts on the inode. A campaign encourages responsible use and better security. Archiving aligns with retention policy. And nearly daily, a manager insists someone didn't get their email, so the engineer traces it by SMTP ID.
Then the company moves to Gmail, which won't tolerate internal mailers forging external domains. Data and management migrate to Google Groups with a new front-end preserving the old permission controls. Legacy API users are tracked and urged to migrate before "the end." And the heart of corporate communication for 15+ years is decommissioned.
Every stage has real costs:
• #Maintenance
• #Upgrade
• #CatastrophicFailure
• #DailyOperations
• #Decommissioning -
@aj @mike805 @zbrown @worik @timbray
#SoftwareCosts don't end at deployment.
2001: An engineer adopts a French #OpenSource bulk mailer, running on mostly unsecured SMTP. Over the years it's extended ad hoc — eventually managing security group permissions. The company grows; the #software (now at 100× planned #capacity) falls over daily.
2009: After the original engineer leaves, a contractor-turned-hire inherits it. Memory leaks fixed, algorithms rewritten that had pre-cached the universe for "efficiency." Redundancy established and tested. Deployment documented. The upstream package has been rearchitected twice since 2001, and after being pulled off the project twice to restart, the replacement engineer maps all integrations to the new architecture with a proper API — replacing direct database queries. The max supported mailing groups turns out to be tied to filesystem limits: 32k+ groups (now at 300× original capacity thanks to fixing the memory leaks and hourly restarts) each with a directory, capped by hardlink counts on the inode. A campaign encourages responsible use and better security. Archiving aligns with retention policy. And nearly daily, a manager insists someone didn't get their email, so the engineer traces it by SMTP ID.
Then the company moves to Gmail, which won't tolerate internal mailers forging external domains. Data and management migrate to Google Groups with a new front-end preserving the old permission controls. Legacy API users are tracked and urged to migrate before "the end." And the heart of corporate communication for 15+ years is decommissioned.
Every stage has real costs:
• #Maintenance
• #Upgrade
• #CatastrophicFailure
• #DailyOperations
• #Decommissioning -
@aj @mike805 @zbrown @worik @timbray
#SoftwareCosts don't end at deployment.
2001: An engineer adopts a French #OpenSource bulk mailer, running on mostly unsecured SMTP. Over the years it's extended ad hoc — eventually managing security group permissions. The company grows; the #software (now at 100× planned #capacity) falls over daily.
2009: After the original engineer leaves, a contractor-turned-hire inherits it. Memory leaks fixed, algorithms rewritten that had pre-cached the universe for "efficiency." Redundancy established and tested. Deployment documented. The upstream package has been rearchitected twice since 2001, and after being pulled off the project twice to restart, the replacement engineer maps all integrations to the new architecture with a proper API — replacing direct database queries. The max supported mailing groups turns out to be tied to filesystem limits: 32k+ groups (now at 300× original capacity thanks to fixing the memory leaks and hourly restarts) each with a directory, capped by hardlink counts on the inode. A campaign encourages responsible use and better security. Archiving aligns with retention policy. And nearly daily, a manager insists someone didn't get their email, so the engineer traces it by SMTP ID.
Then the company moves to Gmail, which won't tolerate internal mailers forging external domains. Data and management migrate to Google Groups with a new front-end preserving the old permission controls. Legacy API users are tracked and urged to migrate before "the end." And the heart of corporate communication for 15+ years is decommissioned.
Every stage has real costs:
• #Maintenance
• #Upgrade
• #CatastrophicFailure
• #DailyOperations
• #Decommissioning -
Companies Need to Build Strength into Daily Work
https://newsletter.tf/companies-build-strength-daily-work/
Businesses must become stronger to handle problems. Experts say companies need to build resilience into how they work every day to stay successful.
#BusinessResilience, #CompanyStrength, #DailyOperations, #ProblemSolving, #FutureReady
-
Companies Urged to Embed Resilience in Daily Work
https://newsletter.tf/companies-build-strength-daily-work/
Companies need to build resilience into their daily work to handle challenges and stay strong.
#BusinessResilience, #CompanyStrength, #DailyOperations, #ProblemSolving, #FutureReady
-
Companies Need to Build Strength into Daily Work
In today's changing world, companies face many challenges. Experts say it is important for businesses to build strength into their daily work. This helps them handle problems and keep going.
https://newsletter.tf/companies-build-strength-daily-work/
#BusinessResilience, #CompanyStrength, #DailyOperations, #ProblemSolving, #FutureReady
-
Artificial Intelligence (AI) is no longer a distant concept; it's now a tangible part of our daily operations.
Read more 👉 https://lttr.ai/Al2V5
