Experienced Microsoft 365 pro and Microsoft MVP. Skilled in pre-sales, team management, and global projects. Passionate about innovative solutions. Newsletter author.
Location
Spain
Work
Digital Workplace Architect (EMEA) — IT Consultant
Implementing authentication processes is always a nightmare for me. I always have the standard diagram of the authentication process flow and looks simple and easy, but not when trying to add it to the application.
I can never recall how to use Regular Expressions correctly, ever. I've probably googled about it a hundred times or more! However, it's an easy-to-understand topic, just hard and confusing enough to commit to memory. For a challenging topic, I'd say concurrency, because there are many things that seem to mean the same thing but they're different. Additionally, they mean different things to different people so reading different articles just adds to the confusion. Also, it's a concept that's hard to grasp unless there are visuals denoting time and tasks. If you ask me what are the differences between concurrency, parallelism, multithreading, asynchronous, and threading, I'd be stumped, or at the very best, extremely unconfident in my answers.
As a self taught programmer, I was never immersed in the OOP ways. I got into FP from pretty early on, and while I am glad to have learned FP without imperative baggage, I am just starting to see the value in OOP approaches for certain problems. (Don't get me wrong, I'm still an FP fanboy...)
Engineering Manager at Greenplaces. Writing about PR review, merge risk, and EM craft. Building Merge Lantern, a risk-triage platform. Strange and wonderful things for the web, mostly.
Location
Raleigh, NC
Education
Bachelor of Science in Software Engineering, University of Phoenix
I think, Design Pattern will be the next toughest concept to learn, esp when learning from the book by the Gang of Four. The topics themselves are really tough; the example code using C++ making the learning even harder. So, I will postpone my plan of learning it.
Implementing authentication processes is always a nightmare for me. I always have the standard diagram of the authentication process flow and looks simple and easy, but not when trying to add it to the application.
Yes, learning oAuth makes my brain overheat too.
I can never recall how to use Regular Expressions correctly, ever. I've probably googled about it a hundred times or more! However, it's an easy-to-understand topic, just hard and confusing enough to commit to memory. For a challenging topic, I'd say concurrency, because there are many things that seem to mean the same thing but they're different. Additionally, they mean different things to different people so reading different articles just adds to the confusion. Also, it's a concept that's hard to grasp unless there are visuals denoting time and tasks. If you ask me what are the differences between concurrency, parallelism, multithreading, asynchronous, and threading, I'd be stumped, or at the very best, extremely unconfident in my answers.
As a self taught programmer, I was never immersed in the OOP ways. I got into FP from pretty early on, and while I am glad to have learned FP without imperative baggage, I am just starting to see the value in OOP approaches for certain problems. (Don't get me wrong, I'm still an FP fanboy...)
Docker and Kubernetes. I feel like every time I work with it, I have to relearn it 😞
I think, Design Pattern will be the next toughest concept to learn, esp when learning from the book by the Gang of Four. The topics themselves are really tough; the example code using C++ making the learning even harder. So, I will postpone my plan of learning it.
Domain driven design. It's not a full list of what you need to do. Pick three and try it out.
React. I’ve tried numerous times, but I never “got” it…hopefully this time it sticks…
Machine learning, big data is a complex topic.
Docker & Kubernetes >_<
OOP concepts