this is my experience as well. we have a bespoke wrapper around Jenkins, and the more we can test locally the less time we have to spend waiting for the system to fail. it’s one of the reasons i’ve adopted just to script things locally as if it was CI.
chrash0
joined 2 years ago
heck yeah this is the review i was looking for 💯
you’re right. i just expected it to be an increase 😅
i honestly didn’t look that close, obviously haha
but yeah, i’ve been kinda looking for a reason to de-Microsoft my stuff
good lead. it’s just the one project for now, and to my surprise it’s actually a dependency for the ollama-rs project, so i feel somewhat obligated to keep it stable.
yes, according to this morning’s email
i guess in these situations i think of my aunt, who is in her 80s. she has an iPhone. should she buy a NAS and host Immich? i don’t think “make backups” is the simple advice it appears to be for the vast majority of people
i think it’s easy to make comments like this from the peanut gallery, with the benefit of hindsight and a self-selected group of users who will agree. but Apple should be legally obligated to address this. the solution can’t be “this idiot didn’t spend his nights and weekends doing 3-tier backups and high availability infrastructure diversity!”; that’s not scalable. if we just accept that companies can do this, they will continue to. but this has been on the front page of HackerNews. it’ll probably make it to Tim Apple’s desk eventually, so we’ll see what shakes out.
i think the alternative is to use grep args. but ya know i’m living in the future using nushell’s open command and ripgrep so the argument is just kinda adorable
as someone who used to work on “expert models” i’m excited that not everyone has abandoned them for “what if we just had a model that knows everything (that doesn’t exist) and costs a billion dollars to run”
honestly, the brag document is a great takeaway. so many times people will subtly or implicitly question documentation or refactors, and when shit hits the fan and the readability refactor or documentation or logging/tracing PR becomes the clincher in quickly resolving the issue i love calling it out. documenting those cases themselves as a way to sell documentation and code quality to others feels like an amazing idea (if not exactly a “brag document”)
view more: next ›
we use Jenkins + a bespoke wrapper at work. thats left a bad taste in my mouth enough to avoid Jenkins altogether