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

Literally means excess returns here as well (a better outcome to those that don't review anything).

It was a clearly different unit, look at the wheel caps.


Actually, only the demo car up front and close had different wheel caps. The car that accelerated was similar looking than the one that flew.


I'd repeat the question, according to who is this even likely a materially different car? Why does a wheel cap mean it's a different car? You could make this argument by pointing to literally any difference, like a sticker - it doesn't add an credibility to it.


Write schema/data migration files [with agents] in version control and deploy those deterministically (after review).


I don't want to sound offending, but if that is your own writing style, it makes sense why AI writing resonates with you.


That's not an effect. As both in the case of a dividedend and a stock buy back, the company's market cap drops by the amount of cash that's being distributed out, creating an identical re-buying situation in market cap-weighted index funds. Stock price itself is irrelevant for index fund rebalances (unlike for shareholder returns).


> So for my definition of “everywhere,” with the caveats mentioned above, the following features work everywhere. YMMV.

  .
  ^, $
  […], [^…]
  \*
  \w, \W, \s, \S
  \1 - \9 backreferences
  \b \B
  ? + 
  | alternation
  {n,m} for counting matches
  (...) capturing
Except that these don't work in macOS/BSD sed (even with -E flag):

- \w, \W, \s, \S - need to use POSIX classes instead: [[:alnum:]], [^[:alnum:]], [[:space:]], [^[:space:]]

- \b - need to use use [[:<:]] (word start) and [[:>:]] (word end) instead

- \B - (not a word start/end) no alternatives



It's not documented, but unfortunately neither of these re-signs the commits even if GPG signing is configured. They are based on `git replay`, and that doesn't sign either (at least yet).


How/why did it consume more tokens?


Well, thing is I ask it doesn't things where sandbox fails.

And then it has to bypass sandbox to run those command with elevated permission.

This double tripe boosts token usage.

I don't think average developer workflow can be really limited to a workspace. You'll need commands which touch your system or require more privilege


I think the script would be named as `#` so that it can be called via `\# mycmd` instead of `\\# mycmd`.


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

Search: