ELI5: Interest Rates & Bond Prices

Investors like to keep a close eye on interest rates, especially those who hold bonds. The two are closely related. When one goes down, the other goes up. This can cause some confusion. Shouldn't higher rates mean more valuable bonds?

New bonds are issued all the time. It can be weekly, monthly, quarterly - depends on the issuer.

Bonds are essentially loans to companies and governments, where in return investors are paid interest at a fixed rate. If rates rise, bonds issued prior to the hike will provide a lower return than their newer counterparts - becoming less valuable. When rates drop, old bonds will provide a higher return - becoming more valuable.

Let's say you purchased a 10-year bond with a par value of $1,000 and an interest rate of 4%, this equals to a return of $40 a year.

If interest rates rise to 5%, new bonds will be paying investors $50 a year. 20% more than what your bond pays.

If you want to sell your bond, it'll be impossible to sell it for the $1000 you've paid. Things have changed. The market now demands a higher return. Seeing that you can't increase the rate of your bond, you'll need to discount the price to make up for the lower returns. The new value of your bond would be $922.78.

The opposite is also true. If interest rates instead dropped to 3%, you now hold a bond that pays more than the current rate. Meaning you can charge a premium. Your bond will be now be worth $1,085.30.

Comments

Today's Special: Humble Pie

You champion a project, fight for an idea, and then...reality sets in. That churning in your stomach isn't butterflies, it's the realization you've missed the mark. Pride will puff up your chest, and kick in the "defend at all costs" instinct. But arguing with the umpire never changed a call. Admitting you're wrong isn't a sign of weakness. It can strengthen your professional standing. In a world obsessed with the illusion of infallibility, the courage to adjust course is a breath of fresh air. It shows you're confident enough to be wrong, and adaptable enough to learn from it. Do your research, think critically, and stand behind your decisions. But when the data whispers (or screams) otherwise, don't be afraid to swallow that slice of humble pie. Be the first to acknowledge. Don't wait for someone to point out your mistake. Be open, take responsibility, and most importantly, focus on what you're going to do to address it. Don't dwell ...

Starting Really Really Small

On your desk is one of the most intimidating sights known to man. A blank page. The prospect of filling it up with anything resembling decent seems insurmountable. Staring at the long road ahead fills you with anxiety and dread. The first step is the most difficult. So we procrastinate. We " research ", we " prep ", we " plan ". We do everything except tackling the problem. We avoid the pain for as long as we can. To make a blank page less intimidating. Tear it in half. There, half as scary, twice as easy. Still too much? Do it again. And again. Keep doing it until the task is so small that it's too easy not to do. Getting starting is the hardest part. So make the hardest part as easy as possible. This doesn't guarantee amazing results, but it gets you in the game. You can't win if you don't play.

Why We Shouldn't Be Afraid of Ambiguity

Ambiguity. That fuzzy monster that chases us down darkened hallways, whispering doubts about our roadmap and feature sets. You know the feeling. You constantly wrestle with unknowns: Will users like this? Is this the right direction? Frankly, if you had a nickel for every time the answer wasn't crystal clear, well, you might actually want to chase that ambiguity down the hall. But here's the thing: ambiguity isn't your enemy. It's your dance partner. Innovation rarely happens in a land of perfect clarity. Sure, there's a time for well-defined processes. But when you're creating something new, there are bound to be more questions than answers. The key is to learn to waltz with the unknown . Embrace the experiment. Don't be afraid to throw some spaghetti at the wall and see what sticks. Focus on outcomes, not outputs. Don't get hung up on features. What problem are you trying to solve? How will you measure success? Get comfortable with "go...

Herman Ye

Search