Skip to content
  • 7 points on Schools are banning phones in the classroom and it’s paying off in higher test scores in !technology@lemmy.world ·

    Not surprising, but there’s a useful lesson in why it works.

    A ban takes away the decision, and the daily willpower fight against old habits. Same thing I’ve seen in change projects: if the new way depends on people choosing it again and again, it fades.

    Make it the default and it sticks.

  • 2 points on What is the future of software engineering in regards of learning? in !asklemmy@lemmy.world ·

    I wish I’d had an AI assistant when I was teaching myself to code at 14, in a small village with no developers anywhere near me. My first stack overflow came from a recursive call, before I even knew what recursion was. It took me months to figure out. A patient teacher next to me would have found it in minutes.

    That’s how I’d use AI to learn: not “solve this for me” but “where’s the problem? Why? Teach me.” Used like that, it’s the knowledgeable, patient mentor most of us never had. Used the other way, it does your learning for you, and you learn nothing.

  • 1 points on Pitching Linux (and transformations) to people who don't care about Linux: what I got wrong 25 years ago in !linux@programming.dev ·

    Thanks for sharing such a personal story, Repair Cafés are a great idea, especially nowadays when “old tech” is still perfectly usable.

    Curious: what were the biggest challenges you faced when setting one up?

  • 0 points on Longtime Linux Developer Steps Down From Some Roles Due To Patch Flood Caused By AI in !linux@programming.dev ·

    Same here. Vibecoding my own tools is fine, because I’m the one who pays for the bugs. A kernel patch is different: thousands of people pay for them, so understanding every line is the minimum.

    Anyone who sends code to public software should follow a simple code of ethics. A low barrier to entry is great, it’s how most of us started. But the bar for responsibility should rise with how many people run your code, and right now it doesn’t.

  • 2 points on Longtime Linux Developer Steps Down From Some Roles Due To Patch Flood Caused By AI in !linux@programming.dev ·

    It’s an unfortunate news, burnout in open source was real even before AI. Now it has just exploded.

    Reviewing code has always been a bottleneck. AI made sending a patch nearly free, but reviewing one costs the same as ever, and it lands on a few volunteers.

    For code that millions run, someone has to understand every line, so the sender should do that work, not the maintainer. Otherwise you’re just moving the cost onto the people who can least afford it.

    There should be a simple rule: if you can’t explain your patch line by line, don’t send it. And maintainers should feel free to reject any patch by default when the sender can’t explain it.