manbash

5 ms·

31.
by manbash 6mo ago
This is very cool. I couldn't find it it already supports duets. I assume it won't.
32.
by manbash 6mo ago
Copyleft was intended as a principle to keep the software free (as in 'freedom'). Proposing to lock out certain areas of the codebase is directly opposite to this principle.
33.
by manbash 6mo ago
Yeah, it really wasn't about the school.
34.
by manbash 6mo ago
Folks here can decide for themselves whether to check green accounts' "Show HN" these days. We are all aware of AI slop and creep in all shape and form. Moderation is already taxing as it is.
35.
by manbash 7mo ago
I think it's a nice break from vibe-coding. It feels like a good direction in terms of use cases for LLM.
36.
by manbash 7mo ago
I was reviewing a confluence page which was reviewed my many stakeholders. Something bugged me to an excruciating extent about the content of the page: something was off at some parts of the text. I inspected the page and it turns out the f
37.
by manbash 7mo ago
Wait, I am curious how Gemini "pushes" devs to GCP.
38.
by manbash 7mo ago
This paper seems like something I would like to keep as reference, especially with its approach to employ STRIDE and present very elaborate DFD (which you don't see as often in my experience). The DFD in 7.1 is quite impressive.
39.
by manbash 7mo ago
"software developer" is pretty broad. Here this is specifically B2C (business to customer) applications. I only assume that you haven't been in this market sector, otherwise you would've been more familiar with GDPR and
40.
by manbash 7mo ago
Respectfully, what was the purpose of this comment, really? And I also disagree, your suggestion is not easier. The & operator is quite intuitive as it is, and conveys the intention.
41.
by manbash 7mo ago
> i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. Making it seem like there's only going to be one mass layoff round. There will b
42.
by manbash 7mo ago
Yup don't expect up-to-date practices and always come with the expectations that your security will be flawed.
43.
by manbash 7mo ago
It's nice that they explain the "what" (...it is doing) but not the "why". Who is going to use it and for what reasons? Also, if it's essentially a sort of metadata, can't the output generated image be rep
44.
by manbash 7mo ago
RE agents are really interesting! Too bad the author didn't really share the agents they were using so we can't really test this ourselves.
45.
by manbash 7mo ago
No, it's not. You assume it was stolen, while it wasn't implied in that comment. They simply stated that the data have been put publicly at some point or another.
46.
by manbash 7mo ago
Exciting! It doesn't imply that we should now sprinkle the new annotations everywhere. We still should keep working with proper iterators and robust data structures, and those would need to add such annotations.
47.
by manbash 7mo ago
Chiming in: indeed, the response is very dry, and raises suspicion. It states the obvious facts and then makes a boring statement, lacking any nuance of the conversation. It is not argumentative in the very least. Time has been spend, yes.
48.
by manbash 7mo ago
The list of issues does not seem to stem from whether they had used this build tool (CMake) nor others (nor official build environments).
49.
by manbash 7mo ago
Why laptops specifically (and not also desktops)?
50.
by manbash 7mo ago
AI and LLM specifically can't and mustn't be allowed to publically criticize, even if they may coincidetally had done so with good reasons (which they obviously don't in this case). Letting an LLM let loose in such a manner t
51.
by manbash 7mo ago
The models generalized "understanding" and "reasoning" is the real myth that makes us take a step back and offload the process deterministic computing and harnesses.
52.
by manbash 8mo ago
A bit off topic, but I am curious about your experience with Structurizer. My experience wasn't so positive (albeit the general incentive that it's open-source and local).
53.
by manbash 8mo ago
I have worked with Wayland + Flameshot for the past 2-3 years and it seems to work fine as far as I can tell.
54.
by manbash 8mo ago
Oh, definitely. Also, they end up getting stuck in a loop, adding and removing the same code endlessly. And then someone comes and "improves" their agent with additional "do not repeat yourself" prompts scattered all ove
55.
by manbash 9mo ago
Aw shucks I was almost pulled for another round of Star Fox 64. Unfortunately it's not there.
56.
by manbash 10mo ago
Ah, those days, where you would slice your designs and export them to tables.
57.
by manbash 10mo ago
How else can you take responsibility if you don't make it public? You can't have integrity if you hide away your faults.
58.
by manbash 10mo ago
Under "Programmatic Tool Calling" > The challenge > Traditional tool calling creates two fundamental problems as workflows become more complex: > Context pollution from intermediate results: When Claude analyzes a 10MB
59.
by manbash 10mo ago
> I speculate that within a few months, the communities will have settled on a single dominant one. The solutions on the roadmap are not centralized as GitHub. There is a real initiative to promote federation so we would not need to rely
60.
by manbash 10mo ago
Nice work. I have gone through the fairly straightforward paper. May I ask what you've used to confirm the cache hit/miss rate? Thanks!

More ›