This "always-open self" Wells speaks of, though admirable, doesn’t always guarantee a happy time of things. Often it is exhausting. Often it is heartbreaking. But no worthwhile life ever had it different. Sic transit Gloria Mundi.
Nothing to add from my side...
To become great at technology strategy, start by getting good at making boring plans. Get clear about the problem you are overcoming with your plans.
As mentioned before it is good to use boring technology but it is also a good idea to make boring plans.
So I’m making a case here that you should tend to prefer mature things, and you should try not to use too many things.
But it’s not an absolute principle. Obviously sometimes it does make sense to add new technology to your stack. And it can even make sense to use a weird new thing.
It is always good to stick to/use technology which has a proven trackrecord and is known well by you. But as always your mileage may vary and as always the answer in technology is: "It depends".
What you really want is a repeatable, automatic pipeline that takes your code, merges it with everyone else's, runs some tests, deploys it to a test server, runs some more testing and validation, then automatically promotes it to production once you know it works.
Simply obey the rule that you never ever should do use this tool in any production environment.
As cloud adoption rises, so does cloud "sticker shock." That tremendous savings seen from the switch to up-front CapEx investments in information technology to subscription mode soon gets soured as the rising monthly bills come in for services nobody knows where and when they are being used.
Although many cloud providers advertise that cost savings can be achieved, the reality then looks different in many places. Especially the distinction between CapEx and OpEx looks tempting at first glance, but in practice it often fails to meet the high expectations.
There is no good reason to use short timezone codes like EST, CST, PST — doing so will only bring you pain. Either use the tzdb name like America/New_York, or use an offset from UTC, depending on what you want.
It is important to be aware of special things when handling date and time.
Just a quick thought. From my point of view there are three different stages of software quality:
Each of them have different needs, share some aspects of software development but do not share the same requirement for quality/maintainability.
Unfortunately, they can also leak our sensitive data, consume our limited bandwidth, drain our batteries, and, in one case, expose links in chats that are supposed to be end-to-end encrypted. Among the worst offenders, according to research published on Monday, were messengers from Facebook, Instagram, LinkedIn, and Line.
Nicht wirklich überraschend, dass Dinge aus dem Hause Facebook ganz vorne dabei sind, wenn es um Privacy Verletzungen geht.
Quelle: Study shows which messengers leak your data, drain your battery, and more | Ars Technica
Quite an interesting read on the current state of a Covid19 vaccine development.
Will a vaccine stop Covid? - UnHerd
Originally found this here: Kristian Köhntopp on Twitter: "»But it absolutely will not be: we get a vaccine in December and we’re out of this by February. The light is real, but the tunnel it’s at the end of is still pretty long.«" / Twitter
Creating/changing Linux files in your Appdata folder from Windows will likely result in data corruption and/or damage your Linux environment requiring you to uninstall & reinstall your distro!
Do not change Linux files using Windows apps and tools | Windows Command Line
