• 6 Posts
  • 623 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle



  • All banks I’ve done business supported exporting CSV or OVX files of transactions so you don’t need a third party connection into your bank account, although that is an option. It depends on region, but banks are only required to retain data for certain periods of time, and keeping a history of each transaction can be useful for budgeting or investing.


  • Regarding Mint, If I’m remembering correctly, it seemed like they were doing a redesign of the site and then decided to shut it down. I’d have to imagine after they got purchased, all the original devs left and maintaining each connection with each bank was a huge hassle. They probably spent so much modernizing the site and still had to maintain connections, that the operational costs outweighed the income from advertising.


  • If you’re dealing all in cash this makes sense, but for those with multiple bank accounts, keeping track of everything without software is burdensome. I can’t imagine copy/pasting each transaction from my banks website into a spreadsheet. Computers are better at math than humans, they should be doing the calculations, not me.


  • Thirding Actual, I will admit I was using Mint for way longer than I should have for convenience, and moved to Actual after Mint shut down. If you only have a few accounts, it’s not that terrible to download transactions as QFX files and import them once a month when paying the bills. I haven’t tried SimpleFin or anything automated, but that would get you even closer to the experience of Mint.


  • I think this is what OPs message is. There’s no silver bullet that solves everything and change will be gradual. Making any incremental improvements to our fuel consumption which has a net positive effect to reduce climate change is a good thing.

    Gen IV reactor designs are incapable of going into thermal runaway, but Chernobyl and Fukashima weren’t, which is how they became a cautionary tale and resulted in better designs. It’s like basing your fear of flying on airplane disasters from the 1950’s, and instead driving, which is even more dangerous. Just like unsafe airplanes from long ago, upgrading to safer designs is needed. In order to do so, new reactors need to be built to handle the load, but get blocked because of the fear of another Chernobyl, which just leaves older reactors around that are actually a concern.







  • His quote from the article:

    “[…] I need to come to terms with the fact that the level of dopamine I’ve been getting from interacting with LLMs…with doing more and more and more and more…is not healthy for me or good for the world. It is careless, and has disconnected me from where people are on this.

    I was talking about this with [my wife] Katherine last night and she did not pull any punches. Frankly, neither did [my brother] John. Neither of them think I’ve been being healthy. I need to readjust.”

    Not really knowing the drama before today, it seems like he is being very rational and speaking honestly about the effects LLMs are having on his behavior and that he identified he needs to change, which is what the whole article is about.




  • Well if the requirements.txt is pinned to a specific version of a dependency of a dependency, you might not know or really care why that’s set. But then this becomes a nightmare and dependency hell laterif you want a newer version of some package, and that newer version requires a bunch of newer packages and loses the others. At that point you probably will toss your old file and start a new one from scratch piecing together all the requirements with like pip freeze in a new virtual environment.

    Sure you could omit the versions, but then everytime you deploy, you don’t know what you’re going to get and a deployment today would be very different next week with a whole bunch of different versions of dependencies.


  • Yes exactly, like if I know my app needs the requests library, I will just put that in requirements.in but after compile requirements.txt will include the exact version of requests and every version of each dependency. So that every time pip install is run, all dependencies are always the same despite what happens upstream


  • Curious what others have to say, but my go to is to have a requirements.in with direct packages I need for the project, and then run pip-compile to generate all the dependencies with their exact version at the time so that deployments are repeatable. This works well for deployment, but if I were writing a library for others to use, I think you put the direct dependencies in setup.py