chrash0 @ chrash0 @lemmy.world

Posts

3

Comments

197

Joined

2 yr. ago

“Suggesting”

other commenters have hinted at this, but the main point of most of the good advice is this: don’t use the system Python install (ie the one from apt) for development. uv is my go to, but the idea behind *conda, pyenv, asdf, etc is the same. the underlying OS shouldn’t be an issue; you should be able to ship the code between OSs and build just fine, ideally.

generally speaking, i think it’s good practice to find several recipes and compare and contrast them. you’ll find opinions and get a sense for what the writer’s priorities are (quick, fewer dishes, what they usually have in the pantry, etc) and can figure out which writer has similar priorities to you. or just synthesize a recipe from those sources. this does require some technical know-how, but i think this is a good skill to have.

the first issue is familiar to me as my first laptop had this issue, while running Windows XP. the fans were going out and simply couldn’t move enough heat. the solution then that mostly worked was one of those laptop stands with fans built in. it worked most of the time, but a real solution might mean cleaning out the chassis and maybe replacing the fans.

for the second, i didn’t really have trouble setting up the Nvidia drivers just following the docs. sorry if that isn’t helpful; i’m stuck with Nvidia for my ML/CUDA stuff.

my opinion is that the browser in general for rich front ends is the mistake, but i know i’m the minority

nice. simple and modular i like. i deal with far too many “one stop shops” at work to bring that home

we use Jenkins + a bespoke wrapper at work. thats left a bad taste in my mouth enough to avoid Jenkins altogether

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.

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 switched to Linux in 2013ish to get away from my gaming habit and go all in on programming and computer science. that may not work these days as all the games i play work on Linux ha

sure, there’s reason to be cynical, but i don’t think handing society to fascists out of bleak pessimism is the way i want to live my life.

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”)