DEV Community

Cover image for What were some of the toughest technologies and concepts for you to grasp along the way?
Ben Halpern
Ben Halpern Subscriber

Posted on

What were some of the toughest technologies and concepts for you to grasp along the way?

What were they, did you every fully overcome your confusion?

Latest comments (87)

Collapse
 
gowikel profile image
Pedro JosΓ© Piquero Plaza

Kubernetes. In fact, I am still on it.

Collapse
 
tcharl profile image
Charlie Mordant

Reactive programming made properly: RxJS or/and Reactor.

Other:

  • Spring cloud (stream+eureka+ribbon+feign+oauth2)
  • Oauth2 identity brokering
  • Data engineering (ETL, Data Vault, Kafka, Dimensional mode, Olap)
  • Observability/tracing (Zipkin)
  • Ansible is also sometimes fun ;-). ...
Collapse
 
hoxon profile image
Leonardo Mangano

Ownership model in Rust

Collapse
 
ads-bne profile image
ADS-BNE • Edited

React for me.

I was very familiar with using JS on a website, so I thought React would be an easy transition. Nope. What stung me was:

  • React is compiled locally. If you're not used to that and how it works then its a pain to get started. When I learnt JQuery ages ago I started with something very, very small eg $(".mydiv).text("hello world");. This worked and I was able to build upon that and create more and more complex DOM manipulations from there. With React you can't just start with that one line.
  • React has a lot of dependancies that don't make sense at first. Node, npm, React-DOM. In most beginner React tutorials there is little to no explanation of these. Initially I thought I would have to learn Node.js in and out before I learnt React - and that's a totally different kettle of fish.
  • React tutorials are inconsistant. Some are very old, some predate React Hooks, some use TypeScript, some don't use Create React App, some presume prior knowledge of things like Redux.
  • It's not intuitive to actually deploy a React component or app up on a live site. Most React tutorials end at the point where you've completed the app on your local machine... cool, but now what? How do I actually get it on my site?
Collapse
 
manuartero profile image
Manuel Artero Anguita 🟨

OAUTH

I've read and even studied several times. My mind just go blank for some reason.

Collapse
 
baasmurdo profile image
BaasMurdo • Edited

Sockets (as in WebSockets), not coding them, that was the easy part.
But actually understanding why and how they work with multiple sessions and clients.

Collapse
 
isupermario profile image
Sarang

And Flex is all you need πŸ˜…

Collapse
 
bandev profile image
Bryan M

Containers and Kubernetes, for my first internship I was thrown into the cloud computing world and I had no prior knowledge of it at all. It took a week to figure out what exactly a container was and why containerized apps are crucial to today's CI/CD.

And kubernetes..... don't get me started with that. Something I'm still trying to figure out until this day xD

Collapse
 
jcs224 profile image
Joe Sweeney

I disliked JavaScript greatly for many years. I just didn't get how to use it, coming from mostly object-oriented languages (Java, C++, even PHP 5 and above). Then, one day, a switch flipped and suddenly I thought it was actually pretty fun! I think it took just embracing a new mental model and embracing/getting over some of its quirks.

Collapse
 
crayoncode profile image
crayoncode

Some concepts of Functional Programming like pure functions and monads. To this day I cannot reconcile/fully understand the idea of functions without side-effects and basically no external state that does not depend on the function's arguments with what I know about programming. I simply could not find a consistent approach on how to build the applications I code on a daily basis using pure functional programming and I would trade my right arm for a look at a codebase of a buisness application that fully embraces FP.