What technology or concept tripped you up before you eventually got a grasp? Or maybe it's still causing problems for you?
For further actions, you may consider blocking this person and/or reporting abuse
What technology or concept tripped you up before you eventually got a grasp? Or maybe it's still causing problems for you?
For further actions, you may consider blocking this person and/or reporting abuse
Nik L. -
Paulo Henrique -
Spandan Sehgal -
RyTheTurtle -
Oldest comments (88)
Rust. I tried maybe three or four times, I understand concepts such as Option monad etc. but I really cannot write code that makes sense in it.
Hah,
Since Rust is so hard to learn, why many developers love it at StackOverflow.
I think it's not easy, it really needs more time to understand the borrow checker.
Yeah, borrow checker is a b**ch, although I think I mostly figured it out. But I think the docs about it could be better.
Work-life balance. ⏱
I feel like I still need to handle them properly.
After that, Rust's borrow checker. 🤓
Totally agree, often be able to combine work-projects-study-life seems imposible. And I don't have kids yet!
Don't worry. :-D
You excelled yourself on this one ;)
Integrating TradingView charts into an angular project, weird stuff... (It was not that bad, but really confusing and different to any other lib I've integrated...)
Yup, this one was hard for me also...
Myself...it's an ever learning experience. And regex. I swear I have to re-learn it every time I need it, and always forget it after a week of not using it.
The same feeling about regex,
and there are some trivial differences between different programming languages.
To be honest, relational databases.
They seem so straightforward, right?
I went into university as a self-taught C/asm programmer and I thought I knew a fair bit. My databases course was really difficult.
I admit I was that student who didn't always turn up on time, or at all.
I got 0% on my databases exam, because I handed in a piece of "artwork" instead. I drew a scene with a man in tatty clothing lugging a grandfather clock on his back down a long stretch of beach. I remember this because it was a representation of how I felt time was dragging in the exam, and I didn't understand the questions well enough to bother trying to answer them; I knew I would fail.
It wasn't until years later, when PHP/MySQL was just starting to get attention, and I found an example of the simplest thing on someone's website. It showed me how to make a guestbook. Remember them? And it explained what it was doing step-by-step, and I understood it without even furrowing my brow.
The lecturers at my university had thrown us into the technical side of things straight away, trying to teach us data concepts without giving the simple example, the td;dr we're used to seeing at the top of documentation these days.
Then I went on to become the SQL ninja I am today, who only rarely brings down production with a missing clause.
I had a similar "climbing road" for data structures.
Haha tell me about it. Thought I could wing my intro to databases class with some programming knowledge... Guess the joke was on me 😥
Mastering the skill of saying NO.
Dynamic programming, still can't wrap my head around this concept!
For me, understanding Overpass API was a nightmare at the beginning. But, i didn't give up and i started grasping it after a week 🌞
CSS,
I can not remember the properties, need to search it whenever I use it, I don't need to work much with it in my daily work, luckily!
I can not get the logical pattern of CSS. It's complicated for me.
Any suggestions？
I was very slow with css when I first started! I suppose my proficiency came from being a fe developer and being exposed to it all the time. There are very few you have to remember, everything is googleable or on a cheat sheet. If you have a nice text editor that has auto-complete for css you can probably make good guesses on what the properties will be.
What do you mean logical pattern of CSS? Specificity?
How much of software development is not actual software development - so much is talking to people, thinking about approaches, research, etc etc etc - it's not just a case of "make stuff" there is soooo much more too it!
development =/= coding. Writing the code is usually the easiest part. Everything else is what a company pays us for.
Soft skils
Two podcasts that helped me:
Also a workshop in non violent communication that was eyes opening
I'm totally into Developer-tea, it's amazing.
Developer tea is the best
Multithreading. I mean, I got the concept pretty fast, but getting it right with all the locks and semaphores simply didn't sit well for the longest time. Honestly, I'm not sure I get it now, 20 years after learning about it the first time - though to be fair, I can count on one hand the number of times I've actually used threads, so not much practice in that area.
DevOps, so many definitions, colors and flavors to choose. Some are hard to implement and others are so good.
Some people think DevOps is a state of mind, let’s do yoga and meditation, everything is going to be ok.
Transitioning from a scientific research background to software development job.