No, they're saying that it was misleading. OP said "I'm building an open source Google Photos alternative" and surprisingly didn't say "based on Immich". This dramatically changes the evaluation of "open-noodle".
We're now in an era where LoC is easy and design is hard[1]. Starting with an existing project means using an existing design, where someone else has already made many/most of the difficult decisions.
10Xing code without caring about design/UX/DX is trivial. Literally anybody with a token budget can do it. But they probably won't ship a good project. Not with current frontier models.
[1]: design has always been hard. But now it's even more difficult because of code veloocity and because LLMs are happier to work with bad code than humans. It's never been easier to go deep into rabbit holes without noticing a single issue.
Pretty much every example in this thread is "I forked some existing project and made changes I like".
The main thing they dont realize is:
1. These are mostly superficial changes.
2. The only thing they 10xed is their ability to "start" on something.
3. They have not produced actual value. Their project/fork is just a version they think they prefer. But It is less maintainable, and less robust/useful for others due to its specificity.
My observations is that consistently these arguments are made by: inexperienced devs who simply dont understand what it takes to produce value in the real world.
LLMs CAN 10x you (in very specific areas like prototyping), IF you understand how to deliver this value, but that is the hard part. It has always been the hard part.
Because they're taking water from already parched regions, often pumping it out of the ground. Even if the water did come back locally as rain (it doesn't), it still makes it impossible for people to live off the same aquifers and water sources sustainably.
To be fair if you are evaporating water you could be losing some of it outside of the Great Lakes water basin, you are increasing the evaporation rate above what is natural for that area of land.
However the place for that to be least likely to be a problem would be Wisconsin with their evaporated water blowing east over top of the Great Lakes 90% of the time and any excess humidity will rain back down or slow down lake evaporation because the air over the lakes is already saturated with humidity most of the time.
But there still can be a problem if all that water is being pumped from deeper underground aquifers instead of surface water, so the source still matters. Those aquifers still should replenish fairly quickly in that area, but draining aquifers can happen in decades if the demand is there, while replenishment from non-surface aquifers can take hundreds of years even in water filled areas. And in certain ground compositions, underground aquifers can collapse and subside if the water is mostly drained, never again being able to hold that much water again and causing changes in surface topology.
I disagree I drive through there every winter and the lakes are very large. The ecology of the valley is dry but nowhere near as dry as say the mojave just to the south.
We're now in an era where LoC is easy and design is hard[1]. Starting with an existing project means using an existing design, where someone else has already made many/most of the difficult decisions.
10Xing code without caring about design/UX/DX is trivial. Literally anybody with a token budget can do it. But they probably won't ship a good project. Not with current frontier models.
[1]: design has always been hard. But now it's even more difficult because of code veloocity and because LLMs are happier to work with bad code than humans. It's never been easier to go deep into rabbit holes without noticing a single issue.
reply