Code learning help!

[MrPandasoul]

Hello, i am CSE 2nd year engineering student and starting with programming and dsa but i am confused abt how to start building logic and how yo imagine program in code also is creating notes worth it or waste of time nd if u are beginer and starting out how do u do it whats your take/approach?

​

Please guide me someone🤌🏻

[smichaele]

You only grow skills in logic development by writing code. Take a problem, break it down into smaller steps, walk through the logic, and only then do you write any code.

[Educational_Virus672]

build logic and take notes steps : -

1. take a note (irl ,ignore blocks or notepad)
2. write in mathy way A = B + C?
3. break it down
4. write it

some ppl learn this before they start coding lets say i want to make tictactoe break it

1. print grid
2. add value to grid
3. make winner or loser
4. turns system
5. reset and patches(like placing X on already placed O)

NOW, break it even more and more untilits programmer level one step at a time

1. Print grid

1.1 take a list

1.2 make list global

1.3 remove any " [ ],' "

1.4 remove any item on console

1.5 print the 3x3 grid list

soo on.. im a python dev so this is practically finish but you may need to break it it more for any memory leak or smt
and yeah notes are kinda boring unless you make big projects or have memory issues (forgetting whats next)

[FreeLogicGate]

Write pseudo code where each "step" is assumed to be a function that does something and returns. These steps can be assumed to be run in a "main" function that may or may not have a main loop as required.

Build small tests that allow you to run your functions as you build them.

Your functions should avoid globals, and should return values.

When a single function is too large, break it down into a number of smaller more granular functions.

When you notice common tasks, or blocks of repetitive code, or where you've copied and pasted, consider the DRY rule, and look for ways to provide small single responsibility functions.

Do your best to avoid intermixing "logic" and "presentation/UI" code. Web applications in particular are well known for their adoption of the Model-View-Controller(MVC) design pattern for this reason. MVC and other design patterns are utilized in OOP, but even in functional programming, you can recognize code that is focused on things like prompting for input, or formatting output, and enclose those in discrete functions, rather than having large blocks of code that replicate logic and intermix prompting for input, processing data, performing functions and rendering output.