What’s a concept you understand now, but took you forever to grasp?

I’m sure we all have plenty of answers to this one, but sometimes we forget how far we’ve come.

Comments

[squ94wk]

git

Sadly there was hardly anyone around that was able to teach me what actually happens.
Now I try to be that person to others.

[cvanpoelje]

How to work on the right part at the right time,
Problems usually lead to new questions who lead to problems that need solved.
It took me so long to realize that I can cut one problem into 100 small problems.
Which in turn would make solving the major problem a lot easier.
Also, whatever distracts you, needs to be done another time.

[Mark Tse]

That a REST API call is just a glorified HTTP call.

[Chris Weir]

Data Structures. My lecturer at University wasn't the best and explained them very poorly. I always figured I'd never understand them. Then I watched CS50 and it 'clicked'.

[Ola' John Ajiboye]

I think it has to be props in React. I didn't get until someone said it just like argument to a function the name doesn't really matter. And also testing, It just didn't make any sense at first.

[Leigh Scherrer]

1. Recursive algorithms!
2. Promises
3. Callbacks

[Hadi Golkarian]

Javascript single threaded event loop and event propagation.

[sonofhammer]

ForEach loops. Took me two weeks of sticky notes, diagrams, and code to finally get it.

[The Well Spoken Dev]

..... And no one's said it yet. SQL joins => EF6 😫😫😭

I write hundreds of these regularly and still go cross eyed when I have to reverse outer joins with DefaultIfEmpty....

[corey rodgers]

Working out how node uses modules, how to require them in web pages an the browser ,using browserify to use modules on a client browser, for some reason this took me a long while to work out but something just clicked