I'm concerned about these laws and their implications for privacy, but as a parent, I'm not sure what you mean to say parents should parent. How? What should the parent do? How would you recommend a parent protect a 13 year old who spends their time in their room and out with their friends on their phones?
Tell me you don't have children without saying you don't have children.
In many places it is essentially impossible for children (even younger than 13) to have a normal social live without access to a smart phone. Just some examples, many public transport providers are moving to apps as the only way to pay for fares, nearly all communication for sports clubs happens through messenger platforms, school information is typically distributed via apps as well and the list goes on (I have not even touched on the kids own social interactions).
The irony is that the people who say "parents should parent their kids online activities" the loudest, largely grew up with unrestricted computer use, in chat rooms, weird corners of the internet all by working around any restrictions that parents tried to put on them. Mainly because they were much more computer literate then the older generation.
They get them from their friends at school. I can’t be with my son every waking moment of every day and it’s a ridiculous stance to tel me to do so. I’m also not the only parent I’ve met who wants to be able to limit my child’s access to garbage like social media and Youtube online.
What you’re proposing is similar to a “Google Free Village.” What we need is something that lets parents have some control by proxy without violating the privacy of the child or anyone else. I believe it’s possible to do so.
The Internet that we grew up on has been totally subsumed by scumbag marketing to the point that it’s unavoidable. It’s an addictive substance now. Stop pretending like the ways of the 90’s and 2000’s are still accessible.
I have a different solution to your other repliers: do nothing, your kid will be fine in all likelihood. If you must satisfy the politician's syllogism, set some time limits and make them touch grass. But a thirteen year old oughtn't be parented like a three year old.
Age verification kind of disgusts me and your kid will probably be fine
Isis did manage to recruit young men in the UK via telegram (OK, you just said “in all likelihood“, maybe I’m tossing you the exception that proves the rule)
Thanks for sharing. I appreciated getting different perspectives. I come down on ultimately this is lying and I don't see how lying to oneself is going to be helpful.
Terrific point. I wonder if that's true for any of today's chatbots, in any exchange. Aren't they always pretending to be a thing they're not? A companion, a person, a "s/he" not "it"?
But to push the analogy a bit. If you are rowing on a lake with motorboats, it is a totally different experience. Noisy, constant wake. We are part of an ecosystem, not isolated.
Growing up, the lakes in New England were filled with sailboats. There were sailing races. Now, its entirely pontoon boats. Not a sailboat to be found.
The lake is not however yours to dictate how others will move along. Imagine if the horse owners decided in such an analogy not to allow cars on the road because they noisy and "totally different experience".
You want a pre-AI experience? Feel free to code without it. It's definitely still doable.
nah. tell him, you're in a race. others are using motorboats. the last to reach the finish line loses their salary.
that's a better analogy, or at least what a lot of people think the analogy is.
From my experience in some large tech firms, you could easily cut 20% of the workers and not see much impact. There is so much bloat, process-people, meetings-people, etc... Even if the cuts aren't from AI, execs will use AI as a reason to make these cuts.
Yep - IME the trick is that fixing a bloated company is 2 parts: laying off bloat, and fixing the bad processes / restructuring the company to not need so much bloat in the first place.
I’ve worked at a company that pulled the layoff lever a lot but never did the hard work of investing in fixing the broken stuff… the layoffs actually just made everything worse.
If you have a team whose job is to put duct tape on the widget when it leaks, and you lay off most of that team without fixing the widget, your leak gets worse because you have fewer people with duct tape.
What you need is find people who can fix the widget, then fire all the duct tape people.
The duct tape people are generally drowning under all the work they're doing, and they'd be fine to keep doing other productive stuff.
There's always going to be duct tape stuff around, and you don't want the people who can actually fix widgets to wind up running around with their hair on fire applying duct tape to keep it running without any time to fix widgets.
And when there's too much duct tape jobs going around the widget fixers may take a look at it all and decide they don't get want to get stuck with applying duct tape once all the duct tape appliers are fired, so they just skip to some other job.
Every big company I’ve worked for has an immense about of bloat. Whole departments that exist just because someone wanted it to exist at some point in time.
The health of an organization is often linked in their ability to fire people.
Thank you for sharing this. I found some good articles in what you shared. The long lists of places to post are not that helpful. I've poured through 100 of them in the past and only the top 20 make a difference, you might want to update the list to prioritize. I tend to point Claude Code or Codex at these lists, have them evaluate the scores of the sites and give me a priority list.
This is not my experience either. If you put the work in upfront to plan the feature, write the test cases, and then loop until they pass... you can build a lot of high quality software quickly. The difference between a junior engineer using it and a great architect using it is significant. I think of it as an amplifier.
> If you put the work in upfront to plan the feature, write the test cases, and then loop until they pass...
it can be exhausting and time consuming front-loading things so deeply though; sometimes i feel like i would have been faster cutting all that out and doing it myself because in the doing you discover a lot of missing context (in the spec) anyways...
reply