Qwen is just crushing it overall. I regularly use 3.7-flash for everyday coding needs and it gets the job done.
210 karma · joined April 14, 2015
[1] https://calculatedrisk.substack.com/p/new-home-sales-decreas...
- back in April, moved 401k fund from S&P allocation to cash equivalent (2% yield). Note: this wasn't a cash out, just reallocation.
- Bought long-dated treasuries (10 yr and 30 yr). Allocated through July and August. This one is not doing well, but allocation was sized appropriately (< 2% of portfolio).
- pooling any excess capital in a savings account until volatility calms down.
- have a couple rentals and plan to continue holding. It will be interesting to see some buying opportunities in the upcoming year or two.
Why does this reduce the amount of funds to the treasury? The losses are on the Feds balance sheet. My understanding is that the Treasury is not involved here, but the article hints at them being affected. Is it implying that treasury yields will rocket higher???
> In that scenario, expect officials to face tough questions from Capitol Hill to explain why they've lost billions of dollars on behalf of the American people.
If the Fed takes a loss, doesn't this mean that base money supply increases? Sure it will be drawing liquidity out of the system, but in the long run, it will leave more money in the system compared to where they started with QE.
The best thing you can do is be open to hearing all opinion/theories. Some people will contradict others, but over time you figure out who is right and who is not.
In addition, I also watch a few indices in my stock app for a high level overview. These are the treasury yields, corporate credit spreads, dollar index, s&p 500, nasdaq, etc. I used to follow much more, but it's not needed for higher level macro.
When I'm ready to commit:
1. `git diff` to get an overall picture of what changes were made. Which parts of this diff can be packaged into an isolated commit?
2. `git add -p` This is where I selectively stage bits.
3. `git diff --cached` to verify that the staged items are all in place
4. `git commit` with a detailed message.
5. Repeat steps 1-4 until all changes have been committed.
6. `git fetch origin main && git rebase origin/main`
7. Finally, `git push`
When PR feedback is left by peers, some teammates prefer you to not rewrite commits and force push. This makes re-review easier for them (especially if you use the Github features around PR review).
I opt for rewriting commits if it's okay with team members. This way you don't have "fix typo" commits getting merged into the main branch.
Edit: formatting
It looks like artists are able to publish songs under other existing artists?
For a company that has hundreds of engineers, with daily continuous deployment, it helps to have certain in-development features gated behind flags. When it comes time to deploy these new features, they can gradually be rolled out to users. If the feature starts triggering exceptions, it's very easy to scale back.
Once the beta feature becomes stable, often the feature is removed (along with all logic in the source code guarding this feature).
Similarly, for A/B testing, the feature flagging and logic is removed once a test is deemed to have either passed or failed the A/B experiment.
Like anything else in software, feature flagging can incur technical debt if not properly maintained.