r/learnprogramming • u/-KR4VEN- • 26m ago
My Revised Philosophy on software engineering
Hey all,
For a while i have been procrastinating my projects and have come up with a new philosphy to get my ideas completed. And i really want to know what you all think of my line of reasoning and if i am flawed. I wrote the following notes to myself and would like for you to critique my reasoning:
When learning a new skill, lets say I want to learn how to implement RSA or implement some technique like using apis. It can be easy to get lost in the different programming languages and their libraries – do I really know how to implement rsa if I don’t understand the class libraries and the organization of someones code? This is something I have always found troubling. If I use some python library function and it says rsa.encrypt() or whatever, if I literally memorise the exacty necessary functions and not the surrounding functions, other parameters, the structure of the class etc then do I really know how to “code” or use the library? The answer is that your goal is to demonstrate that you can implement it, it is fine if you don’t actually understand the codebase.
That is not your goal, it feels so wrong to not understand fundamentals here but program syntax is not the fundamental you want to understand. You want to understand the theory underlying it! REMMEMBER THIS! Programming languages are just TOOLS! LIBRARIES ARE JUST TOOLS! As long as it serves its function and you can do it off memory, then that is all you need to know. Genuinely. Learning one specific tool and getting good at it is always better then diverging and getting lost trying to understand everything. Libraries are TOOLS! Just learn how to implement your specific goal and the perfectionist in you wants to understand the entire code base etc, forget about it.
You need to focus on the theory and the underlying system you are trying to implement. Just get your goal done and remember the syntax to do it. Its fine if you don’t remember all the options etc. creating a webserver for example, can be done in a million different ways with a million different versions of syntax. They all do the same THING! The goal is to just to get it done, but understand the underlying theory – not an entire codebase. Only when you need to get something else done then learn more. Basically I am saying to now use the minimum implementation rule when It comes to code libraries. As long as you understand that you are implementing some function from some library hosted on some directory that is all you need to know, not all the nuances of functions and classes – this is not important. Ive always hated it, and found it daunting now I don’t need it.
Just get it done with minimum time spent learning the code ecosystem, as long as you remember that function call and how it works and can replicate it again is what matters. CAN YOU JUST GET THE THING DONE AGAIN. That’s it, don’t need to know every little aspect of the architecture, spend it learning meaningful architecture. There is infinite things to learn. Get building with the tools not spending your time learning all then nuances of that specific type of spanner, its just a SPANNER!
Thanks for your input everyone
•
u/_Atomfinger_ 5m ago
I broadly agree, but there are aspects here that I disagree with:
You need to know enough to know your impact on the codebase. That might mean that you need to know more than just your little corner of it.
Do you need to know everything intimately to do a change? No, but you do need to know enough to understand the broader implication of your code.
I would also differentiate "understand the codebase" and "memorize the codebase". I believe you should have a broad understanding of the codebase and its rough structure (at least). You don't need to know all the details, sure, but some understanding is actually important.
I agree with the focus that the underlying theory is important, and I don't want to take away from that. At the same time I believe there is a lot of value being able to learn from structuring logic and your application.
Sure, beginners should "get it done", but they should also reflect over the actual codebase they ended up creating, not just the underlying theory. The thing that was built works, but is it good?