home.social

#linesofcode — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #linesofcode, aggregated by home.social.

fetched live
  1. Ah yes, the gripping saga of "Lines of Code" 🌟, a tale as ancient as the early 2000s. Who knew counting code lines was still a thing? 🎉 Spoiler: it's not, but hey, at least it finally got a PR makeover! 📈💼
    curlewis.co.nz/posts/lines-of- #LinesOfCode #PRMakeover #TechHistory #CodingTrends #SoftwareDevelopment #HackerNews #ngated

  2. Ah yes, the gripping saga of "Lines of Code" 🌟, a tale as ancient as the early 2000s. Who knew counting code lines was still a thing? 🎉 Spoiler: it's not, but hey, at least it finally got a PR makeover! 📈💼
    curlewis.co.nz/posts/lines-of- #LinesOfCode #PRMakeover #TechHistory #CodingTrends #SoftwareDevelopment #HackerNews #ngated

  3. You point exactly to the crux that not many non-developers catch:

    Code is NEVER the product, what the code does is the product.

    Therefore, 'Lines of Code' is a totally ridiculous KPI.

    A good developer spends a lot of time REDUCING the Lines of Code, in order to optimise response times.

    Which user cares about how many lines of code it took to write the program that they are using? Users care about functionality and responsiveness.

    @gooba42 @molly0xfff
    #Programming #LinesOfCode #KPI

  4. You point exactly to the crux that not many non-developers catch:

    Code is NEVER the product, what the code does is the product.

    Therefore, 'Lines of Code' is a totally ridiculous KPI.

    A good developer spends a lot of time REDUCING the Lines of Code, in order to optimise response times.

    Which user cares about how many lines of code it took to write the program that they are using? Users care about functionality and responsiveness.

    @gooba42 @molly0xfff
    #Programming #LinesOfCode #KPI

  5. Today a had a revelation that reduced 3 from one of the of (I still need to push the change to the development branch of codeberg.org/RyuKurisu/autorot )

  6. For the last 50 or so years, #SoftwareEngineering has been largely about how to write fewer #LinesOfCode, to minimize the amount of #code to #maintain, and to minimize the number of #bugs.

    Now with #Copilot and #ChatGPT, people seem to have forgotten this, and are trying to increase the number of lines of code a #SoftwareEngineer produces per day.

    Can you see where this leads to? What is the situation a company making use of these #technologies will find itself in next?

    I'm just saying software engineer #unemployment isn't going to be it.

    I'm not saying these technologies and #tools aren't useful; clearly they are. I have used them a lot for different purposes. They can help in #teaching software engineering, and any other topic, for example, if it doesn't matter that the material is a few years old.

    We can finally have decent #chatbot #ProgressiveUserInterfaces which understand what the user wants, and understand the system they interface to.

    These technologies will also evolve fast and ultimately they will change everything.

    It's just that the first ideas people got of "fewer software engineers are now needed" and "now junior engineers can do everything" are grossly unrealistic. I don't mind people testing that though, feel free to make bets.

  7. For the last 50 or so years, #SoftwareEngineering has been largely about how to write fewer #LinesOfCode, to minimize the amount of #code to #maintain, and to minimize the number of #bugs.

    Now with #Copilot and #ChatGPT, people seem to have forgotten this, and are trying to increase the number of lines of code a #SoftwareEngineer produces per day.

    Can you see where this leads to? What is the situation a company making use of these #technologies will find itself in next?

    I'm just saying software engineer #unemployment isn't going to be it.

    I'm not saying these technologies and #tools aren't useful; clearly they are. I have used them a lot for different purposes. They can help in #teaching software engineering, and any other topic, for example, if it doesn't matter that the material is a few years old.

    We can finally have decent #chatbot #ProgressiveUserInterfaces which understand what the user wants, and understand the system they interface to.

    These technologies will also evolve fast and ultimately they will change everything.

    It's just that the first ideas people got of "fewer software engineers are now needed" and "now junior engineers can do everything" are grossly unrealistic. I don't mind people testing that though, feel free to make bets.

  8. Tragically, they got the database back online pretty quickly so I've been working for the rest of the workday, haha.
    Porting auto-generated #SQL from a crusty old ETL tool to, well, just SQL is part satisfying, part annoying. So many fields being selected multiple times, so many strange order-by clauses that need to be translated into deduplication/filtering rules; a real net-negative #LinesOfCode task!

  9. Tragically, they got the database back online pretty quickly so I've been working for the rest of the workday, haha.
    Porting auto-generated #SQL from a crusty old ETL tool to, well, just SQL is part satisfying, part annoying. So many fields being selected multiple times, so many strange order-by clauses that need to be translated into deduplication/filtering rules; a real net-negative #LinesOfCode task!