Leverage is great when prices are increasing, but not when prices are moving in the opposite direction. The recent 40-year trend of decreasing interest rates lulled a lot of people into the belief that real estate leverage is an unalloyed good.
> I bought my current home in 2011 for $420k, and the Zillow currently estimates its value at $757k.
Well yeah, in the last 20 to 30 years in most countries the story has been the same. My parents bought a house in Brazil in the early 90's for 30k and we're now selling it for 400k. My relatives in Australia bought a house in Adelaide for 400k around 5 years ago. Prices exploded there and it's now around 700k. They got 300k dollars in a few years while actually earning less than that in salaries over the same period.
On the other hand, me, in Europe, managed to lose money on a house I bought 10 years ago because I overpaid (at the time it was really hard to buy as competition was huge) and after COVID, prices in my region fell 20% and never recovered... Also, I invested too much on a new building in the property which people in this country don't actually value a lot, so the investment did not pay off.
But before that I had made 60k on an apartment in just 2 years. So, while I know too well that the housing market can be unpredictable, I would continue to bet on it going up in most markets since the conditions which made prices increase have not changed.
> I would continue to bet on it going up in most markets since the conditions which made prices increase have not changed.
I think they have. As mentioned above, the past 40 year trend of declining interest rates appears to be at an end. It was the most significant factor in rising prices in my opinion.
You also have to factor out inflation over those periods of time, as often it turns out the return is relatively anemic, but the time periods are long.
>> Leverage is great when prices are increasing, but not when prices are moving in the opposite direction.
This.
I worked for a medium sized company in the early aughts. It was a family owned business. The eldest brother was the owner and we often had lunch and he would tell me that once I make x amount, then I should buy this kind of real estate. When you get to this xx amount, then buy this kind of real estate. Fuck the stock market, only real estate goes up in value every year like clockwork. At the time he had several rental properties and three or four houses located all over the country.
That was until 2008.
Its funny, I ran into him at an architecture conference a few years back and one of the first things he said to me was, "Remember that real estate advice I was giving you? You can completely ignore that now!" and we both had a good laugh about how drastically the market had changed since 08'.
Sounds like your friend did something wrong with his investments. I had rentals before 2008, and bought more during the crash in South Florida for pennies on the dollar. It was a great time to buy.
In some states (California being one) the original mortgage on a house purchase is non-recourse. This means that the bank cannot come after your personal assets in the event of default. Yes your credit gets dinged but the leverage of a home loan is fundamentally different than a margin loan in the stock market.
> Aren't Cascade Layers [1] a more reliable, native solution
Like many new-ish CSS features, adoption is low; around 4-5% from a crawl of 17 million sites [1]. It's been available in all major browsers since 2022.
I'm generally addressing developers who are never going to use any (or very little) modern CSS [2]. There was a thread on HN where some participants complained about "all these newfangled CSS features". Several didn't see the need to learn CSS Grid, even though it's been available for nearly 10 years. (Aside: I really disliked the floats/tables-for-layouts era, with the requisite IE hacks.)
There are lots of developers who don't see a need to use features they weren't using in the late '90s or early 2000s. For a lot of them, they'd rather use the devil they know.
There’s a huge gap between web developers who speak at web conferences, appear on CSS-themed podcasts, and who are members of standards bodies vs the 9-5 developer that works for some insurance company or school, who's not a CSS enthusiast or hobbyist. Using ITCSS would be awesome them.
Finally, there's nothing unreliable or non-native about ITCSS; it's just CSS where the layers are in specificity order. It doesn't get any more native than that.
Yep, they solve the same problem. I built my blog on Harry Roberts' ITCSS paradigm some ten years ago, and found it extremely easy to migrate to cascade layers. They're an underutilized solution to addressing growing specificity.
They're admittedly less useful if you're already using component-based design. That's closer to something like BEM in hyper-targeting each element.
This was my gut reaction as well as an eInk enthusiast, but I think the author is looking for something quite different. As much as the rM is a calmer, slower-paced device by design, it's still a device with a screen that doesn't have the same physical affordances and spatial flexibility as pieces of paper.
I agree, absolutely love my reMarkable for those reasons, as well as not needing to manage the _annoying_ physical properties of paper (storage, organization) any more
RSS is actually one of my favourite uses for the tablet; I built a little service that builds a pdf "newspaper" twice daily and sends it to Google Drive. Very nice to read my feeds on the rM2 instead of a glowing screen
Hi, hyperpaper creator here– sorry it didn't work for you :(
Just curious if there were any problems specifically with the planner, or if it was just the fact that the rM really didn't work for you at all? Always looking to improve it and fill in any gaps in the product.
Also when did you try it? Because I will admit the first version was definitely clunky
The Swedish, rather short-lived but very influential, magazine Pop voted There's a Riot as the best album of all time in 1994. That list had a huge effect on a whole generation of Swedish music fans.
I've been using "pdfcpu optimize" as a post-processing step for dynamically generated pdfs for several years now. Simple, well-documented, and fast. I've been very happy with it
I will add a +1 to your recommendation as well, his blog has been my favourite way to keep up with the AI landscape over the last 18 months. Just the right level of detail and technical depth for me
Yeah, honestly the answer is mainly not having a proper job (I don't have anyone who can tell me how to spend my time) combined with constructive procrastination: I've not been making nearly as much progress on my main projects over the past couple of months because there's been way too much stuff I want to write about.
I can write fast because I've been writing online for so long. Most short posts take about ten minutes, longer form stuff usually takes one or two hours.
I also deliberately lower my standards for blogging - I often skip conclusions, and I'll publish a piece when I'm still not happy with it (provided I've satisfied myself with the fact checking side of things - I won't dash something out if I'm not certain it's true, at least to the best of my ability.)
One thing I'd love to know - how do you balance time spent "building" vs. time spent "researching"?
The writing, I understand - you do it relatively quickly because of a lot of practice. But I feel like just reading up on the AI news every week takes up a significant amount of time - time that can't be spent researching/building things.
Having relevant projects is key. My https://llm.datasette.io projects gives me the ideal playground for trying stuff out - any time a new API model comes out I can spin up a new plugin to for LLM, which is a great way to try the model with limited development time (most API plugins are a few dozen lines of code).
I've managed to balance building vs writing a lot better in the past - I lost that balance in November and December, I'm trying to get it back for January.
Oh that's cool. We've been blogging about AI eng recently, but the project is often "try this idea/tool/library in order to write a blog post about it".
Having some kind of standard "I need to integrate this new thing with an existing codebase" makes a great standard project.
reply