gfody

34 ms·

421.
by gfody 6y ago
these are just management mistakes. the only similarity to tech debt is the delay in consequences.
422.
by gfody 6y ago
It's not explainable until all these weights are between unambiguous concepts in a knowledge base rather than plain text tokens that must be interpreted. For some reason we gave up on symbolic AI in the 70's and decided making mac
423.
by gfody 6y ago
circuit breaker?
424.
by gfody 6y ago
this is incredible but I can't help but feel like we're skipping some important steps by working with plain text and bitmaps - "a collection of glasses sitting on a table" sometimes eyeglasses sometimes drinking glasses
425.
by gfody 6y ago
smokers more effectively social distance, because people can smell when they’re too close
426.
by gfody 6y ago
> The greyscale one in particular is fascinating, and I can feel the effect immediately came here to mention greyscale - I took the greyscale challenge back in 2017 and never went back. I would catch myself pulling out my phone for no ot
427.
by gfody 6y ago
would love to see a subreddit simulator for HN, the finance jabber alone would be amazing
428.
by gfody 6y ago
there are two kinds of programmer: one thinks code is an artifact and that you can produce quality code. the other thinks code is excrement and only exists as a waste product necessitated by the immaturity of our information modeling tools.
429.
by gfody 6y ago
if select is all you need then a view would suffice
430.
by gfody 6y ago
you can also embed images and fonts in svg, probably not as reliable as pdf for pixel-perfect reproductions everywhere though
431.
by gfody 6y ago
> Do we bear no responsibility at all here for how we behave? as described in tfa, the ad infrastructure is maximizing controversy and devisiveness when it optimizes for engagement. it's like inciting a mob - the instigator is more
432.
by gfody 6y ago
> Those people will be highly incentivized not if we don't incentivize them - we just need a social media platform to not be an advertisement platform
433.
by gfody 6y ago
this would be after <attention token> has become the new fluid currency and you've gone deep into debt by paying more attention than you had
434.
by gfody 6y ago
a token as proxy for (the value of) your actual attention is just the innocent prerequisite to some incredible dystopia. as with javascript, Brendan Eich appears to be channeling technology up from the depths of hell. I wonder if he created
435.
by gfody 6y ago
“top performer” is meaningless unless you’re looking back with enough distance to quantify all manner of contributions.. the people who generated the most complexity the fastest are just as likely to be dangerous forces of chaos.
436.
by gfody 6y ago
i think fossil has the better architecture and it would probably take off if the baked in webapp were as polished as github. somebody should fork fossil and make a github clone.
437.
by gfody 6y ago
> In our view, we should be able to maintain every view either in linear time wrt the number of updates or sublinear time with respect to the overall dataset, and every case that doesn't do so is a bug. This is awesome and I believe
438.
by gfody 6y ago
Sorry I’m definitely overly pessimistic when it comes to new database tech - you’ll find us industry hardened rdbms users hard to convince (we’ve been through a lot) thanks for chatting!
439.
by gfody 6y ago
> I'm not clear on your "all sorts of limitations"; you'll have to fill me in on them? this feels like bait but honestly I'm under the impression that incrementally updating materialized views (where optimal = th
440.
by gfody 6y ago
I am genuinely interested in Materialize's capability to incrementally maintain views and I understand there are all sorts of limitations as to when that's even possible - I can't find a comprehensive list of them. I don&#x27
441.
by gfody 6y ago
sorry you missed my ninja-edit - it sounds like SOME lateral join queries CAN be efficiently maintained but not ALL (not the ones that are surprisingly expensive for whatever reason) that's where the promise of "we can materialize
442.
by gfody 6y ago
there are messages like this in the docs: > "WARNING! LATERAL subqueries can be very expensive to compute. For best results, do not materialize a view containing a LATERAL subquery without first inspecting the plan via the EXPLAIN s
443.
by gfody 6y ago
is there a single comprehensive list of restrictions on what can and can't be materialized? for example, if SQL Server can't efficiently maintain your materialized view then it doesn't let you create it - the whole list of re
444.
by gfody 6y ago
they really should've called it something else. now they sound ridiculous: "Productivity Score is NOT a metric for measuring productivity!"
445.
by gfody 6y ago
we use s3 in a repo pattern pretty heavily and I had no idea they didn't have read-after-write consistency. I've noticed s3 will hold connections open by sending back blank lines and always assumed it was synchronizing for consist
446.
by gfody 6y ago
with everything else going on maybe we'll see virtualbox guest additions for macOS
447.
by gfody 6y ago
IIRC Apple got some exotic automated optimization tech when when they acquired PA Semi - I think it was mentioned in the Steve Jobs biography. The A chips have always been impressive and the timing lines up.
448.
by gfody 6y ago
I'm sure zoom filters that detect all such potential prejudice bearing signals and either sanitize them or translate them into your preferred locale (presumably your own - the one to which you're most sensitive) just like Vinge&#x
449.
by gfody 6y ago
this. and all the bleating over precisely which sort of consistency mongo has when it's a document store that cant gaurantee shit about what version of some entity was serialized into the document you just fetched. calling themselves a
450.
by gfody 6y ago
hey.com claims to have "fixed" email - I tried to find out what exactly they do to justify the claim but hit my timeout at about 5 minutes wading through vague testimonials. there's a 37min video that supposedly breaks it all

More ›