mrkeen

41 ms·

841.
by mrkeen 2y ago
You just reminded me of one of my main reasons to avoid getters, which the article didn't mention. Accessing a field will not invoke other code.
842.
by mrkeen 2y ago
Why not just prevent the construction of bad states instead of constructing bad states and later checking them?
843.
by mrkeen 2y ago
> When an actual human being wants to interact with a website they include their own public key. Move over cookies, IP addresses and tracking pixels, we now provide cryptographic proof to advertisers that we are interested in something.
844.
by mrkeen 2y ago
> Same with a medical diagnosis. You don't expect to fix the issue by just mentioning the diagnosis to the patient and saying "fix it". That's what this is though. The slide deck author is the establishment - the per
845.
by mrkeen 2y ago
I'm trying to puzzle this one out a bit. Who are the good and bad actors in this threat model? I wrote a server: myServer = do fetched : Bytes <- fetchFromExternalApi let parsed : SecretResponse = jsonParse fetched
846.
by mrkeen 2y ago
> "A lack of vigilance and discipline" Let's say hypothetically that it's a bad strategy to give your employee a C compiler and tell them to write code. Now, if you instead gave your employee a C compiler and told
847.
by mrkeen 2y ago
This comes to mind https://www.theguardian.com/technology/2014/jun/30/facebook-...
848.
by mrkeen 2y ago
I remember them as mascots. I don't remember any scam. Weren't they just there to tell you put money in your CBA savings account? There was such a thing as interest back in 90s, right? It might have even kept up with inflation?
849.
by mrkeen 2y ago
Right, now it's compile once, don't run on the web.
850.
by mrkeen 2y ago
The author's spot on with the liaison and elision rules. > Nasal vowels are especially hard for English speakers like myself because, well, our language doesn’t exactly have any I hadn't heard of these. > To new learners ‘so
851.
by mrkeen 2y ago
We also managed to get rid of JavaScript like 15 years ago, with major backend technologies providing their own compile-to-js frameworks. But JS outlived them, because it's the whole write-run-read-debug cycle, whereas the frameworks o
852.
by mrkeen 2y ago
Turner hoped that we could have programming languages that wouldn't go into (useless) infinite loops. They should either terminate, or keep producing values forever (be 'productive'). The author sets out to prove that Bird&#
853.
by mrkeen 2y ago
Because the alternative to using one name is using more than one name. These days I'm pretty sure I'm using `select` to mean `map`.
854.
by mrkeen 2y ago
Probably just Berkson's paradox https://en.wikipedia.org/wiki/Berkson%27s_paradox
855.
by mrkeen 2y ago
For Google's case the order was reversed. Google used to send customers to your site. Now they try to show you the information on their site so that the customer doesn't need to go to your site.
856.
by mrkeen 2y ago
Zero information on this site. It's like the AI that spewed this garbage out was only fed Medium think-pieces, parodies of Gartner, and Dilbert.
857.
by mrkeen 2y ago
Personal pet peeves: * They hide the queries. When your DB or cloud service gives you a printout of your 10 slowest queries, you then have to figure out what object code that relates to. And then is there even a way to fix it, or are you
858.
by mrkeen 2y ago
I think the analogy works. It's all about the tradeoffs. Double-entry is harder to grasp, but it has certain properties, like being able to sum along rows or columns. With that property, you can then make assertions like "if any
859.
by mrkeen 2y ago
From a use-case perspective, Haskell monads let you restrict where various effects happen. Some code can be allowed to do local mutation, other code can do shared-mutation suitable for (ACID-like) transactions. In Java you can do anything
860.
by mrkeen 2y ago
> Functional programming does not prevent you from using objects It's a bit like how doing single-entry bookkeeping doesn't stop you from doing double-entry bookkeeping.
861.
by mrkeen 2y ago
> The trouble with functional programming is functional programmers > This needs to be said more. Way more. In other words, why stop with an ad-hominem when you can do an ad-nauseam too.
862.
by mrkeen 2y ago
It's already very unlikely that you can 'recover-and-proceed' in the context of any business app exception (Security violation, customer not found, no such payment, etc.). So what's left in exception handling is logging
863.
by mrkeen 2y ago
I am also skeptical. A compiler is a function from source code strings to binary bytes. Writing out instructions to do memory-unsafe things is not in itself a memory-unsafe activity.
864.
by mrkeen 2y ago
It's the closest you get to 'λ' on a US keyboard.
865.
by mrkeen 2y ago
> You crash the program. No thank you. > Or you can put in a fail safe before the error bubbles up to main and do something else In other words, >> your parser backtracked from parsing a Bool and decided to try to parse an Int i
866.
by mrkeen 2y ago
I had a 16-core 32-thread Threadripper that I was rather fond of. Not good enough for win 11.
867.
by mrkeen 2y ago
But to be clear, tedious manual XML configuration was also Spring. Others may have done it earlier, but Spring still decided it was the way to go, put their name on it, and released it.
868.
by mrkeen 2y ago
> The fact that the program arrived there is a Logic error in your program. No, your program correctly determined that user input was invalid. Or your parser backtracked from parsing a Bool and decided to try to parse an Int instead.
869.
by mrkeen 2y ago
Three branches of government, two houses, mix of federal and state powers, checks and balances, an impeachment system, all that stuff?
870.
by mrkeen 2y ago
[ https://doge.gov/ ] Sorry, you have been blocked You are unable to access doge.gov Feels like the Twitter transition again. Hey remember when there was concern that he might not have time to effectively run Tesla a

More ›