188 karma · joined December 18, 2025
However, if you would have taken the time to read the thread, you'd have known that I already pointed all that out in my very first comment. The forest was seen all along. The only reason that the other thought it wasn't seen was due to not understanding basic math. And here I guess because of a penchant for trolling?
Disagree about what? You've certainly recognized that professional engineers have tried to usurp the term for their own devices, but that was already called out earlier. There was never a disagreement there. The word "engineer" predates societies of engineers by several hundred years or more so there is no claim that those societies came up with it, so there is nothing to disagree about there either.
> Doing a brick layer training doesn't make one a construction builder.
If someone goes to a bootcamp and then, following that, sits on the couch watching TV until their end of days then you're right that they would not be an engineer. But I have never seen anyone claim that they are something when they aren't doing it. Someone who worked at McDonalds when they were 14 years old and never again don't still call themselves a fast food worker when they are a 50 year old CEO, so I am not sure this take logically follows. It was implied that there is associated action.
But it remains that 6 days per week was the norm prior to 1938, so 48 hours would be typical. We're talking about 40 hour weeks being typical. Stay on topic, my man. The 40 hour work week was not won, unless you think the Great Depression was caused by a labor uprising?
The 40 hour work week came in 1938. This is even echoed in the original link, as mentioned earlier.
What do you mean won? The 40 hour work week was instituted during the Great Depression (hence why you see 1938 in the link) to try and get more people back into the labour force. The idea was that, like, if those working 60 hour weeks were forced into working 40 hours then 20 hours would open up for someone else, giving them some spending money to open up the economy again.
The 40 hour work week was originally conceived of by labor, which may be what you're thinking of, but it wasn't put in place for them. That was for businesses so that they could have more customers.
We're still working this hard because we, as a group, want to. It is as simple as that.
The hardest part, by far, was ensuring you were delivering value. It was, and is, all too easy to build something technically impressive but completely useless.
Verification isn't nearly as hard. We understand very well how to minimize the chance of error. With humans involved there is still room for mistakes, of course. There is no such thing as a panacea. But the space for failure here is significantly smaller than in the above.
> it's hope and prayers that the software is correct.
I don't think anyone has thrown away their verification systems. If anything, they've doubled down. And for what mistakes can be made within verification, LLMs are quite good at recognizing those mistakes, so it is likely that software has never been closer to being correct. There is still no such thing as a panacea, but we're a long way from relying on hopes and prayers.
? 5220-2500-300-200-200=2,020
> before you've even bought any food
It is unfortunate you left out food as a core cost so that we could see what you think is the true discretionary income, but the internet suggests €450 is a reasonable figure for a single parent. It's what we have so we we'll have to run with it.
That leaves nearly 20,000 per year after the essentials are paid for. I wouldn't have a clue how to spend that much, aside from investing it which only serves to push your income even higher later. What are you buying, exactly?
Yes, this maps quite nicely to SQL. Consider this pseudocode[1]:
for customer in (select distinct c.customer_id, c.name from customers c natural join purchases p natural join addresses a where p.purchased_at >= last_year and a.city = 'Oregon') {
println(customer.name)
for purchase in (select date, amount from purchases where customer_id = customer.customer_id and purchased_at >= last_year) {
println("\t"+purchase.date+": "+purchase.amount)
}
println()
}
I know, you're already recoiling in horror. But that's because you've grown accustomed to having to deal with shitty implementations of SQL. It is recognized that you cannot actually write code like that under those shitty implementations because your program will quickly grind to a halt as soon as you gain a few customers, but the point here is to stop using shitty SQL implementations and embrace SQL as it as it was actually intended to be used.> But in my opinion, this does not mean that SQL should not have provided a native solution for this.
SQL does provide a native solution. But it seems your argument is, perhaps, that it should formally define a way to hack around shitty implementations? Why not use the right tool for the job instead?
> I also think that SQL teaching generally emphasizes joins as the natural way to work with relational databases way to much.
Agreed, and I am suggesting that is because of the hacks required to work around the reasons why you cannot write the above code under shitty implementations, which has lead to many to conflate joins and view aggregation.
If you want something like the above except using a declarative language instead then you can put something like GraphQL in front of it. What are you really gaining by turning SQL into GraphQL? SQL is not intended for graph databases. It is a different tool for a different job.
[1] The need for distinct here is SQL's actual flaw. If it were truly relational like it likes to pretend to claim to be that would be unnecessary. It brought the relational calculus but not the relational algebra, which leaves a funny impedance mismatch. You can deal with that in the small scale well enough, but as queries become complex they become hard to reason about because they don't behave like the expression suggests. Which serves as a good corollary as to why turning SQL into GraphQL is unwise when it doesn't have a graph foundation. Primitives best match the primitives. You can layer the abstractions on top, where you can take responsibility for the leaks, as your specific needs dictate.
But they do still need the job shop machinist which fill essentially the same niche using slightly different tools (mills and lathes rather than forges and hammers). Is your 16 year old implying that LLMs are the programming equivalent of a mill/lathe in metal working?
So you're right. Without AI the average lazy developer would write 50k implementation lines of code and 0 lines of test code, and now they have 450k lines of test code in addition to their 50k of implementation code. It might not be great test code, but I know which I'd still rather have (hint: the tests).
Verification isn't a panacea though. The hard lesson everyone learns when they first start taking an interest in verification is that perfect verification is fundamentally impossible.
It is a higher level concern so that isn't a bad thing. SQL is focused on giving you a view of your data. Whereas you want to combine many different views. That is where composing many different queries should be seen as quite natural at the interface point, not a shortcoming of SQL. If that composition isn't natural, you may want to take a closer look at your application's architecture.
> but then I am implementing what essentially amounts to a join myself
Joins and aggregated views are very different concepts. I think this misunderstanding, which is one I've seen many times before, stems from the hacks used to work around the aforementioned problems. Many have come to believe those hacks actually how SQL is designed to be used, not the hacks that they are.
> I have not seen this in any other general interface for relational databases.
Oracle has their thing. Its name escapes me at the moment. Postgres has json_agg/jsonb_agg and similarly SQL itself has array_agg. Lots of options out there.
But it's not only a question of if it can be done, but if it should be done. There are a lot of other advantages to moving query aggregation out into another application. There is a reason why we stopped sticking SQL servers directly in front of the clients and it isn't just because of SQL using a table representation.
Because you don't need nested results. You can fire off another query.
Although I am venturing to guess that you feel you need nested queries because you're doing doing something stupid like trying to send SQL queries over the network where the cost of firing off another query becomes a great performance burden. But the answer to that is don't do that. SQL was specifically designed to be run on the same machine as your application.
If you need to present the data to network clients where nesting is necessary for performance reasons, turn your application into the network database service that produces nested data (the "API server" as the kids call it). Leave the SQL as an implementation detail hidden behind the scenes.
The second biggest flaw, which isn't really about SQL itself but in implementation, was attaching SQL to the network where latency starts to become a problem. That requires hacks to work around. This is likely this is why you're seeing data duplication — trading all that duplication to avoid the latency problems that wouldn't be a problem if you kept it on the same machine like SQL originally intended.
Realistically, the question isn't meaningfully answered in isolation. One would have to see the bigger picture to put it into context.
It is absolutely true that someone else's life doesn't define their own future path, but that doesn't mean they don't latch onto those stories and project the negativity onto themselves. One cannot see the future, so it is quite common to look to others to predict what the future may hold. As you point out, the future is often completely different to what you imagined, but it is what you are imagining that shapes how you feel.
In reality the people would likely revolt by no longer recognizing private ownership of capital if that were to happen, but technically they don't have to. If they truly believe in capitalism — or, as it pertains to the discussion, there is an army forcing them to believe — they can continue to uphold the right for that private entity to own all the capital.