Wildroot

Queries may use an external AI service. Details

Wildroot Browser

TodayAISimilar posts

Similar posts

The anxiety over vibe coding is eerily familiar to the 1980s anxiety of using other people's code #AI #VibeCoding

Case 1 concerns a compiler. It has been developed by a group A for a Language L and worked very well on computer X. Now another group B has the task to write a compiler for a language L + M, a modest extension of L, for computer Y. Group B decides that the compiler for L developed by group A will be a good starting point for their design, and get a contract with group A that they will get support in the form of full documentation, including annotated program texts and much additional written design discussion, and also personal advice. The arrangement was effective and group B managed to develop the compiler they wanted. In the present context the significant issue is the importance of the personal advice from group A in the matters that concerned how to implement the extensions M to the language. During the design phase group B made suggestions for the manner in which the extensions should be accommodated and submitted them to group A for review. In several major cases it turned out tIn the years following these events the compiler developed by group B was taken over by other programmers of the same organization, without guidance from group A. Information obtained by a member of group A about the compiler resulting from the further modification of it after about 10 years made it clear that at that later stage the original powerful structure was still visible, but made entirely ineffective by amorphous additions of many different kinds. Thus, again, the program text and its documentation has proved insufficient as a carrier of some of the most important design ideas.
Opinion

3 posts close in meaning, closest first

  1. I was sharing with my wife my (current) preferred approach to AI produced code by engineers. It's borrowed from her PhD - thesis defence. If an engineer can defend their code in a thesis defence, I have no concern about how it was produced. What is thesis defence for software changes? They should be able to explain, without using an llm: * What is the objective for the code change * Why did they choose this approach * What other approaches they considered * What unrelated/unexpected things they found along the way * What are the limitations of chosen approach * What is the wider/longer term impact of choosing this approach

    Show more of this post

    * Who else did they collaborate with, or who else understands their chosen approach to be able to answer these questions if needed Notice I don't want them to explain their work. I can read the code and understand it. I want to understand how well researched this approach is, and how well they understand it. I also want to ensure that they have put in at least as much effort (to produce the code or to prepare for the theses defence) as the reviewer will put in. #ai #softwareengineering

    Similar topic and wordingOpinionAI
  2. And I'm not coming at this from a "I'll never use AI, it's evil" stance. I use AI at work a fair bit. But I use it in a way that I still own, deeply understand, and am able to explain and modify anything that I produce - whether I built it with or without AI. Around me I see work being pushed where the author can't answer a few questions about it, it is clearly beyond their usual ability, and has no chance of being maintainable workout AI. This is just lazy folks using AI lazily. I can handle this (at a cost). They don't understand it but I can, and I can make it simpler and maintainable. What really has me reconsidering my approach is the Software Factory approach I am seeing being adopted by some of the smarter people I know. They are actively making a choice that they don't need to know how the system being produced works in details. As long as it produces desired behaviour/output, it is all that matters. #ai #softwareengineering

    Similar topic and wordingOpinionAI
  3. “The economist Sendhil Mullainathan, in writing about the dangers of AI, cited the long-tail phenomenon (which I described in chapter 6) in his notion of 'tail risk’:” «We should be afraid. Not of intelligent machines. But of machines making decisions that they do not have the intelligence to make. I am far more afraid of machine stupidity than of machine intelligence. Machine stupidity creates a tail risk. Machines can make many many good decisions and then one day fail spectacularly on a tail event that did not appear in their training data. This is the difference between specific and general intelligence.»

    Show more of this post

    “Or as the AT researcher Pedro Domingos so memorably put it, 'People worry that computers will get too smart and take over the world, but the real problem is that they're too stupid and they've already taken over the world.’” #MelanieMitchell wrote this in 2019. It’s 2026 and I have not seen any improvement in this regard: no advancement in building systems that understand rather than mimic, and hence remain fragile to the long tail of events absent from the training data. #AI #LLMs

    Similar topic and wordingOpinionAI