Programming

17383 readers

680 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Feeling dumb (feddit.nl)

submitted 1 year ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

I've been learning on and off about programming for 3 years now. Mostly front-end, html/css/js, for school projects. My degree isn't in CS or IT, so projects that give the opportunity to code are scarce and often short. So I get that I may simply may not have enough hours in coding.

So I'm delighted to be taking CS50 as a Minor at the moment, this has given me the chance to sink a lot of hours in coding, and currently I am in week 5 Data Structures.

But every time I start on the problem sets, I feel overwhelmed and feel like I don't understand anything. I have to Google/GPT the most basic of things. Even though I've been programming regularly the past 6 weeks, I don't feel as if I have improved and I'm starting to doubt if this is a career for me.

In a year I would like to find a career in development. Have any of you felt this way? And what has helped you get rid of this imposter syndrome?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Indeed. But you just have to learn to use them like any tool.

Most things that used to be a Google followed by skimming articles can now be a question to them.

They are also remarkably good at explaining code snippets. If you drop a line of code in there and ask it what it is it'll explain it piece by piece with correct terminology and answer any follow up questions really well.

That gets around the not knowing terminology problem that many beginners have

I do this frequently with the legacy SQL I have to deal with at work. It can handle some really nasty stuff very well.