just6979

7 ms·

31.
by just6979 8mo ago
"with potential adaptions relevant for the potential older code state there" And there it is. Not "potential adaptations", they will be a 100% necessity for some applications. There are industries outside webdev where th
32.
by just6979 8mo ago
and Git Flow and similar day "that's what merges to main or for". GF and TDB really are way more similar than anyone wants to admit. It's basically "branch for release" vs "merge for release". There a
33.
by just6979 8mo ago
The dev branch can be useful with larger team sizes where there might be lots of overlapping work being done. Or a shop that isn't fully into automated continuous delivery, ie: a human needs to press the button to actually deploy to pr
34.
by just6979 8mo ago
I don't think they "ran it through an AI image generator" to scrub it, I think someone asked an LLM for a description of a git branching model with an image to go along with it. Since there is _a lot_ on the web about GitFlow
35.
by just6979 8mo ago
It only takes a cursory knowledge of what LLMs really are to understand why recreating tutorials is easy, but making actual new stuff that is well engineered (takes way way more than "passes the test suite") is difficult. Actual n
36.
by just6979 8mo ago
https://en.wikipedia.org/wiki/Frequency-hopping_spread_spect... , combined with the inverse square law, is pretty amazing. The amount of data needed to send audio to your ear-buds is quite small compared to the spectrum
37.
by just6979 8mo ago
That middle ground has been eroded by cost-cutting. Example: my mother had a cardic resynchronization device, and it had some kind of NFC type thing to enable the full wireless comms mode: wave a wand over her shoulder and the device's
38.
by just6979 8mo ago
Pretty sure they're replying to the post that directly contrasts Discord/Slack and IRC. TFA mentions both, yes, but as a direct example of service/platform (Discord) vs protocol (IRC, XMPP, etc). The comment asks a question t
39.
by just6979 8mo ago
I would start with asking what kind of improvment, why, how, etc. Or I could just start changing things to more closely line up with whatever textbook or "Clean Code" clone book I has last read, and hope it still passes the tests
40.
by just6979 8mo ago
"You can do this in pure software, the hardware side of it just adds noise." That "noise" changes the context, connects it to different parts of the training corpus. Removing the "physical art" part would likel
41.
by just6979 8mo ago
I assume it was to force the LLM to "think" about creating physical art as opposed to just a digital representation in a file. I'd bet the responses would be different if it was told to just look at the SVGs instead of photos
42.
by just6979 8mo ago
They even mentioned this in the article: "However, the tester surmised that introducing the materials into the circuit is just like adding a resistor in series, and they’re unlikely to distort the audio too much, except by lowering the
43.
by just6979 8mo ago
In order to carry the proof, you have to parse it early (otherwise you're not carrying it the whole time before parsing), so you you're both right.
44.
by just6979 8mo ago
But can you get an AI to zone out on a fluffy couch at the center point of a dank hi-fi setup with the volume cranked to 11, while chillin' on 50mg of THC? And will you enjoy paying someone else to let the AI to do that?
45.
by just6979 8mo ago
You: "Why did you build this?" LLM: "Because the embeddings in your prompt are close to some embeddings in my training data. Here's some seemingly explanatory text with that is just similar embeddings to other 'why?
46.
by just6979 8mo ago
Nah, more fun to burn money.
47.
by just6979 8mo ago
Then how many models deep do you go before it's more cost effective to just hire a junior dev, supply them with a list of common backdoors, and have them scan the code?
48.
by just6979 8mo ago
"I push very high test coverage on all my projects (85%+)" Coverage doesn't matter if the tests aren't good. If you're not verifying the tests are actually doing something useful, talking about high coverage is just
49.
by just6979 8mo ago
"Some users will _accept_ "improvements" IFF it doesn't break their existing use cases." Fixed that for you.
50.
by just6979 9mo ago
If you need the AI to indicate "could be wrong" on everything it writes to prevent your devs from blindly following everything it says, you're doing it so wrong. That should be the default mindset. Of course it could be wrong
51.
by just6979 9mo ago
Wait, so you have the LLM review, then you review (selectively choose) the proposed review, then you (or the LLM?) review the reviewed review? But often times (so, the majority?) the initial LLM review is useless, so you're reviewing r
52.
by just6979 9mo ago
Yeah, it's called git: make your own branch from the PR branch, commit and push the nitpick change, tell the author, and they can cherry-pick it if they approve. Gitlab has this functionality right in the web UI. Reviewers can suggest
53.
by just6979 9mo ago
Usable icons _are_ a bit interesting. A bunch of same shapes with same-ish colors on a grid is NOT prioritizing usablity. It's prioritizing minimalism. The middle icons in that list are interesting enough that your visual cortex can pa
54.
by just6979 9mo ago
I don't think skeuomorphism applies to icons. The early pen-and-inkpot icon isn't trying to act/feel like a pen and inkpot. It's not like there is an inkpot in the program's UI and you have to move the cursor to it
55.
by just6979 9mo ago
You don't need to store the timezone anywhere, you just need to know the current local timezone when the stored UTC time is used. And that's why storing in UTC is better, because it only takes one conversion to represent it in som
56.
by just6979 9mo ago
I think you got it backwards. The only way is guessing, it's all random. It's the internal inconsistencies that get me. Like, OK, I understand that there might be some quirks, maybe due to some weird backwards compatibility or tec
57.
by just6979 9mo ago
"There's no reason a local copy should have the exact same implementation as a repository, git made a wrong turn in this." Who is forcing you to keep a local copy in the exact same configuration at upstream? Nothing at all is
58.
by just6979 9mo ago
This. "If you do a single rebase at the end, there is nothing to remember, you just get the same accumulated conflicts you also collectively get with frequent rebases." There is _everything_ to remember. You no longer have the con
59.
by just6979 9mo ago
If you rebase form main often, it keeps the difference to main quite small, so that when it comes time to do the final merge to main, it's either able to be fast-forwarded (keep it linear, good job!), or at least a very low risk of bei
60.
by just6979 9mo ago
A merge can have you doing a history quiz as well. Conflicts can occur in merges just as easily as rebases. Trouble with trying to resolve conflicts after a big merge is that now you have to keep the entire history in your head, because you

More ›