I use spreadsheets - download csv from your bank, import, label categories, then you can look at it any way you like. Doesn't take that much time, and with a few heuristics, the tagging can be mostly automated...
1,783 karma · joined April 5, 2011
I use spreadsheets - download csv from your bank, import, label categories, then you can look at it any way you like. Doesn't take that much time, and with a few heuristics, the tagging can be mostly automated...
The thing that's interesting to me is the idea that these things have to continue to "evolve." Like we need to keep adding features to keep people engaged to have an active community, yada yada.
In my mind, and maybe I'm wrong, some of these projects are just sorta finished - they've evolved to a completed state more or less and just need maintenance. Memcached has sorta went this route afaict - it's still tremendously useful for some things and it's not constantly trying to add data types to compete with other things.
As of last week there were something around 1024 people who had all 450 stars.
Only started on like day 6 of 2022, but became hooked and had some time early in 2023 to go through the previous years. Once you have a few algorithms canned, it's not too difficult and some themes repeat across years.
It's fun to brush up on stuff you don't touch all the time - actual algorithms and stuff.
Hats off to the volunteers and Eric - I aim to donate every year now - it's a great event.
But yeah, it was only a couple more years until amd64 came around and really made a difference.
Torch, nvidia, and triton site pkgs are quite a bit bigger on Ubuntu since I guess nvidia gpus aren't available on mac.
I've been supporting pytorch + cuda just using 'python3 -m venv foo' and pip (+ pip-compile) for the last year and it works - not super fast, but I prefer using the python.org blessed tooling.
I worked in a group that did physical design, timing closure, test insertion, etc. I did a lot of layout automation in Avanti's tools; sometime after I left, it all went to Cadence I believe.
You'll notice the numbers on these L1Axxxx - this is an internal LSI number, after they ran out of numbers for the xxxx part they bumped it to L2Axxxx and I worked on a few chips with those designations.
We had the same issues where I ended up working; it was a year or two before 32-bit intel systems started to show up and they absolutely screamed compared to Sparc, but couldn't handle really big jobs. When the amd64 stuff started to come around, that's when you could just see the writing on the wall - Intel / AMD were gonna absolutely kill Sun...
Also, may just be me, but I've mostly seen just bad Django apps - God object patterns galore, the schema/orm/business logic all being very tightly coupled and essentially nothing is able to be refactored because of this. They often have to be simply thrown away and you start over.
But, I think having an explicit service interface solves a lot of these problems - as long as you maintain the interface and pass back the same type of object, you're free to talk to whatever backing store you like. And you get a lot less issues with circular imports and whatnot in my experience. ymmv
Running and configuring VMs isn't hard to do correctly, it just takes discipline to never "hack it in the moment" - or if you do, can that change in your config system.
The additional benefit is devs can run all the same stuff on a Linux laptop (or Linux VM on some other platform) - and everyone can have their own VM in the cloud if they like to demo or test stuff using all the same setup. Bootstrapping a new system is checking in their ssh key and running a shell script.
Easy to debug, not complex or expensive, and we could vertically scale it all quite a ways before needing to scale horizontally. It's not for everyone, but seed stage and earlier - totally appropriate imo.
I just have a small shell script which symlinks everything into my home dir - also serves as a reference as to what actually gets put where.
I've been putting an http endpoint in my sites that checks all the backing stores and returns a 204 on everything ok, and a 200 + error message on something broken. This is a remarkably simple and effective way to do entire site monitoring given the called endpoint can check server stats, task queue depth, backing store health, anything really.
And I'd say, if whoever you hire can get the database schema nailed down more or less correctly in the first iteration or two - you'll be good. It all hinges on finding someone who's done this sorta thing before, won't over complicate it, and can wring out the first level of mistakes before implementing an entire software system around it. Knowing the business in and out would definitely help here.
All depends on how you work and what you're doing really.