Let's try BART zero shot on restaurant related queries

Let’s look at what bart-large-mnli has to say on restaurant related labels for food and non food queries The queries here are just arbitrary statements I came up with off the top of my head. You can skip to the final scoring, but in summary, using a super simplistic evaluation here, I think that the super accessible bart-large-mnli model does pretty well here. One observation I am seeing casually, which I believe Jake Tae https://jaketae....

June 16, 2024 · 7 min · 1453 words · Michal Piekarczyk

Recycling xero shoe diy huarache rubber

What to do with the left over rubber from your Xero DIY haraches? I originally got this Vibram rubber sheet from this xeroshoes.com link, a few years ago. I have made two pairs for myself and I made a few pairs for some family members too. They are great, however, I had stowed away the left over rubber for, well, a long time now haha. I didn’t know what to use the left over material for, until now 😀....

June 9, 2024 · 1 min · 90 words · Michal Piekarczyk

Some quick analysis of prior fasting data

Ok fasting hours, but how about eating hours? The data dump from my Zero fasting app highlights the fasting hours. I had used Zero from 2019 to late 2023, and I wanted to look at briefly, well what about the eating hours, other than the fasted hours? In an effort to save time, I used ChatGPT to come up with the calculation around the eating hours. Actually the first try was interesting since the outcome was showing daily eating hours that were beyond 40 hours 😅, but coercing ChatGPT to try to correct so this falls within the expected under 10 hours, ChatGPT was able to actually course correct nicely !...

June 2, 2024 · (updated June 8, 2024) · 3 min · 623 words · Michal Piekarczyk

issue experienced in typewise logseq interaction

UPDATE: 2025-02-04 wow, i dont know if this is new or if I stumbled upon something thats been sitting in plain site all along, but today, when after entering a part of a logseq node , with either the # or [[]] notation, if subsequently I type q comma and a space, , then no typesense autocorrection occurs! The issue An example that is around undo-ing auto-corrections, when using the Logseq app....

May 24, 2024 · (updated February 4, 2025) · 1 min · 184 words · Michal Piekarczyk

Nice pretty printing go slices

package main import ( "encoding/json" "fmt" ) type Foo struct { Blah int Flarg string } func main() { var stuff []Foo = []Foo{ Foo{Blah: 8, Flarg: "sure"}, Foo{Blah: 7, Flarg: "mhm"}, } stuffBytes, err := json.MarshalIndent(stuff, "", " ") if err != nil { fmt.Println("Marshaling errors", err) return } fmt.Println("harder to read\n", stuff) fmt.Println("\nbetter\n", string(stuffBytes)) } outupt is easy on the eyes harder to read [{8 sure} {7 mhm}] better [ { "Blah": 8, "Flarg": "sure" }, { "Blah": 7, "Flarg": "mhm" } ]

March 30, 2024 · (updated May 26, 2024) · 1 min · 85 words · Michal Piekarczyk