Yeah. I feel a lot like this too. I left my most recent job in May and don’t have plans to return to tech anytime soon. To fill my time and to try to do something actually useful, I decided to start writing about learning more and thinking better.
On the surface, this sounds like a great idea. The problem is that, once you look at the details, you realize there are none.
How is this going to work? Where does that $68bn get re-allocated? Who will benefit from this? What is the economic advantage of investing in transit infrastructure in dollars and cents?
I've seen a few of these proposals that sell hopes and dreams with no discussion of how it's going to work. Until I see that, I can't support this.
Can you clarify what you mean by "transit oriented development"? As a general rule of thumb, 10-20 story tall buildings are an eye sore. I don't think it makes sense to make things denser if it's going to be so ugly that no one wants to live there.
You New Yorkers have a unique perspective of your own on such matters! It's a great town, and you folks up there do a wonderful job of making a body feel welcome. But there's too many tall buildings and not enough tall trees for me to ever want to live there, and I can see why people who like SF for what it is wouldn't want it to follow your example, any more than I want Baltimore to.
I think it's a stretch to say that the peninsula will remain majority single family home cities. Everywhere I look all I see are new apartment complexes being built.
> There's still a lot of work out there that really boils down to basic CRUD and reporting at the end of the day, and developers naturally begin to invent complexities on top of that CRUD to make the work interesting and challenging.
I'd go so far as to say that _most_ work today (at least in startups) is building CRUD apps. The technology has changed, but the work hasn't. Inside of building CRUD apps in Rails, we now build them in React.