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

help-circle
  • I’m not a historian, but Tacitus definitely mentioned Jesus’ crucifixion. Saying there are a “a lot” of source is an exaggeration, you’re right about that, but there’s basically no doubt that Jesus was a real, historical figure. (I’m not saying that you’re disputing that, I’m just still stuck on the guy actually thinking that Jesus wasn’t real.)

    Obviously Christian sources can’t be taken at face value, but there’s enough corroborating evidence - be it archaeological or written - that proves that at least some of the things in the gospels are based on facts, even if it’s certainly embellished and a lot of it likely just made up and/or warped over time.




  • As I said, there are some self-hostable alternatives, but nothing even remotely enterprise ready yet. I’m keeping a pretty close eye on this because my boss wants to train a support chatbot on company data and run it on our own hardware. (And an alternative to copilot would be great too, as that’s banned for internal use.) There are some great tools to tinker around with, but I haven’t found anything that I would call production ready.


  • Decisions like this just prove how massive the market for a self-hostable alternative is. They’re not banning it because it’s a bad tool, they’re banning it because they’re concerned about what happens to the source code their engineers paste into it.

    There are already a bunch of OSS attempts, and it likely won’t take long until we have something of comparable quality to ChatGPT is available for companies to host on their own hardware.


  • Personally, I think the biggest challenge with documentation is keeping it up to date.

    The only way I’ve found to be actually up-to-date on docs is to do GitOps and have self-documenting code. That way every change being made is automatically documented with a commit message.

    If you can’t do that because your tools aren’t GitOps compatible, you need management to enforce some kind of documentation rule. Like every time a system gets touched, documentation needs to be updated. A project isn’t complete until docs are done/updated.

    This is easily said, but in practice it’s just not going to happen. You need a team that both actually wants to this, and has the time to do it.







  • My little conspiracy theory on this: I wouldn’t be surprised if every intelligence agency in Europe knew how did it, but no one is going to tell, and we’re not going to find out for years.

    An attack on critical infrastructure like this is essentially an act of war, and nobody in Europe wants to escalate this conflict any more by admitting they know who’s responsible.

    If it was Ukraine, it would result in public outcry, and we’d basically be forced to cease any military support. If it was Russia, it’s an act of war and there’d be public pressure in the other direction, maybe even enough to make us officially declare war. If it was the US, there’d be pressure for at the very least some pretty severe diplomatic consequences.

    Nobody in European governments wants any of those results right now. Everybody is content to just leave it be and an article like this pointing blame at one of the three every couple of months is the only thing we’ll hear on it until it gets declassified in 50 years when it doesn’t matter anymore.