Hacker Newsnew | past | comments | ask | show | jobs | submit | Disposal8433's commentslogin

Flagged because:

> what if we could run only the relevant E2E tests

The real title should be "Using Claude Code to Reduce E2E Tests by 84%."


That's not a good reason to flag; you can just comment on the bad title (as you did), or even email hn@ycombinator.com and ask them to fix it.

Article flags should be reserved for things you don't believe should be on HN at all.


Killing robots made by slaves. Where do I sign up?


I wouldn't do it, killbots have a preset kill limit: an antagonist can just send waves of men after men until they reach their limit.


> If outages [...] stop whole companies in their tracks

They should fucking learn how to code because no one in their right mind would depend on such an external service that can be easily replaced by cloning repos locally or using proxies like Artifactory. Even worse when you know that Microsoft is behind it.

Yes, most companies don't have good practices and suck at maintaining a basic infrastructure, but it doesn't mean GitHub is the center of the internet. It's only a stupid git server with PRs.


> It's only a stupid git server with PRs.

I feel like you’re missing a few features here


Which ones and what are those exclusive features that GitLab doesn't have?


What do you suggest? Some kind of std::const_reference<Type>? Clang-tidy is enough in addition to the reviews.


The person is arguing that it is a massive difference, not a typo. I am saying that if that is the case, then maybe the hamming distance between correct and buggy code that both compile should be greater than 1, regardless if more tooling can help solve the problem or not.

I specifically take issue with this framing of it is not an issue for we have the tools to help with this, especially where the tools are not part of a standard distribution of a toolchain and require more than minimal effort. C++ has had many a warts for many decades, and the response has always been *you are just holding it wrong* and not running a well covering integration test suite with sanitizers on every commit, you just need to run one more tool in the CI, just a comprehensive benchmarking suite, have more eyes looking for a single char difference in reviews.


The easiest* solution would be to do what rust does. You need to use & on both sides and error out on mismatch. Eg.

fn foo(bar: &Bar) { ... }

bar(&Baz)

* This would be a breaking change, so a non-starter.


I'm seeing this way too often in production code, despite linters and reviews. So we have to keep plastering over.


The problem is not the reference, the problem is implicit copies and the horses left the barn 40 years ago, it's too late to fix that. The only thing we can do right now is deleting or marking copy constructors explicit whenever possible


It's perverse and disgusting. Also what about lazy students, neurodivergent, or poor people that are most likely not having a good outcome despite learning? In the end even average students would be ignored by the teachers.

What about everyone having the same education? What about not putting capitalism in everything?


Some of the richest people are neurodivergent. Musk, Gates, and Zuckerberg have all said they have or likely have ASD. I’m sure there are more.

I’m not defending the original idea, I’m not a fan, but the right special interest, properly directed, has had made billionaires. These were just 3 examples off the top of my head that I heard in passing over the last couple years.


Maybe Musk, Gates and Zuckerberg are neurodivergent, IDK, self diagnosis is often self-serving. I don't think they are billionaires because their powers of autistic hyperfixation were properly directed.

You said there were "just 3 examples of the top of your head" as if there were a much larger pool from which to infer a correlation between autism and wealth. In most cases autistic peoples' special interests don't have million dollar market potential. I suspect the potential for wealth and placement on the autism spectrum are orthogonal to one another, and that factors like education, class and luck play bigger factors.


He's even more wrong when the Python typing system allows us to catch bugs in small scripts.


Like obfuscating text on Twitter, GitHub gists, or using an unreliable E2E encrypted service?

> without creating accounts or relying on any platform to keep it safe

You're still restricted to places where your JS decryption functions can be used. A novel idea would be to put both text and decryption inside a simple URL like a bookmarklet.

> The encryption method could be anything

Insecure then.


Thanks @Disposal8433 Yeah, agreed on the JS limitation — right now it only works where the little decryption script can run in the browser, so it’s not truely universal. On the crypto side though, this isn’t meant to be deep security — just casual privacy. The point was the pattern (encrypt locally, store publicly, key in your head), not using AES-level algorithms.


I had the same reaction. It's a big stretch to call a "tool" 500 lines of JS that could be replaced with a few Bash calls, a regexp, or a small self-contained Python+UV script. Even worse when it's limited in functionality.

We failed at creating automation tools for the users (even if Apple tried that with AppleScript or Automator), but vibe coding throwaway scripts is not the answer.


I can't run a few bash calls or a Python+UV script in Mobile Safari on my phone. That's very much a goal of most of these as well.

I actually have a separate collection of vibe-coded UV+Python scripts on that site here: https://tools.simonwillison.net/python/


It is prohibiting in a few ways: relying on a company in a foreign country, and no alternative if your account gets randomly banned. Also what would happen to developers in embargoed countries?

Those are unacceptable to developers outside of the USA.


Those are good point!


Or yours...


What would you like to see?

Can tell you :)


you're building a tool that is designed to sink its tentacles into peoples' most personal accounts and take unsupervised automated actions with them, using a technology that has serious, well known, documented security issues. you haven't demonstrated any experience with, awareness of, or consideration for the security issues at hand, so the ideal amount of code to share would likely be all of it.


Fair enough makes sense to not have trust!

We like to believe we're pretty trustworthy, and do our best to make everything secure.


i actually really like your product for what it's worth. don't listen to the haters. hackers build things.

i just won't use it, and nobody should, unless they can understand exactly how it works and reason for themselves about the risks they are taking. you clearly work hard and care deeply about what you are building, and it will be very useful. but it has the potential to cause widespread harm, no matter how trustworthy you are, how much you care about it, or what your intentions are.

with respect to user security and privacy, doing your best is not much better than yolo security. the minimum standard should be to research the threat landscape, study the state of the art in methods to mitigate those threats, implement them, and test them thoroughly, yourselves and through vendors. iterate through that process continuously, alongside your development. it will never end. or, you can open source it and the internet does this for you for free. build something people love, grow traction, convert that to money. THEN figure out how to make money from them.. not the other way around. or, more likely, some combination of all of the above.

someone else linked you to simon wilson's lethal trifecta page, i would absolutely start there, and read everything linked as well. pangea and spectreops both do good work in the llm pentesting space, i'm sure there are more.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: