genderweird data witch in London
Admin @ Queer.Cloud
Queer as foretold, actually autistic.
NSFW account (@EdenLewd)
| Pronouns | They,Them |
genderweird data witch in London
Admin @ Queer.Cloud
Queer as foretold, actually autistic.
NSFW account (@EdenLewd)
| Pronouns | They,Them |
@WizardSasquatch It's mostly because I know how to use a model, and when to use specific models, and how to prepare data for them.
But often I don't really get *how* they work, and I want to work at being able to write my own to understand them.
I can setup pipelines myself with docker and Python, but writing a custom algorithm is the part that I think is really interesting.
I've been working on writing CART-equivalents in Rust, and that seems like a good step for now?
@WizardSasquatch SQL pipelines -> R for marketing tools, ad hoc R projects for business analytics, occasional C++ for clustering when it called for it. Lot of dashboards early on, now I don't do as many dashboards.
Fair amount of working with different models and writing code around validation.
What other portion are you thinking about?
I really don't feel like I enjoy the analysis side of data science anymore.
It's cool to learn new things about data, but at the end I have a notebook and a few new tools. And that just doesn't feel like enough anymore.
I think I want to do some kind of data/ops, build some tools, work with algorithms.
So unfortunately I don't really have the time to maintain a mastodon anymore.
I still want to use mastodon, I love talking about rust on here.
But I don't think I can manage _this_ server.
So I'm going to close it down in 3 weeks-ish - 19th December, and move to a new address by then. It's been fun learning this stuff, but I know it's possibly insecure because I just don't have the time to keep updating it.
@trwnh But Rust hates this too.
It doesn't know how many columns are going to be allocated like this, it certainly doesn't know what types to give them, and it doesn't know when they'll go away.
The big thing for Rust is memory safety, so if you allocate something, the compiler has to work out when it'll be de-allocated.
The compiler right now can't work out how many thing will be allocated, so it can't work out the opposite either. So it's not passable in Rust at all