I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
What language or even learning path do you recommend for my situation?
A rather standard feedback loop like the following is what I'd recommend:
Try to do something.
Make mistakes while trying to do it (not intentionally, just because you happen to make the mistakes).
Learn from your mistakes.
Repeat from step 1.
Iterative learning of this type of thing really is the best way in most cases. Exact choice of language doesn't matter as much as how you approach it (though I would recommend C (not C++, not C#, just plain C) for the learning part, as it kind of forces you to do most of the work yourself).
Is there anyone who experienced the same?
Most people. The number of people for whom this type of stuff is intuitive is pretty small, especially since you can't tangibly interact with a lot of the concepts involved.
Are there any topics every programmer should know?
Yes, but it really depends on what, specifically, you're doing which topics you 'should' know.
The two big ones (at least IMO) that are useful for almost every programmer are basic set theory and basic graph theory. Both provide the underpinnings for a number of very widely used data structures, as well as being helpful to understand a number of other programming concepts and talk about certain types of algorithms. Graph theory is especially useful when dealing with tree structures, which are very common in a wide variety of programming environments.
Student from Germany who fell in love with coding and the tech industry after pivoting from a traditional career in banking. Currently pursuing a Bachelor's in CompSci.
I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
Unfortunately, not really. I've been looking for a while now for some good primers on basic set theory and graph theory to point people at who are just starting out, but have yet to find any that don't assume a pretty heavy background in advanced mathematics (which kind of defeats the purpose of pointing people straight at set theory and graph theory) or cover a much broader range of sub-topics than most programmers will ever need.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A rather standard feedback loop like the following is what I'd recommend:
Iterative learning of this type of thing really is the best way in most cases. Exact choice of language doesn't matter as much as how you approach it (though I would recommend C (not C++, not C#, just plain C) for the learning part, as it kind of forces you to do most of the work yourself).
Most people. The number of people for whom this type of stuff is intuitive is pretty small, especially since you can't tangibly interact with a lot of the concepts involved.
Yes, but it really depends on what, specifically, you're doing which topics you 'should' know.
The two big ones (at least IMO) that are useful for almost every programmer are basic set theory and basic graph theory. Both provide the underpinnings for a number of very widely used data structures, as well as being helpful to understand a number of other programming concepts and talk about certain types of algorithms. Graph theory is especially useful when dealing with tree structures, which are very common in a wide variety of programming environments.
Alright, thanks for that huge advice! Do you have any recommendations for resources like books, courses etc.?
Unfortunately, not really. I've been looking for a while now for some good primers on basic set theory and graph theory to point people at who are just starting out, but have yet to find any that don't assume a pretty heavy background in advanced mathematics (which kind of defeats the purpose of pointing people straight at set theory and graph theory) or cover a much broader range of sub-topics than most programmers will ever need.