Was it types, promises, or ternary operators?
Maybe async, testing, recursion?
Was it OOP, malloc, or decorators?
Or maybe compilers, data structures, or recursion?
For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (54)
python has been my main programming language and it has been little tough
Dynamic programming, hands down.
Ah yes. Pointers, relatively easy to understand and use, and extremely easy to screw up and thereby sending you into an abyss where you don't understand any of it.
Not to understand, but to get it right.
To this day I cannot understand how recursion works. I used to find OOP concepts confusing but now I'm used to it.
The Objected Oriented Programming, back at when i started learning Programming, the first thing that set me off was setters and getters, I was like why build setters and getters if one can initialize it in Constructors and can access it through the class. That was the most difficult, But still now the OOP methods and properties confuses me a little time by time.
I took me some time to take the time to understand covariant types
The concepts themselves have never been a problem, it's been the "best practices" of the concepts that have been a problem. About two decades ago, I tended to suffer from NIH (not invented here). I still seriously overthink decisions like REST vs graphQL vs RPC, which component libraries or frameworks to use, etc., as I'm still highly opinionated, but I at least understand that outsourcing the work to someone for whom the library/framework is their primary mission is more likely to produce a quality product than rolling my own in between or in support of my real tasks.
I was learning Go and struggled a lot with channels and buffered channels, after using promises for everything in JavaScript. I kept getting deadlocks trying to wait for multiple goroutines to all finish!
Hmmm... pointers which made it tough to learn C because of it.