Just a regular Joe.

  • 0 Posts
  • 104 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle
  • NFSv3 (udp, stateless) was always as reliable as the network infra under Linux, I found. NFSv4 made things a bit more complicated.

    You don’t want any NAT / stateful connection tracking in the network path (anything that could hiccup and forget), and wired connections only for permanent storage mounts, of course.



  • Hah. I hadn’t seen that article / heard of the theory, but as far as crackpot theories/hypotheses go, it’s one of the more likely (edit: to come about). I doubt it’s anywhere near the majority yet, personally.

    It was already obvious that propaganda news articles (on obscure websites) had orchestrated releases and promotion on social media, in a massive circle jerk, and I assumed machine generated/assisted content was involved. Then ChatGPT hit the headlines and we all had the power.


  • Whose deepfake influencers do you “trust” more? US, China, russia and a few lesser players are already working to control the information space / spread propaganda (note: not necessarily/always lies, but there is typically a focus or spin) far and wide.

    We know people are highly influenced by propaganda (some more than others, but all of us are) and that quantity and repetition plays a role. Since this is now an established battlefield, I’d like our (western) defences to be strong.

    It has potential for abuse, certainly. That’s par for the course. There is also the potential for it to be used to debunk fake news, shock people out of false beliefs, and help reconnect people to reality. Let’s see how this plays out. popcorn time






  • For deploying applications and associated infra in one fell swoop (often using higher level AWS compute services), it works well enough. In those cases, the dev teams are the infra and support teams, and it is an integrated part of their deployment pipelines. All good, probably.

    Then you have a very typical scenario in larger companies, where you have a mix of centrally managed services (eg. Kubernetes clusters and VPCs/networking) shared by multiple teams and services, custom API gateways, and the dev teams of java/js developers fresh out of college who typically just want to write code and have it talk to a backend DB which they don’t particularly want to support. With services having to be supported for 10+ years, developers will come and go, and sometimes just go, leaving legacy apps and infra that need to be supported by some poor sods in low cost countries, along with CF, TF, Ansible, custom scripts, operators, and manually provisioned infra. In such an organization, you must encourage (and wherever possible enforce) standards.

    If CDK is the company standard, and therefore well understood and supported, with guidelines and company standard libraries, then great. If not, it will be another snowflake.


  • I’m not a fan of CDK as it seems to just introduce more cognitive load for developers and ops (as soon as something goes wrong / gets difficult), often long after the original authors have moved onto new shinier projects.

    It’s yet another way to create snowflakes, but it’s not the worst, precisely because it uses CF behind the scenes.

    If there were an org-wide (or “platform engineering”) strategy based on CDK, it would be different. The same goes for pretty much any infrastructure management tooling choice.





  • https://opensource.stackexchange.com/questions/8367/is-the-term-open-source-a-trademark has a discussion about this.

    The short story is that the OSI failed to obtain a legal trademark in the US for the term “open source” (software), resulting in many opportunistic companies and individuals adopting the term popularized by the OSI (which was founded by Eric Raymond, Michael Tiemann and Bruce Perens).

    There was controversy at the time due to it being a business-friendly spin on the ideological “free software”, and I personally avoided using the term for many years as a result. Even without a trademark on the now generic term of Open Source, there is still value in the OSI brand and its stamp of approval on a license.

    Those who want to be crystal clear, should probably always say OSI Approved Open Source License.

    Now, I’m off to have a Nescafé Approved Coffee.