• Home
  • Technology
  • Gaming
  • Entertainment
  • World & Business
  • Science
  • Sports
  • AI
HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
  • HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
    • Home
    • Technology
    • Gaming
    • Entertainment
    • World & Business
    • Science
    • Sports
    • AI
    AI

    Lemire Describes 1970s Programmer Influx and Software Mess

    Professor posts about the sudden rise of inexperienced programmers and resulting software problems.

    DL
    1 Source, 25d ago, first seen 25d ago

    TLDR

    Daniel Lemire posted that in the late 1960s and 1970s a rapid increase in programmers followed a prior shortage. He stated that people such as David Parnas faced the resulting difficulties and that far more software was produced with much of it falling apart. Lemire added that the conditions sent Edsger Dijkstra into a depression. The post includes one colorful cartoon illustration as an attachment.

    Combined views

    3.8K

    1 Source, first seen 25d ago

    Combined views

    3.8K

    1 Source, first seen 25d ago

    50 likes
    50 likes
    7 comments
    16 saves
    7 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    7 comments
    16 saves
    7 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    Today's Rank

    —

    Not ranked yet

    Today's Rank

    —

    Not ranked yet

    1 Source

    @lemireIn the late 1960s and 1970s, people like David Parnas faced a problem. A decade earlier there were almost no programmers. Suddenly there were hordes of inexperienced ones. What could have been a golden era was turning into a mess: far more software, much of it falling apart. It sent Edsger Dijkstra into a depression. Does this sound familiar? AI-assisted coding is producing far more code. Whether the projects will work or crumble remains to be seen. There is a danger. I'd like to propose the layered model. Keep a small core that changes slowly and on purpose. For that part you actually read the code. You insist on tests. You can use AI assistance, but there is no vibe coding allowed. Everything else can move fast. There will be bugs, but the AI fixes them quickly. Dependencies should be one way: the outer layers depend on the core. The core cannot depend on the outer layers.

    1 Source

    @lemireIn the late 1960s and 1970s, people like David Parnas faced a problem. A decade earlier there were almost no programmers. Suddenly there were hordes of inexperienced ones. What could have been a golden era was turning into a mess: far more software, much of it falling apart. It sent Edsger Dijkstra into a depression. Does this sound familiar? AI-assisted coding is producing far more code. Whether the projects will work or crumble remains to be seen. There is a danger. I'd like to propose the layered model. Keep a small core that changes slowly and on purpose. For that part you actually read the code. You insist on tests. You can use AI assistance, but there is no vibe coding allowed. Everything else can move fast. There will be bugs, but the AI fixes them quickly. Dependencies should be one way: the outer layers depend on the core. The core cannot depend on the outer layers.