It’s difficult but worth the time if you have it. No other language creates programs with such guarantees for not having common memory bugs and performance like c.
I’ve built little things that already have a solution when that other solution either didn’t do it the way I had in mind or did more things than I needed it to. It really depends on how you’re valuing your time and knowledge/experience in the end.
Then you fill the fucking code with print statements because you don’t know to use debug, realize the variable feeds some stupid fucking function that does nothing but has to be there and a few hours later comment out said print statements and just re add the variable.
You know, it occurs to me that doing that with print really isn’t any different than the accepted method of debug logging other than where the output is directed to.
Most times I find that these projects are either old or badly made (often both). If you’re inspired and you feel like you can make them better, then go for it.
An artist isn’t going to refrain from painting a portrait of a dog if other artists have already painted dog portraits, so why should you?
Yeah don’t let this stop you! If you do the side project for fun and/or learning, just go ahead and build stuff. Don’t look at other projects too soon so you give space to your own creativity. But perhaps compare stuff in a later stage.
This is key. One will inevitably make many different design and UX decisions vs whatever preexisting projects are out there, making one’s project more suited to at least a few contexts than anything preexisting.
In addition to being plain demotivating, looking at other stuff too early basically encourages one to just make the same decisions as others, becoming much more like just a second implementation of what already exists.
Also consider the possibility when the other, more popular projects got enshittified. Now the fleeing users have an option to switch to your project. It actually happened on one of my side project. I made it because I want to try building my own version of X. It got ~2000 users, but later down the road, X got sold to a new shitty owner that waste no time to enshittify it, and my side project suddenly grow to 20,000 users overnight.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
But now you have the opportunity to build it in Rust or Typescript! /s
This but unironically
I really need to learn Rust…
You will get there one day, I believe in you :)
It’s difficult but worth the time if you have it. No other language creates programs with such guarantees for not having common memory bugs and performance like c.
Take off the /s and do it!!
That doesn’t stop the Javascript frameworks.
If it sounded cool to do, I do it anyway, and keep it to myself. Never have to clean that shit up. Unfinished? Who gives a fuck, I did it, job sorted.
If it sounded like it needed to exist… thank god, someone else did it for me! Not my problem. git clone, next idea.
A Minecraft rewrite in Rust with a very specific engine and goals certainly hadn’t been done… right?..
https://github.com/PistonDevelopers/hematite
third panel: end up doing it anyway because it’s fun
4th panel, you did a great job but nobody gives a shit
So? You did it because it’s fun, not because you wanted a pat on the back.
There are some projects that are just for you, and others you hope people will get use out of / enjoy
This is the correct answer
I came up with idea where instead of typing stuff like “5/6” “6*9” into the terminal, you could have gui interface.
Instead, you can try to extend the existing project with new features, possibly improving your code reading skills and discovering new practices
Think of it this way: If there’s loads of implementations of an idea, it means there’ss already a market/need for it!
I’ve built little things that already have a solution when that other solution either didn’t do it the way I had in mind or did more things than I needed it to. It really depends on how you’re valuing your time and knowledge/experience in the end.
Try to add 100+ things to make it very big project, then dropped without even completing 10% of to-do list.
Eventually you get a better idea to start the same project from scratch, then drop it.
Sometimes starting from someone else’s code and stripping only to the functions you need is fun!
That’s how you find that one variable that isn’t used anywhere but breaks everything if you remove it.
Then you fill the fucking code with print statements because you don’t know to use debug, realize the variable feeds some stupid fucking function that does nothing but has to be there and a few hours later comment out said print statements and just re add the variable.
You know, it occurs to me that doing that with print really isn’t any different than the accepted method of debug logging other than where the output is directed to.
Most times I find that these projects are either old or badly made (often both). If you’re inspired and you feel like you can make them better, then go for it.
An artist isn’t going to refrain from painting a portrait of a dog if other artists have already painted dog portraits, so why should you?
Then a while later you go back and look at what you did and realize it’s old and badly made.
Then you pat yourself on the back for inspiring the next dev that comes across your project
Yeah don’t let this stop you! If you do the side project for fun and/or learning, just go ahead and build stuff. Don’t look at other projects too soon so you give space to your own creativity. But perhaps compare stuff in a later stage.
This is a great perspective. I have definitely fallen into this meme’s sentiment many times. You have to remind yourself that it doesn’t matter.
This is key. One will inevitably make many different design and UX decisions vs whatever preexisting projects are out there, making one’s project more suited to at least a few contexts than anything preexisting.
In addition to being plain demotivating, looking at other stuff too early basically encourages one to just make the same decisions as others, becoming much more like just a second implementation of what already exists.
Someday people might look at your project and become demotivated at their own, and the cycle continues
be the change you don’t want to see
If you’re looking for original ideas… I have bad news for you
They come from unique problems
If it brings you joy, you should make the 27th implementation of neofetch in rust.
What? There’s already 26?!
<types rm -fr neofetch-turbo while drying up tears>
I can’t believe I’ve never seen
rm -frinstead ofrm -rf. “remove for real” is instantly my new method of deleting directories.I’ve been doing -fr like forever. Don’t know why
BURN THE HERETIC
Just alphabetical order 😄
rf makes it seem like recurse/force instead of some genz/genalpha shorthand
or you realize that the idea fundamentally wouldnt work. i wanted to build a lemmy music recognition bot until i remembered lemmy has no videos lmao
Who cares if it already exists, just make it.
Also consider the possibility when the other, more popular projects got enshittified. Now the fleeing users have an option to switch to your project. It actually happened on one of my side project. I made it because I want to try building my own version of X. It got ~2000 users, but later down the road, X got sold to a new shitty owner that waste no time to enshittify it, and my side project suddenly grow to 20,000 users overnight.
X? Social media? /j
This makes me want to revive some of my comatose projects.