In order to create a simple client-server application, do i have to master 'Data Structures'?

Question

Honestly, i discovered that i learn by doing more than hearing and watching. Lets say i have learned all different kinds of Data Structures such as Linked List, Trees, etc. When it comes to implementation (programming) i feel the need to revise what i have learned. Therefore, i decided to learn as i go, e.g. while i write codes, i face things that i have to learn so i can implement it in my program, such as recursion that way i find myself learning more than just hearing and watching lots of concepts and then go to program. I hope you get my point. Are all programmers learn like that?

Anyhow, my question is

In order to create a simple client-server application, do i have to master 'Data Structures'?

Answer 1

Most programmers learn a particular language or theory by reading about part of it or attending a class covering that subject and then programming something that deals with it. This is why programming books often give exercises at the end of each section and teachers, in classes, frequently assign small projects when you are starting new concepts and material. This way, you get practical experience in the subject and it also reinforces what you learn before moving on to more new material.

In a simple-client server application, it would be a very good idea to know some of the basic data structures such as queues and linked lists. However, some of the more complex structures are not as necessary. However, how important these are also depends on the language you are using and the protocol you are using. For example, TCP/IP protocols have the client confirm that data has been received from the server. This allows the client to automatically make sure it gets all of the information it needs and has the information in order. UPD/IP protocols on the other hand do not do this. This means the client may not get all of the info (if a packet gets lost on the internet) or the information may not arrive in the same order it was sent and the programmer must manipulate the data and make sure the data is in the correct order and nothing is missing before attempting to process data. To do this, you often use things such as queues or linked lists to create buffers so you can sort your data before you use it. These are data structures. Also, different languages have different network libraries readily available and may or may not have things built into the libraries to handle the manipulation of received data.

So you should have at least a basic understanding of different data structures before you start doing network programming.