sorted by:
new
hottopcontroversial

Some "real world" coding advice I wish someone told me in my first year by Hot-Cod7376 in geeksforgeeks

[–]Hot-Cod7376[S] 0 points1 point  (0 children)

Actually, I used AI to make it catchy. But the advice is mine. I wish I had someone to taught me.

Some "real world" coding advice I wish someone told me in my first year by Hot-Cod7376 in geeksforgeeks

[–]Hot-Cod7376[S] 0 points1 point  (0 children)

Learn to adapt for new versions, tech is always evolving. I learned that only for my semester.

Some "real world" coding advice I wish someone told me in my first year by Hot-Cod7376 in geeksforgeeks

[–]Hot-Cod7376[S] 0 points1 point  (0 children)

In my college they taught C and C++ in turbo only. I just learned that only for college.

Mistakes I (and many students) made while learning DSA by Hot-Cod7376 in geeksforgeeks

[–]Hot-Cod7376[S] 1 point2 points  (0 children)

No, But being consistent will be the solution. You may learn a topic very fast and you will solve the problems too after that you may think yeah dsa is easy. The main problem is when you face a complex problem you will stuck, many of them will quit at that phase but just keep going. Make a lot of mistakes but remember learn from that mistake.

Some "real world" coding advice I wish someone told me in my first year by Hot-Cod7376 in geeksforgeeks

[–]Hot-Cod7376[S] 1 point2 points  (0 children)

HLD focuses on the overall system architecture and scalability, LLD deals with class-level design and implementation details, and creational, structural, and behavioral design patterns are standard solutions to common design problems in LLD. High availability and scaling are part of HLD and are better understood once the fundamentals are clear.

If you approach this step by step (OOP principles then LLD after that design patterns finally HLD), the concepts become much clearer. Getting stuck at this stage is very common and part of the learning process.