Today, you’ll find a number of items that you should take the time to read through. Are app rewrites a bad idea? How can you be secure in the cloud? Why is there a big fork in the Linux world? When is autoscaling bad? Check out more below.
[article] 5 Rituals To Keep You Happy All The Time. “All the time” is a tall ask, but I liked the points Eric made in this post.
[blog] Google Cloud Platform Security Checklist : Part 6/7 — Data Security. This offers a good look at the range of things you need to consider when securing data in any cloud.
[article] 6 Ways to Become a More Collaborative Leader. How to switch from a crusader to a collaborator. However, I suspect there are seasons where the former is needed.
[article] Anthropic releases Claude 2, its second-gen AI chatbot. I like what the Anthropic folks are up to!
[blog] New ways for Google Cloud partners to develop and demonstrate deep product expertise. Here’s a new, useful program to reduce uncertainty about who has which expertise.
[article] You can’t stop the business, or why rewrites fail. Rewrites are tricky, build a new-next-to-old is tricky, and modernization piece by piece is tricky. Basically, anyone promising an easy solution is making things up!
[blog] Buffer workflow executions with a Cloud Tasks queue. Buffering is a key strategy for modernization when you might be introducing load that existing components can’t handle. Cloud Tasks is a pretty cool solution for protecting apps from HTTP surges.
[article] Why SUSE is forking Red Hat Enterprise Linux. Seems like a big deal. People choose a given distro for a number of reasons. I look forward to a time when fewer people need to care! More from SUSE.
[article] 7 Ways to Future Proof Your Developer Job in the Age of AI. You can’t future-proof yourself, but “learning how to learn” and maintaining a growth mindset will give you an edge.
[article] Downsides to using cloud autoscaling systems. Autoscaling is a primary reason to use cloud in the first place, but you can get in trouble if you don’t know the triggers or caps.
##
Want to get this update sent to you every day? Subscribe to my RSS feed or subscribe via email below:
Richard Seroter's Architecture Musings 
we successfully rewrote our application. Something similar how SAP rewrote R/3 in NetWeaver. we went with eyes wide open understanding all the risks. But staying with the old one was not an option. Unexpectedly, Covid helped a little, because customers slowed down implementations and the “New” team was able to catch up better.