Live data from Hacker News

Viewing profile — niros_valtos

niros_valtos

HN member
Joined
Sun, Oct 17, 2021, 12:37 PM UTC
HN karma
602
Public activity
129 items

About niros_valtos

No profile information was provided.

Recent public activity

  1. 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…

  2. comment
    Comment #48370878

    [flagged]

  3. comment
    Comment #48370861

    [flagged]

  4. 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…

  5. comment
    Comment #48358520

    [flagged]

  6. comment
    Comment #48357975

    [flagged]

  7. 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…

  8. 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…

  9. comment
    Comment #48347891

    [flagged]

  10. 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…

  11. story
  12. story
  13. story
  14. story
  15. comment
    Comment #39353185

    Download the GitHub CLI. Run ‘ gh pr create’. Good luck!

  16. 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…

  17. story
  18. 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.

  19. story
  20. story
  21. story
  22. story
  23. story
  24. story
  25. story