#DSA as itself or DSA in Java

1 messages · Page 1 of 1 (latest)

lusty coral
#

Feeling like I need to hop into the concepts and practices of DSA after learning basics of Java OOP. I'm seeking an advice whether learning DSA as itself first would be ideal than learning DSA in Java, or is it the other way around?

vale axleBOT
#

<@&987246717831381062> please have a look, thanks.

#

Here is an AI assisted attempt to answer your question 🤖. Maybe it helps! In any case, a human is on the way 👍. To continue talking to the AI, you can use </chatgpt:1108714622413963314>.

#
TJ-Bot
Feeling like I need to hop into the concepts and practices of DSA after learning basics of Java OOP. I'm seeking an advice whether learning DSA as itself first would be ideal than learning DSA in Java, or is it the other way around?

I would recommend learning DSA as itself first before diving into DSA in Java. Understanding the concepts and principles of data structures and algorithms will provide a solid foundation that can be applied across different programming languages. Once you have a good grasp of DSA, you can then focus on implementing them in Java or any other language.

Useful links:

  1. GeeksforGeeks - Data Structures
  2. HackerRank - Algorithms
  3. TopCoder - Data Science Tutorials
- AI generated response
lusty coral
#

I have a hunch that learning dsa as itself first would be more ideal conceptually but i wonder how will i be able to practice those concept while learning if theres no programming language involve

lavish seal
#

What does DSA stand for in your question?

#

Data structures and algorithms?

#

I think that learning data structures and algorithms is paramount for a tech person

#

I think it is ok to be learning both things pseudo parallelly or completely parallelly

#

Nothing helped me better than NeetCode and LeetCode. It's painful and time-consuming but rewarding. I tried 3 years of university learning that stuff, but my lecturers were under-educated and were teaching me wrong material that contradicts reality. Those university folks (most of them) are flying in the cloud cuckoo land. It's ok by the way, it's just how they operate fundamentally. It's their natural limit. It's like banana cannot think.

NeetCode and LeetCode practicing while keeping the brain on and thinking about tradeoffs, trying different solutions, comparing them in different dimensions (maintainability, raw speed, Big O notation, readability, adaptability, redundancy, modularity, separation of concerns, etc) using different programming languages, using different styles of programming (DOP, brainrot outdated oop impl inheritance, FP, their combination, etc.) and completing tasks at your job is what brings and aligns one to reality

wise furnace
# lusty coral Feeling like I need to hop into the concepts and practices of DSA after learning...

DSA is usually taught using pseudocode or a programming language - where the language itself doesn't matter too much.

So DSA you learn should be applicable in Java or any other language - and should be fairly trivial. You could also use python, but java is nice.

The main prerequisites is that you ought to be okay with basic / elementary programming - in Java or another language.

In univerisites they use these often
This for an introduction to java

  • introduction to java programming and data structures 12th edition
    And then DSA is taught with this book and others
  • Introduction to Algorithms, 4th edition