It's not theft, it's copying. Two different words, with two different meanings, and different legality, for very good reason. You can only steal things that can be taken away, which is why theft is bad, because it deprives the original owner of something they once had.
Copying does not directly deprive anyone of anything. In fact it just adds more value to the world, and makes it more available to more people.
Nobody can "copy" stuff and put it behind a paywall, because the original is still free. It's the prevention of copying that leads to expression being locked behind paywalls.
It's said that copying disincentivizes creativity and creation, but in practice it does the opposite. Just look at the incredible amount of music, fiction, software, stories, art, and information that have proliferated since the birth of the web.
What copying does do is it indirectly deprives people and companies of the ability monopolize profits on particular expressions without competition. But I'm not so sure that's a bad thing.
For example, look at the software industry. I'm extremely grateful that patents and copyright are so rarely enforced in software and UI design, and that we've all been copying the good ideas that came before us for decades with no consequence. I'm grateful the same is true of food recipes, too. I think the world would likely be a richer one if this was true for most fields and art.
> The question is whether we are comfortable with an economic model where creative and technical labour consistently produces outsized returns captured by capital, not by the people who actually built the thing.
You have two mistakes in your thinking.
1. You assume that people are not comfortable with this economic model, when in fact millions of people are making the choice to be on the labor side of this model on a daily basis, who could actively afford to be on the ownership side.
2. You mistakenly believe that "the thing" that produces returns is the product/service/offering when in reality it's the entire business.
Let's start with #2.
Producing and capturing value is about more than just building the offering, i.e. coding something. Millions of people have coded something "valuable" and made $0, because building something is not enough. You have to make sure people learn about the thing, and they have to find it good enough to pay you for it, and then actually pay you for it, and you have to be able to make this happen repeatedly, a sufficient number of times and at a high enough price point to sustain and ideally grow the endeavor.
This goes far behind simply building a product. It requires building a business.
And let me tell you, my friend, software engineers at FAANG companies are only building the software, not the business. The people building the business are the ones making the biggest earnings.
Creators in every industry do not like to hear this. Take the music industry, for example. Everyone who can sing or create music hates the "middlemen". The record labels and whatnot. The DJs. They hate the grind. Every creator wishes that simply creating was enough, and many naively believe that it is. But we live in the real world, which has these things called markets and people and psychology. Markets are competitive, and people and psychology are complex, and someone who works to build a business (an offering + market research + a marketing/sales/distribution process + a viable business model) is going to beat the pants off someone who only wants to create the offering and do nothing else.
Building a business is incredibly difficult, and incredibly risky.
It's more likely than not that you will lose a ton of money and a ton of time. Most people would rather not face this challenge, take this risk, or endure these losses. Most would rather learn a fraction of the skills required (e.g. just the programming part, just the design part, just the singing part, etc.), then allow someone else to do the hard work of starting the business and turning it into something from nothing.
Most people would rather sell their time and services for a comfy salary instead of trying to become an owner. Which is why there are large numbers of well-paid white collar workers who make this choice every day, rather than quitting to start a business.
This is not slavery, it's people being content with what they have and trading risk for security. (God I hate writing any sort of sentence "it's not X it's Y" because AI has ruined this phrasing.)
“Just become an owner” assumes the barrier is courage.
It isn’t. It’s capital.
Risk looks very different when you’re risking surplus wealth versus when you’re risking your rent, healthcare, visa, and your entire savings in one concentrated bet.
Calling that a simple matter of “choice” is fiction.
Saying most engineers could just become owners if they wanted to is like saying most renters could just buy apartment blocks.
Technically possible. Structurally delusional.
Ownership compounds. Salaries don’t. Equity scales exponentially. Labour income scales linearly. The system is designed that way.
You can defend it as efficient. You can defend it as rational. But pretending everyone is standing at the same starting line deciding between “comfort” and “ambition” is cosplay.
The dividing line isn’t grit. It’s who can afford to fail.
If you're an engineer in tech, you can generally afford to fail. I'm speaking from experience. I didn't grow up rich or anything close to it. I became a founder because "well I can always get a job" was a good fallback plan.
This isn't delusional, this is reality for a huge percentage of tech founders.
Then factor in the fact that it costs very little to start a web/app company compared to traditional brick-and-mortar businesses. And the fact that funding is available (e.g. Y Combinator). And you have a lot of explaining to do for why so many well-paid engineers don't even try to start something.
> But pretending everyone is standing at the same starting line...
No one in this discussion has implied that everyone is starting at the same starting line. It's obvious that having more money makes things easier. As it should, because that's the entire point of money.
But the reality is that there are millions of millions of people in America today, even from the lower classes, who have access to the internet + a laptop + free time + the ability to survive a failure.
How could this ever have been done safely? Either you are pushing the envelope in order to remain a relevant top player, in which case your models aren't safe. Or you aren't, in which case you aren't relevant.
I think right here is high on the list of “Why is Apple behind in AI?”. To be clear, I’m not saying at all that I agree with Apple or that I’m defending their position. However, I think that Apple’s lackluster AI products have largely been a result of them, not feeling comfortable with the uncertainty of LLM’s.
That’s not to paint them as wise beyond their years or anything like that, but just that historically Apple has wanted strict control over its products and what they do and LLMs throw that out the window. Unfortunately that that’s also what people find incredibly useful about LLMs, their uncertainty is one of the most “magical” aspects IMHO.
> prior to reforming society into one that does not predicate survival on continued employment and wages
There's no way that'll happen. The entire history of humanity is 99% reacting to things rather than proactively preventing things or adjusting in advance, especially at the societal level. You would need a pretty strong technocracy or dictatorship in charge to do otherwise.
You would need a new sense of self and a life free of fear, raising children where they can truly be anything they like and teach their own kids how to find meaning in a life lived well. "Best I can do is treefiddy" though..
Ugh, GBNews, outrage fodder for idiots and the elderly with no ability to navigate the modern information landscape.
You can tell it's watched almost exclusively by old people because all the ads on the channel are for those funeral pre-pay services or retirement homes.
> Modern humans live in what would have been historically viewed as a Utopia.
I think about this all the time, and how tragic (comedic?) it is that humanity finally created a Utopian age but most of its inhabitants are ignorant of that fact, and thus don't appreciate it, and instead genuinely believe they live in one of the worst times ever.
We are unhappy BECAUSE it's a utopia, and our brains evolved in a landscape that was ALWAYS trying to kill us. Like an immune system in an overly clean environment starts attacking inert things and creates allergies, our minds have created threats and focused on "relative" scarcity over actual scarcity. Instead of "How am I going to get enough calories to survive this week?" it's "Why does that guy get to be in a private jet and I have to fly coach?"
Yeah, you have a hard life as you type on a device powered by magic with a full belly and a roof over your head in a building that magically heats and cools itself. Compared to our ancestors, who alternated between fighting to not die of hypothermia or starvation or have their infants eaten by predators, you really have it hard dude. That bald guy on the TV has a really big yacht and you don't, and that means your life is a tragedy. I'm really sorry for the suffering you're enduring because you don't get to party all day, every day. Participating in your own survival is truly an imposition that nobody should ever have to bear.
Have you considered that rather than people being ignorant, not everyone lives this average experience, or that some portion of this increase in wellbeing creates collateral damage and those that experience it don't have the same rosy view?
> Imagine taking a picture on autoshot mode and refusing to look at it. If the client doesn’t like it because it’s too bright, tweak the settings and shoot again, but never look at the output.
The output of code isn't just the code itself, it's the product. The code is a means to an end.
So the proper analogy isn't the photographer not looking at the photos, it's the photographer not looking at what's going on under the hood to produce the photos. Which, of course, is perfectly common and normal.
>The output of code isn't just the code itself, it's the product. The code is a means to an end.
I’ll bite. Is this person manually testing everything that one would regularly unit test? Or writing black box tests that he does know are correct because of being manually written?
If not, you’re not reviewing the product either. If yes, it’s less time consuming to actually read and test the damn code
I mostly ignore code, I lean on specs + tests + static analysis. I spot check tests depending on how likely I think it is for the agent to have messed up or misinterpreted my instructions. I push very high test coverage on all my projects (85%+), and part of the way I build is "testing ladders" where I have the agent create progressively bigger integration tests, until I hit e2e/manual validation.
>I spot check tests depending on how likely I think it is for the agent to have messed up or misinterpreted my instructions
So a percentage of your code, based on your gut feeling, is left unseen by any human by the moment you submit it.
Do you agree that this rises the chance of bugs slipping by? I don’t see how you wouldn’t.
And considering the fact that your code output is larger, the percentage of it that is buggy is larger, and (presumably) you write faster, have you considered the conclusion in terms of the compounding likelihood of incidents?
There's definitely a class of bugs that are a lot more common, where the code deviates from the intent in some subtle way, while still being functional. I deal with this using benchmarking and heavy dogfooding, both of these really expose errors/rough edges well.
"I push very high test coverage on all my projects (85%+)"
Coverage doesn't matter if the tests aren't good. If you're not verifying the tests are actually doing something useful, talking about high coverage is just wanking.
"have the agent create progressively bigger integration tests, until I hit e2e/manual validation."
Same thing. It doesn't matter how big the tests are if they're not testing the right thing. Also why is e2e slashed with manual? Those are orthogonal. E2E tests can [and should] be fully automated for many [most?] systems. And manual validation doesn't have to wait for full e2e.
My approach is similar. I invest in the harness layer (tests, hooks, linting, pre-commit checks). The code review happens, it's just happening through tooling rather than my eyeballs.
Exactly this. The code is an intermediate artifact - what I actually care about is: does the product work, does it meet the spec, do the tests pass?
I've found that focusing my attention upstream (specs, constraints, test harness) yields better outcomes than poring over implementation details line by line. The code is still there if I need it. I just rarely need it.
People miss this a lot. Coding is just a (small) part of building a product. You get a much better bang for the buck if you focus your time on talking to the user, dogfooding, and then vibecoding. It also allows you to do many more iterations with even large changes because since your didn't "write" the code, you don't care about throwing it away.
> All of them suffer from thinking their money makes them somehow better.
Let's assume they think they're better than others.
What makes you think that they think it's because of their money, as opposed to, say, because of their success at growing their products and businesses to the top of their field?
Do they talk about money that much? 99.99% of the people I see talking about money (especially other people's money and what they should be doing with it) are non-billionaires.
The entire point of comparison is to be able to point out similarities between two different things.
If you ignore the specific similarities being pointed out (learning and training work similar in different mammals), and you instead focus on the most offensive differences you can think of (dogs are lesser intelligent creatures than man), then of course you can find a way to be offended.
But doing so is optional, FYI. And counterproductive to an interesting conversation as well.
Note the word "future" not "present". People are making a prediction of where things will go. I haven't seen a single person saying that Gas Town as it exists today is ready for production-grade engineering project.
reply