the CONTRIBUTING.md document has always existed and contains our guidelines. they know what we’ve agreed upon belongs in a PR, and they simply don’t do it. i’d rather have an empty description than a big stupid ignored form template, because the problem isn’t they don’t know but that they don’t care. that’s a problem that forms, in my experience, don’t fix.
honestly, i hate having a form for my coworkers to fill out. i’ve done it before. i’ve seen it done. i prefer my collaborators, especially in a work environment to do the professional thing and give me enough context to understand the change. i don’t want to have to treat my coworkers like half interested children, but that temptation is always there. a bunch of “did you do your homework?” check boxes feels condescending by proxy. we don’t need a check box for “are the tests passing?” cuz we have automated tests and CI.
i prefer something that just nudges people in the right direction if i can get away with it.
just this week i added a template that read like:
PR guidelines are in CONTRIBUTING.md
This text is meant to be replaced by a short description of your change to inform as to _why_ this change was made to help us triage errors when things go wrong, to provide relevant context to reviewers, and as a matter of due diligence.
i’d say so. i was a professional Android dev for years, and security and privacy are definitely one of the reasons i prefer iOS. i don’t have time to play with my phone so much for my personal device. Apple is the lesser of 2 evils since their business model doesn’t depend on this kind of tracking (even if they do it as well albeit to a lesser extent)
i recently setup an API proxy, C&C server, Grafana and Prometheus, and Discord bot. now i can send pings via Grafana or with a simple request (provided it’s authed via VPN or proxy) and have my Discord bot use a local LLM on my network to deliver the alert to a Discord channel in the voice of Ultron.
nice. this is a detail that i needed to know that would otherwise be a dealbreaker.
i am intrigued by the promises of better histories, since i’ve been reviewing and contributing to a bunch of repos at work.
a lot easier to use
see this is the issue. i don’t find git hard to use. and i’m not going to be one of those assholes that’s like “i never thought it was hard”; i’ve just genuinely been at this for over a decade now. and i run nushell so i’m not opposed to new niche things as long as it improves my workflow.
i really want to get into jj cuz i like the pitch, but the real struggle isn’t new syntax or learning curve but the fact that my workflows at home and especially at work are built around git and GitOps. i tried briefly to integrate it into my dotfiles, but migrating such a large repository got a little hairy.
is there a doc about why a seasoned pro (at least don’t tell my manager otherwise) would switch to jj? are people using this in production effectively? is there a world where i can integrate jj into existing git based workflows that interact seemlessly with other contributors using plain ole git?
“patience is the absence of expectation”
— Shinichi Suzuki
you’re doing everything right. you’re probably worrying too much and prescribing too much. listen to the science and the literature, but also listen to your body. everyone is different. i’ve been lifting for 5 years and bailed out of a 60kg bench press yesterday (tbh higher reps but still; i was embarrassed).
also, comparison is the thief of joy. don’t compare yourself to the guy next to you or the influencers on Instagram or “what’s normal”. the only person you need to try to be better than is you from last week or last month or last year.
trying is the point. trying is progress. discipline is greater than motivation. we all have bad days. but it’s a journey. have a bad day, and go to the gym the next day and celebrate that you made it.
i started when i was 30, and i have been consistent for over 4 years. it pays off eventually, i promise.
but LLMs do represent a significant technological leap forward. i also share the skepticism that we haven’t “cracked AGI” and that a lot of these products are dumb. i think another comment made a better analogy to the dotcom bubble.
ETA: i’ve been working in ML engineering since 2019, so i can sometimes forget most people didn’t even hear about this hype train until ChatGPT, but i assure you inference hardware and dumb products were picking up steam even then (Tesla FSD being a classic example).
i know it’s popular to be very dismissive, but a lot of “AI” has already been integrated into normal workflows. AI autocomplete in development text editors, software keyboards, and question asking bots isn’t going away. speech-to-text, “smart eraser”, subject classification, signal processing kernels like DLSS and frame generation, and so many more will be with us and improving for a long time. Transformers, machine learning optimized chips, and other ML fields are going to be with us for a long time. the comparison to NFTs is either angst or misunderstanding.
the thing that finally got me using a terminal multiplexer was zellij. you can think of it as tmux with training wheels, but i don’t see a reason to go back.
i don’t know the full nature of the exploit, but zlib has an exploitable integer overflow via the MiniZip project. even though our images don’t use that project.
the issue with this take is that they have been transitioning their enterprise services to web services. i and others on my team effectually use Microsoft enterprise tooling on Mac and Linux machines.
i don’t think AD has anything to do with desktop Linux adoption?
i have a Linux Dell at home as well (from work), but it’s just a thin Ubuntu clone with some Dell bloatware. they really could go wild with it with just a few resources. Chromebook is also a good example of what i’m talking about.
OEM integration. i feel like there is a lot to like about Linux that most people who can will. but i think the thing that’s grown Linux a lot (other than geopolitical shifts) in recent time is SteamOS. not just because of Proton, but they’re literally selling a computer as an OEM with a 1st class linux OS. imagine if Dell and HP and Razer started doing the same
the CONTRIBUTING.md document has always existed and contains our guidelines. they know what we’ve agreed upon belongs in a PR, and they simply don’t do it. i’d rather have an empty description than a big stupid ignored form template, because the problem isn’t they don’t know but that they don’t care. that’s a problem that forms, in my experience, don’t fix.