Margin stock accounts also exist, although I don't know enough to know what situations it makes sense to use them in.
I was obviously replying to this part of the parents comment.I'm afraid if this is pushed through, the studios will just switch all online experiences to be fully subscription based. No more purchasing the game, you just pay for a month of the experience.
Say you just started working, have no use for your money and are willing to bet 20k on index funds vs a 90% market drop, you should be able to take 2k in leverage and set up your position be auto closed.
But of course as you have more money this type of market exposure starts shifting as you have shorter timer horizons to rebuild and are instead going into more of a wealth conservation mode.
I don’t understand… do you not go to places where the poor go? Is there no transit to take you to parks and malls and theaters and stadiums? I suspect it’s more that taking your private vehicle is easier and faster, and not because there isn’t service - it probably just sucks.
You can find creation here https://github.com/git-bug/git-bug/blob/master/doc%2Fmd%2Fgi...
And status update here https://github.com/git-bug/git-bug/blob/master/doc%2Fmd%2Fgi...
- error happens, can be attributed to release 1.2.3
- every subsequent time that error happens to a different user, it can track who was affected by it, without opening a new error report
- your project can opt-in to accepting end-user feedback on error: "please tell us what you were doing when this exploded, or feel free to rant and rave, we read them all"
- it knows from the stack trace that the error is in src/kaboom/onoz.py line 55
- onoz.py:55 was last changed by claude@example.com last week, in PR #666
- sentry can comment upon said PR to advise the reviewers of the bad outcome
- sentry can create a Jira with the relevant details
- claude.manager@example.com can mark the bug as "fixed in the next release", which will cause sentry to suppress chirping about it until it sees a release 1.2.4
- if it happens again it will re-open the prior error report, marking it as a regression
Unless you know something I don't, Grafana does *ABSOLUTELY NONE* of that
With vibe coding, you are as much a reviewer/editor as an author, and as an editor should never accept generated code that you don't understand. Happily, the same technology that generated the code can explain the code.
There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.
...
I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it.