Yokohiii

15 ms·

361.
by Yokohiii 11mo ago
I don't fully grasp whether your knowledge gaps are severe or just an impostor syndrome. Do your knowledge gaps affect you or do you just feel guilty for not being an expert of every tech? It's easy to feel dumb on the internet, a
362.
by Yokohiii 11mo ago
I've just started with go a few weeks ago, so take my info with a grain of salt. Pocketbase uses a mutex for all the data reads and writes. That means that every write will block any readers for the write duration. If you do a lot of w
363.
by Yokohiii 11mo ago
Like an egregious comment?
364.
by Yokohiii 11mo ago
https://github.com/pocketbase/pocketbase/blob/master/tools/s... I wouldn't be surprised if that's the performance issue. It seems to be used as in memory cache for all (?) collections and
365.
by Yokohiii 11mo ago
I have an friend that starts an project next month that will rely on npm. He is quite a noob and didn't code in ages. He will have almost no clue how to harden against this, he will probably not even notice if he becomes a victim until
366.
by Yokohiii 11mo ago
I don't think you should focus on successful large projects. Generally you should consider that all big successes are outliers from a myriad of attempts. They have been lucky and you can't reproduce luck. I'd like try to corr
367.
by Yokohiii 11mo ago
Success rates imply a ratio. Constant dollars are adjusted. Yes there is a lot more spending overall. But nothing improved quality wise, despite everyone in software somehow says they "make software better". (Which is phrased by p
368.
by Yokohiii 11mo ago
I think if we look at the lack of accountability it's obvious that one major problem is that many of these projects do heavily rely on contract work. No company or gov in the world can supply the perfect brain- and manpower necessary
369.
by Yokohiii 11mo ago
I think this is too simple. First of all, hardware people have high incentive to fully replace components and systems for many reasons. Replacement is also the only way they can fix major design mistakes. Software people constantly do fix b
370.
by Yokohiii 11mo ago
I can see that high level overviews of complex systems are useful to get some insights, but in the same way I have the feeling that this mentality of high level, abstract organization is the root of the problem. If you have a complex system
371.
by Yokohiii 11mo ago
i think they focus their dataset on photography. flux 1 dev one was never really great at artistic style, mostly locking you into a somewhat generic style. my little flux 2 pro testing does seem to verify that. but with lora ecosystem and e
372.
by Yokohiii 11mo ago
18gb 4 bit quant via diffusers. "low vram setup" :)
373.
by Yokohiii 11mo ago
I said there is hype in general about the topic. > I don’t see how this is true. By what metric might “most” lead to a true statement? It's english, not code.
374.
by Yokohiii 11mo ago
I'd require vendor code being committed to git and integrated into the CI/CD pipeline. It should be treated as if you own it, just with a policy whether you want to change it or not. The difficulty to make changes obvious is same
375.
by Yokohiii 11mo ago
You are right about version locking, bullshit on my side, not sure what I was thinking. I personally don't have a problem with the general ability to change vendor code. The question is whether you want it in an specific case or not. I
376.
by Yokohiii 11mo ago
https://github.blog/security/supply-chain-security/our-plan-... So github has some tools available to mitigate some of the problems tied to it. Probably not perfect for all use cases. But considering the current s
377.
by Yokohiii 11mo ago
But relying on the goodwill of commercial sec vendors is it's own infrastructure risk.
378.
by Yokohiii 11mo ago
I think if you generally depend on npm packages, being frugal is hard, because every random package works against you. Last time my perception was also that publishing sec is a weak point. If at least heavily used packages would be forced t
379.
by Yokohiii 11mo ago
Vendoring literally just means grabbing the source code from origin and commit it to your repo after a review. The expectation that every repo has important regular updates for you is pure FOMO. And if I don't do random updates for fu
380.
by Yokohiii 11mo ago
You forget to account for the fact that the xz-utils backdoor was extremely high effort. Literally a high skilled person building trust over time. While it's obviously possible and problematic, it's still a scaling/time issue
381.
by Yokohiii 11mo ago
The prompt from that project will be even more worthless, it's just a generic instruction to create a generic summary. It's about having human feedback in commit messages. What are their reasons, problems, intentions for the patch
382.
by Yokohiii 11mo ago
About what? Most times i check, it's there. There is hype around AI and agentic dev. It's not subjective. My opinion is that it's a valid factor to consider if you evaluate tech. We've seen with i.e. microservices that
383.
by Yokohiii 11mo ago
Confirmation bias can be a problem. Positivity bias as well. The author seems to take agentic dev as granted, which isn't. He doesn't goes into much detail either. It's at best a soft complaint about why it isn't plug an
384.
by Yokohiii 11mo ago
https://github.com/arpxspace/smartcommit/commit/cc677f7bd210... This is just a complete braindead commit. Without looking at the code I could probably take 5 minutes to make sense of the commit message, being
385.
by Yokohiii 11mo ago
Most of it reads like too high expectation of overhyped technology.
386.
by Yokohiii 11mo ago
Photography and motion pictures were deemed evil. Video games made you a mass murderer. Barcodes somehow seem to affect your health or the freshness of vegetables. The earth is flat. The issue is that some people believe shit someone tells
387.
by Yokohiii 11mo ago
With local models you can use control net, which is simply speaking, the model trying to adhere to a given wireframe/openpose. Which is more likely to give you an stable result. I have no experience with it, just wanted to point out th
388.
by Yokohiii 11mo ago
An more original prompt wont fix things. Modern base models want to eliminate everything that puts their creators at risk, which is anything that is clearly made by someone else, more or less accurately reproducible. If you avoid decent rep
389.
by Yokohiii 11mo ago
If you want a chance for real creativity, flexibility and you have a decent gpu go local. Check out comfyui, download models and play around. The mainstream services have zero knobs to play around with, local is infinite.
390.
by Yokohiii 11mo ago
I don't think it's solely an data issue. Flux models for example are quite stylized, very notable with photorealism. But I think it was an deliberate choice to to have outputs that are absent of likeness and distinct style. I thin

More ›