@BayAreaREMatt Correct, and the majority of the sales volume in Oakland isn't where you'd expect to see spillover. Just looks at the recently transacted map.
I ate one almond the other day. Then I felt bad about the water usage, so I thought to myself - well I just won’t make the next 15,000 AI queries I was planning on making
https://t.co/mJzmAUkmqi
Note that his other "priorities" are all one paragraph of PR talking points.
Amazing that we live in a nearly failed state (housing, drugs, homelessness, crime, affordability) and all this guy thinks about is regulating the only thing that is actually working.
Just read through Becerra's platform and his only substantive position is he's pro AI regulation.
At what point does the entire tech industry just give up and move? The network effect is great but it is possible to rebuild these things.
Don't talk to me about the weather.
@dd_Angus@mattdorsey@SFPD@SFDAOffice The bicyclist:
1. Was lawfully in a protected bike only lane
2. Proceeded on a green light
The driver:
1. Illegally turned right from a straight only lane
2. Ran a red light
3. Hit a bicyclist
4. Fled the scene
What are you talking about?
@Kazanjy@SFBART You can tell the problems with @SFBART are due to incompetence at the director level because all they'd have to do is a simple eyeball check of their parking revenue statistics and do some napkin math, then start enforcing.
This is literally running a transit system 101 stuff.
@Kazanjy BART commuter here! I park in one of their lots & sometimes forget to pay, nothing ever happens.
So I ran an experiment. For three weeks I did not pay for parking. Never got a ticket or notice. If @SFBART wants to solve its funding problems, maybe start with enforcing parking.
When I joined Google, I found it annoying that:
1. Everyone works in the same repo at head
2. All dependencies are explicitly declared
3. External dependencies are copied in a central third_party folder
4. Everything can be re-built from source
I had changed my mind for all of these points after a year.
@ibab I agree this is due to a data bias. The OSS community (the largest data source) is relatively better at killing requirements, cruft, and other dead weight than big tech. That’s the only way you keep a lean project going.
@ibab More than line count, you start to see cracks when the number of requirements (must do X) and considerations (must decide X or Y) reaches some threshold.
I doubt there is a significant difference in performance over 100k LOC vs 10m LOC codebases, all else equal.
@GergelyOrosz I don’t think it’s as much the non-standard tooling as it is the software bloat in big tech. There are innumerable dead code paths and over-designed spaghetti disasters. These aren’t as pervasive in smaller settings.
I wrote a little about this at https://t.co/reG25YCztp
I know it's terrible politics, but just once I want to see a local politician tell a NIMBY complaining about neighborhood character "I'm sorry you're upset but this development is a good idea that helps people, so we're doing it anyway and you'll have to get over yourself."