Hi PrivateNoob, I still remember running into you a lot in my early days :D
I’m currently using pretty much what’s on the repo.
Working on an update though, which will enable me to use a single command to make the tool look at which of my communities needs more activity, then go out and find a potentially suitable image from danbooru or pixiv to post.
Also working on the ability to give it just a danbooru/pixiv artist id, and then go through and queue upp all their work, instead of copy pasting a link to each one I wanna share. And to also then remember the artist and periodically check if they’ve posted more art.
The goal is to make queueing up posts, sharing my favorite artists, finding and curating new ones, as easy as swiping through some tinder profiles every day.
Yoo Mental! Yeah I still remember you from the NFS community especially! :D
You’re impressive ngl, but hopefully, you will be able to break up your main file because it can become unmanageable really fast if you start to expand it. But that’s just me.
But holding the code in my head gets so much harder when I do that. There’s something about the way I think about code that makes it easier for me to do monolithically. Just keeping the whole thing in my mind as a long, from the top downwards list.
There shouldn’t be a difference, it’s not like the code is any different. But for the same reason I tend to stick to what comes easy.
I might make the analogy that one long file is like a 2d projection of a 3d space for me. I can picture the process moving through the code easier, and as soon I split things into multiple files, it’s like my single-dimensional thinking has to become multi-dimensional.
Well everyone works a little bit different, so it’s wise to formulate the code to your own likeness. For example I really like separating everything into their own task if possible, since I can get overwhelmed by scrolling through thousands of lines.
Hi PrivateNoob, I still remember running into you a lot in my early days :D
I’m currently using pretty much what’s on the repo.
Working on an update though, which will enable me to use a single command to make the tool look at which of my communities needs more activity, then go out and find a potentially suitable image from danbooru or pixiv to post.
Also working on the ability to give it just a danbooru/pixiv artist id, and then go through and queue upp all their work, instead of copy pasting a link to each one I wanna share. And to also then remember the artist and periodically check if they’ve posted more art.
The goal is to make queueing up posts, sharing my favorite artists, finding and curating new ones, as easy as swiping through some tinder profiles every day.
Yoo Mental! Yeah I still remember you from the NFS community especially! :D
You’re impressive ngl, but hopefully, you will be able to break up your main file because it can become unmanageable really fast if you start to expand it. But that’s just me.
Haha… I know that’d be best practice.
But holding the code in my head gets so much harder when I do that. There’s something about the way I think about code that makes it easier for me to do monolithically. Just keeping the whole thing in my mind as a long, from the top downwards list.
There shouldn’t be a difference, it’s not like the code is any different. But for the same reason I tend to stick to what comes easy.
I might make the analogy that one long file is like a 2d projection of a 3d space for me. I can picture the process moving through the code easier, and as soon I split things into multiple files, it’s like my single-dimensional thinking has to become multi-dimensional.
Well everyone works a little bit different, so it’s wise to formulate the code to your own likeness. For example I really like separating everything into their own task if possible, since I can get overwhelmed by scrolling through thousands of lines.