For further actions, you may consider blocking this person and/or reporting abuse
Read next
Implement Secure Web Link Preview in your Messaging Application using NodeJS
Sohail Pathan -
8+ Reasons to Hire HTML5 Developers for Mobile App Development
Kapil Jetawat -
Top Image Editing APIs 2024
Sohail Pathan -
"Charney joins Arsenal GK in tears" Wolverhampton nucleus of chain transfer
Safetotosite pro -
Oldest comments (17)
Finding the right keywords for your google search π¬
Especially if you're using a language like "p" π
I agree with @afif google search skill.
Understanding concepts.
Sometimes my mind just shut down π
Hardest part for me is trying not to get overwhelmed and burning myself out
When you need to build a feature that doesn't match the default way your framework was designed to be used.
Stackoverflow. It is very overwhelming as new developer but once you choose the right keywords in your Google search; Stackoverflow is an amazing resource.
Error Codes. This ties in with the keyword Google search posts below. It is crucial to read your error codes in totality and Google accordingly. Sometimes, it takes a few tries to find the solution and sometimes it's as simple as adding a "." where a ":" was needed.
Also if anyone is hoping to learn some basic computer science concepts; there is a wonderful podcast called Base.cs!
codenewbie.org/basecs
There's so many different directions a programmer can take. So it can be rather confusing knowing what is the best step each programmer can take. So for new programmers it can feel overwhelming since there's so many language to learn and tools to use that it is hard to decide where to focus. Then when a programmer does decide where to focus, it can often be followed with some second guessing.
The amount of things to learn out there! I continually battle with the feeling that my knowledge is going out of date.
For me its been
1-Getting started,
2-finding a path to stay on when learning on ones own (how do I get from point A to point B) - I know that no path is static and its always possible to take a side path or tangent but having a general idea of the steps would be help in figuring out what to learn next
Naming Variables.
I find that you need have a lot of endurance as a programmer. On days when I'm tired or just not feeling it, it can be hard to slog through debugging.
Communicating and validating customer expectations.
Anything curly-braces-based is the next worst thing for me.
Another big pain is proper distributed cache invalidation, have I struggled with that!
Breaking out of tutorial hell. Or trying to find consensus on a given topic π¬
Oh yes. That is hard.
Fixing a bug which is never found :')
(Shall we turn them into features? :D :D)
Actually finding something that you really want to work on. Once you get a bit of a tailwind and you actually want to build something, you'll get out of tutorial hell because you actually have to code to build the thing.
Finding the thing you want to build tho... really hard.