Readit NewsAmsterdam is a great example [0] and well-known for a lot of tourists, with the city center being the tourism hub, the zones around it for living, west/northwest for industry/shopping, south for highrise offices and football stadiums, etc. Most tourists won't go that far out though.
[0] https://www.amsterdamsights.com/about/neighborhoods.html
Everybody loves public transit until they get panhandled for the jillionth time, or they witness (or experience) violence, or some other anti-social behavior sours the whole thing.
I spent some time in NYC during the Giuliani years, after the city did a lot of work cleaning it all up: stopping turnstile jumpers, removing graffiti, more police, etc. It was great. You'd get the occasional guy that jumps on, makes a speech about how he's raising money for something or other, and walks around trying to sell chocolate bars. And there was the occasional dangerous person, insisting on getting up in your face.
So long as this sort of behavior remains at a very low level, something like maybe once every couple of weeks, that's probably okay. But public transit loses all appeal if it happens often. If it rises to the level of violence, everybody starts thinking about the suburbs.
Public transit requires a certain level of unspoken agreement. "We will all behave in this manner." If this unspoken agreement is broken often enough, then it must be enforced. If it is not, and other options present themselves, people will choose the other options.
This happened en masse many decades ago in America. Those that could decamped for other places where their social expectations were met.
I'm a big supporter of urbanism. I loathe the time I spend in my car, and I don't even have that far of a commute, but I have zero other options if I want to live where crime is low and the schools aren't dysfunctional. Until this is addressed, there is no argument about commuter density or efficiency of movement or anything else the proponents of public transit like to talk about that will make a lick of difference.
The worst argument anybody can make is "but that's just life in the big city!" If so, then I'm not going to live and raise my family in the big city. Airy-fairy principles of efficiency or an arguable notion of convenience will not take precedence over safety and quality.
Reason Japanese carpenters do or did that is that sea air + high humidity would absolutely rot anything with nail and screw.
No furniture is really designed from a single tree, though. They aren't massive enough.
I agree with overall sentiment. But the analogy is higly flawed. You can't compare physical things with software. Physical things are way more constrained while software is super abstract.
The other reason was that iron was very expensive in Japan as they had only low quality iron ore.
I know you probably meant "augment fact checking" here, but using LLMs for answering factual questions is the single worst use-case for LLMs.
They were all written by the same guy, Anders Hejlsberg:
https://en.wikipedia.org/wiki/Anders_Hejlsberg
https://news.ycombinator.com/item?id=19568681
"My favorite is always the billion dollar mistake of having null in the language. And since JavaScript has both null and undefined, it's the two billion dollar mistake." -Anders Hejlsberg
"It is by far the most problematic part of language design. And it's a single value that -- ha ha ha ha -- that if only that wasn't there, imagine all the problems we wouldn't have, right? If type systems were designed that way. And some type systems are, and some type systems are getting there, but boy, trying to retrofit that on top of a type system that has null in the first place is quite an undertaking." -Anders Hejlsberg
Nobody's code is that secret, especially not from a vendor like Microsoft.
Unless all development is done with air-gapped machines, realistic development environments are simultaneously exposed to all of the following "leakage risks" because they're using third-party software, almost certainly including a wide range of software from Microsoft:
- Package managers, including compromised or malicious packages.
Microsoft owns both NuGet and NPM!
What developer doesn't use Microsoft VS Code these days?
- SCM tools such as GitHub Enterprise (Microsoft again!)
- The CI/CD tooling including third-party tools.
- The operating system itself. Microsoft Windows is still a very popular platform, especially in enterprise environments.
- The OS management tools, anti-virus, monitoring, etc...
And on and on.
Unless you live in a total bubble world with USB sticks used to ferry your dependencies into your windowless facility underground, your code is "exposed" to third parties all of the time.
Worrying about possible vulnerabilities in encrypted VMs in a secure cloud facility is missing the real problem that your developers are probably using their home gaming PC for work because it's 10x faster than the garbage you gave them.
Yes, this happens. All the time. You just don't know because you made the perfect the enemy of the good.
> Yes, this happens. All the time. You just don't know because you made the perfect the enemy of the good.
That only happens in cowboy coding startups.
In places where security matters (e.g. fintech jobs), they just lock down your PC (no admin rights), encrypt the storage and part of your VPN credentials will be on a part of your storage that you can't access.
Back in the days of DOS I used to do this all the time :)
Most of the windows-based programmers I interact with don't know powershell any better than I do. They use GUI tools for interacting with git and the filesystem.
So for me, git bash for git and filesystem interaction is a superpower in these places.
I could learn powershell, and I'm pretty sure it's much better than bash for scripting, but I'm almost never really scripting in bash anyway, I use tools like F# for that. Powershell seems fine, but it's less well supported on Linux and I don't really need a shell based language.
So in the end, git bash keeps on working and I can focus my learning elsewhere. It's stable, still works the same way 15+ years later, so no need to change.