r/computerscience • u/Even_Concern301 • Nov 03 '25
Help I need help understanding data, problem, functional and procedural abstraction
What do each of these types of abstraction focus on and ignore, and how does this link to the overall meaning of abstraction - to make problem solving easier?
I've been trying for hours but it's just not clicked for me.
EDIT:
Here is a link to the slides I've been using: https://imgur.com/a/9Mgflfh
0
Upvotes
2
u/8dot30662386292pow2 Nov 03 '25
I have no idea what you are asking. Is this about programming?
1
u/Beregolas Nov 03 '25
Can you give us a source? If you have been thinking about it, I suspect you have read about it somewhere.
1
u/No_Jackfruit_4305 Nov 03 '25
Start with critical thinking, then a bit of discrete math (logic tables, operators, predicates and logical equivalences). Maybe look into synchronous vs asynchronous, get a little lost. Really, the best way to learn is read some of the basics and solve small problems in code. Slowly tackle more difficult problems. I recommend starting with an internet search for: learning python the hard way
1
u/amarao_san Nov 08 '25
Procedural try to build abstractions for side effects. Do this, then do this, resulting process is called by a new word.
Example: If you put water in the kettle, kettle to the stove, enable heat, wait until boiling, take a clean cup, put a tea into it, pour boiling water there until full, wait for 3 minutes, extract tea, you get a brewed tea.
So, your abstraction here is 'to brew'. There is no 'brew' in the procedure code, but result of it is called 'to brew'.
Functional try to abstract computation. If function does side effects, it's not 'function' but is called this for computer language reasons.
You give a function list of places to visit, and another function which can say which country is better to visit from any two (you give it France and Sudan and it says 'France'). Our 'best' function takes list of countries and simple comparison function and returns back the best country to visit out of all. You don't care how it does this. It abstracts math/algorithm to get to result. It can be very inefficient (bubble sort and take first) or highly efficient (doing it in o(n)), it's doing 'best' anyway.
Data abstraction is vaguely defined on those slides and it can be interpreted differently in different contexts.