• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle



  • I am a little curious about the conditional. I have a suspicion that this is a bit of over engineering.

    The problem you seem to be trying to solve is “I need to access the same data in multiple ways, places, or projects.” That’s what a database is really great for. However, if you just need to combine the same csv files you have on disk over and over, why not combine them and dump the output to a csv? Next time you need it, just load the combined csv. FWIW this is loosely what SQLite is doing.

    If you are defining a method or function that performs these ETL operations over and over, and the underlying data is not changing, I think updating your local files to be the desired content and format is actually what you want.

    If instead you’re trying to explore modules, imports, abstraction, writing DRY code, or other software development fundamentals- great! Play around, it’s a great way to learn how might also recommend picking up some books! Usually your local library has some books on Python development, object oriented programming, and data engineering basics that you might find fascinating (as I have)











  • No, what you mean is YOU use it and you’re assuming most people use GitHub the way you do. GitHub is first and foremost a platform for GIT. Git has nothing to do with releases or file downloads per se. Time spent improving the releases UI is time not spent doing other UI improvements. If you need more proof that it’s not worth it to spend time on the release UI, just take note of the fact that GitHub is not spending time on the release UI. If everyone was using it and it was deficient, do you really think that would be the case?


  • Literally everyone? I’ve been a software engineer for ten years. My company doesn’t use it, and no company I’ve worked for has. I guess they are not part of “literally everyone?”

    Explain to me how GitHub working on one product feature (releases) has no impact on how much they can work on others. Apparently in your rich enterprise software career you’ve found that resources and time are limitless? Or maybe you think it’s trivial for a platform like GitHub to change their UI.

    This smacks of lots junior software engineers I’ve worked with who think problems are simple and solutions are easy because they’ve never actually DONE anything. I get that you’re very convinced that this is easy and cost less but it’s pretty clear to me you have no idea what you’re talking about.