Is it? Based on what I've seen online the company name was derived from a CIA project from the 1970s that the founders worked on, but it doesn't seem to be based on an acronym. There was an earlier unrelated project from the 1950s which used ORACLE as an acronym ("Oak Ridge Automatic Computer and Logical Engine").
this is the internet, not a Sunday service at your local mormon temple where swearing is banned. You can call Larry Ellison an asshole. There are few people more deserving of being called in asshole than he is.
Sounds like a kind of insult to me. I'm not related to them in any way.
And, to be honest, I'm just trying to kind of follow the guidelines. There's too much of bad news and negativity around me, I'm fed with it already, thanks. I want to have fun if it's possible.
Not an insult at all - the mormons are explicitly against swearing of any and all forms, moreso than any group of people i've ever met. they self-censor in a very unique way, they are super clean in how they speak.
Well, if this helps to explain my actions a little - I have friends in Russia (and elsewhere), and very often our jokes/satires/alike come around censorship and "classified information". It’s a bit difficult to explain, but this way of writing messages - with [CENSORED], [DATA DELETED], [CLEARED] and the like - has become something of a meme (and I don't mean dunk memes, I mean cultural meme, yes) or constant joke among us. So for us, it’s a bit like a way of getting a laugh at censorship’s expense. I’m sorry if that was a bit out of context.
> At this point in my life "it just works" is good enough and no longer a point of ironic derision.
I am the same. I used to fiddle and obsess on customising every last thing possible. Now I just want the damn thing to work, and MacOS does exactly that.
Unit tests very roughly double the amount of effort required to make any meaningful change to your codebase. They are also require maintenance same as ordinary code - but the customer does not care in the slightest whether or not they pass. On the other side, they can only really tell you about low level bugs that you already expected, they cannot surface system level bugs - the actual hard bugs that cause problems for you and your customers.
Then there is the danger of thinking that green=all good, an example of 'automation bias' where we learn to trust the automation even as things go wrong.
As makers, it is also tempting to believe that [all] problems can be solved by making something (i.e. code), but actually many problems are not of that nature, and cannot be solved in that way.
Sorry yes. If an LLM written unit test fails, then it has to be determined whether the test was wrong or the code was wrong. This is an expense in human oversight, unless of course we believe that LLMs will get it right at a high enough rate that they can be left to code everything themselves completely automatically.
I kid a little, I worked with some very good PMs when we did client work who made my life much easier. Working on a SaaS though, I find them generally less than useful.
reply