Also if you have clean OOP methods, then collapse your code.
If you forget how you script works, then you might just right click, collapse all, and remember what most of it does by just looking at the methods. It’s a lot easier than scrolling through every line.
1 Like
Maybe don’t drown in bloatware, and problem solved?
Your code has malware named “maid” by the way
This malware decreases your performance and makes development a hellish experience.
The best solution is usually the easiest one; if you have to reach for some module, you’ve already lost as a developer.
Focus on performance when possible; this habit of focusing on performance makes you write lightweight code without ceremony very fast.
If your project has bloat FactoryManagerEnterpriceEditionSignal then your project is already doomed.
1 Like
“Forgetting code the next day”
I call this scope. It’s what you can get done fully without losing your way.
It doesn’t come naturally; it develops over time. The more you program, the larger your scope becomes. Along the way, you’ll learn to mark important areas and use rems to explain things to yourself. Eventually, you won’t even need that. You’ll be able to program without an editor in your head. It starts to become second nature. Rems are still useful for looking at something you wrote years ago… 
You’ll know when to use them too. It just takes time.
For very large projects, mapping out what you’re going to do is very useful. Break out the whiteboard and corkboard. Step it out and pseudocode. Then you’re ready to really go. You’ll get better and develop variations of this too, like flowcharts.
3 Likes
This is good, I think what you said about scope is true. To add onto what you said, devs should try to write the simpler code. A lot of the time I’ll see scripters writing code for something, and they don’t even realize there’s a much simpler way to write that.
Focusing on writing your scripts the simplest possible way will make it easier to expand your scope further.
2 Likes
Learn how to do this and you’ll never walk away from it. It actually becomes the code the more detail you add, over time. This is a short doc on it, Pseudocode 101. You can find all kinds of information online about how this is done. I love to program short scripts like a puzzle because it keeps me sharp, which is why I’m here. I like to do every tutorial I run across. I always find something new.
3 Likes
This doesn’t help the problem of the code being overwhelming and why would you even need a script for this when you can just say “TODO” in your code?
2 Likes
Split your code into modules so it’s easier to see what’s going on and add frequent comments. I also recommend sketching flowcharts for complex systems so you can go back and see your code in branches. I recommend draw.io for flowcharts.
4 Likes
Overwhelming is unavoidable. Every programmer deals with that. This is totally expected and normal. That is where the scope thing comes into play and where getting better at research helps.
2 Likes
Sorry, I meant help, not solve. You’ll never remove overwhelm completely, but you can make it small enough that it doesn’t stop ypu.
1 Like
Are you implying all libraries and frameworks are bad? Anyhow, it’s not that I don’t know how or when to use libraries, my issue is a matter of codebase structure and mentally tracking progress.
Not all libraries are bad per se; if they don’t do exactly what they’re meant to do and instead drown you in abstractions or attempt to make very specific things “universal” then it is a definition of bad.
Before you even began writing the code, you already hoarded these libraries like they are Minecraft mods. Programming is not a modpack; use only what is necessary.
You could try making your code more modular. Have a main script that calls in modules to perform functions as needed.
I am sure a coding purist would disagree with me but once I get past 500 lines even with notes it can get hard to follow it all.
This is better than the one I use.. Thanks, instant switch.
1 Like
I chuckled at this line xd u funny bro
I will always disagree with people saying to improve performance, when the question is, how to improve readability…
I bother with performance mainly when I measure that I should (with the micro profiler), and I improve performance where it will actually make a difference
1 Like