Viewing profile — niros_valtos
niros_valtos
HN member- Joined
- Sun, Oct 17, 2021, 12:37 PM UTC
- HN karma
- 602
- Public activity
- 129 items
- HN profile
- View on Hacker News ↗
About niros_valtos
No profile information was provided.
Recent public activity
-
comment
Comment #48406750
I think that the cost of Opus is already prohibitively expensive, so not sure how that would compare to Mythos. Check this calculator- it shows that a company with 100 devs can hit…
-
comment
Comment #48370878
[flagged]
-
comment
Comment #48370861
[flagged]
-
comment
Comment #48370848
This is the supply chain problem climbing up a layer. We spent a decade learning not to pipe random scripts into a shell, and now agents will happily read a repo's files as instruc…
-
comment
Comment #48358520
[flagged]
-
comment
Comment #48357975
[flagged]
-
comment
Comment #48347969
The line I'd draw is accountability: who owns it in prod at 3am. Vibe coding is fine for throwaway and prototypes, and it becomes a problem when the prototype quietly turns into th…
-
comment
Comment #48347922
We hit this too, and what helped wasn't more reviewers. We pushed the trivial checks (style, obvious bugs, secret and other deterministic scanning) onto automation so humans only l…
-
comment
Comment #48347891
[flagged]
-
comment
Comment #47096421
Definitely not a surprise they ship it. This is manageable for a small subset of repos scanned once. Reality is that code changes frequently and such rescans are expensive especial…
- story
- story
- story
- story
-
comment
Comment #39353185
Download the GitHub CLI. Run ‘ gh pr create’. Good luck!
-
comment
Comment #39336485
This is great! Github Copilot used to summarize our PRs - I think it can work perfectly as a Github workflow to add comments to newly opened PRs. Can be a nice experiment to use mu…
- story
-
comment
Comment #37385915
The risk severity determination is interesting! If the token of the current user has a site admin permission, the risk is higher.
- story
- story
- story
- story
- story
- story
- story