Probably the best article about computer science learning

[terrycody]

hey guys

I searched around and happen to found this article "how to learn computer science, from zero to hero"

I personally think this is the best article I read about programming, even though I don't know how to code, but always eager to learn.

I recommend every programming beginner read this (want to learn CS thoroughly) :

https://www.afternerd.com/blog/learn-computer-science


(apparently, not my site, or I will... u know)

 

[Death Itself]

loved it, thanks!

 

[hitit]

a lot of good info in there, thanks

 

[mariopepper]

Information i found out there is great as for me so i would like to get more usefull like this article

 

[Xalamon]

This article sucks. Honestly. It puts too much emphasis on learning data structures and algorithms when the trend is for programming languages to make this decisions for you. In C# you can use the Entities Framework to optimize database operations and I know Java has a similar framework called JDO. You might benefit from learning what algorithms are, but in reality you won't use any of those skills when you can just use a framework. Focus on solving problems.

 

[NulledCode]

This article sucks. Honestly. It puts too much emphasis on learning data structures and algorithms when the trend is for programming languages to make this decisions for you. In C# you can use the Entities Framework to optimize database operations and I know Java has a similar framework called JDO. You might benefit from learning what algorithms are, but in reality you won't use any of those skills when you can just use a framework. Focus on solving problems.

The thing is, the frameworks you speak of are developed by engineers who know about the algorithms and data structures to develop something higher level so “coders” and “programmers” can use it. There will always be a need for computer science engineers because they are the ones building the tools that make developing easier. So, if you want to be a developer then sure, don’t learn how to optimize a database for high performing queries or worry about improving algorithms. I like what the article had to say and agree with the stages they outlined. I think too many people fall in the coder and programmer categories but think they are in the next level. Anyone can learn coding but engineering is where the money and value is.

 

[PixelMathis]

This article sucks. Honestly. It puts too much emphasis on learning data structures and algorithms when the trend is for programming languages to make this decisions for you. In C# you can use the Entities Framework to optimize database operations and I know Java has a similar framework called JDO. You might benefit from learning what algorithms are, but in reality you won't use any of those skills when you can just use a framework. Focus on solving problems.

Data Structures and Algorithms are the basis of Computer Science. There's a reason why they are taught to all CS students around the world.

 

[IKXS Acquiring]

Yes, data structures and algorithms are important.

And almost any important data structure or algorithm has a library default you can use (Boost, stdlib, etc)

Yes, You should learn your basic DS's and Algorithms.

At the end of the day, you'll only climb by grind. You gotta work this stuff daily, with small and large challenges.

CS grads churn out dime a dozen, with their hats full of Java, Python and Javascript.
Their ace up the sleeve, a small course on Data Structures or ML.

However, the programmer, the coder, the CS who can build actual solutions to problems, is king.

I'd first identify a direction or branch that you really want to get into:
- perhaps its robotics, like making a RC program
- or its IOT
- or is game development
- or web services
- or bot dev
- or ...

Then, start working on problems small and large.

I mean, seriously, making a light blink on a small development board (think ESP32 or RPI) can be a great feeling that first couple times.

Remember to keep it fun, that will keep you motivated. I'm not saying avoid hard problems, but there is such a thing as biting off more than you can chew.

Good luck!

 

[Xalamon]

The thing is, the frameworks you speak of are developed by engineers who know about the algorithms and data structures to develop something higher level so “coders” and “programmers” can use it. There will always be a need for computer science engineers because they are the ones building the tools that make developing easier. So, if you want to be a developer then sure, don’t learn how to optimize a database for high performing queries or worry about improving algorithms. I like what the article had to say and agree with the stages they outlined. I think too many people fall in the coder and programmer categories but think they are in the next level. Anyone can learn coding but engineering is where the money and value is.

From my point of view there is a much bigger need for developers than computer scientists. In my experience, computer scientists lose their natural connection to the market by focusing on high-level algorithms, while neglecting the needs of clients and general users. The result is a market saturated with reverse-engineered apps and games made by computer-scientists that are more used to optimize than to create.

Data Structures and Algorithms are the basis of Computer Science. There's a reason why they are taught to all CS students around the world.

Data Structures and Algorithms only help you optimize solutions, not create new business ideas. Computer Scientists get really good at optimizing speed and creating algorithms to solve complex problems like computer vision, and mimicking nature in general, but in that hyper-specialization, they lose contact with simple solutions to day-to-day problems the market is currently experiencing.

I may want to hire a computer scientist to optimize on my developments, I wouldn't like to become one.

 

[TheVigilante]

Will give it a read if you say it's the best you have come across

 

[Jack Merlin]

Thanks for the share

 

[rafark]

This article sucks. Honestly. It puts too much emphasis on learning data structures and algorithms when the trend is for programming languages to make this decisions for you. In C# you can use the Entities Framework to optimize database operations and I know Java has a similar framework called JDO. You might benefit from learning what algorithms are, but in reality you won't use any of those skills when you can just use a framework. Focus on solving problems.

If you need to make small, quick software then yeah, frameworks are the way to go (dirty and fast but help you get the job done). For the long term, however you will need to dive deeper into algorithms, architectural concepts, etc

 

[PixelMathis]

Data Structures and Algorithms only help you optimize solutions, not create new business ideas. Computer Scientists get really good at optimizing speed and creating algorithms to solve complex problems like computer vision, and mimicking nature in general, but in that hyper-specialization, they lose contact with simple solutions to day-to-day problems the market is currently experiencing.

I may want to hire a computer scientist to optimize on my developments, I wouldn't like to become one.

This article is about computer science, not business development so my point still stands.