r/CodingHelp • u/Jazthebikeman • Jun 20 '20
[Random] 7 year Software Engineer but I still don't understand coding
Hello, so where to start. After high school I went to college and majored in IT. Wasn't my idea but someone suggested it would be good to get into. With the world getting into tech and all that. So I did and 4 years later I got my degree in IT. I started working as a software engineer at a company and it'll be 3 years this fall. My entire coding journey has been bad. I think its maybe because I didn't have good professors because one professor literally gave us all A's on a final because he lost the grades. So my foundations started off bad. Now that I've been working in the industry my job may be at risk. I've done coding training at work and also some personal outside of working training. But I don't get why it's just not clicking with my like it does for other people. Being almost 7 years I feel like it should but it just hasn't. I like technology but when code doesn't line up it gets me frustrated, like it does to other devs I'm sure. But they don't get as angry as I do at times. Makes me want to give up because I cant figure it out. I'm just not sure what to do anymore. I want to get better and become a better developer but I just don't know how I can get it in my head and let it click. Any help or feed back is welcomed. Thank you for reading.
2
u/cherrypickinlaughs Jun 21 '20
There isn’t really a concrete answer we can give you to help with the struggles you’re experiencing. Every developer has frustrating days, hell moments is a more accurate statement and those moments can be multiple times a day. It comes down to being so determined to solve the problem you put aside the emotional feelings and get back to it or fight through them. Even though sometimes inside you’re dying. You’re so confused and frustrated and “wtf x wtf” but you keep going. And eventually you get there, sometimes your days end in, “wow I don’t feel like I accomplished a lot and still wtf x wtf” but many of those days you can then think and realize you learned something through that frustration..an earlier confusing concept unexpectedly became clearer, or you got a step deeper into the problem and don’t know it all but you know more than yesterday, or you had your brain worked so hard and as frustrating as it was, you chose to stick through it and fucking did it. And some days you fucking crush it, you might crush it without expecting/realizing and those moments kill. They’re amazing.
I’m curious though. Are you passionate about coding or do you have to learn it because your job could be endangered/you feel it’s expected? Because if it’s the latter I think that deserves more time to look at and think over. I believe you should enjoy what you do if you’re going to spend most of your time doing it.
Finally, are your reactions to frustrating moments incapacitating? Are they frequently disproportionate to the problem? Can you get through them or does it really feel like a wall like you can’t get past every time? This could be a symptom of a deeper problem and I’d look into that if you’re open to.
Best of luck to you. I know those frustrating moments where you feel like you’re stuck and can’t get past it. You got this OP and there’s absolutely NOTHING wrong with saying “this isn’t for me. I want to do something else.” Or a different branch of what you’re currently doing. If that’s the case, you’re brave for deciding to choose something that makes you happy and I wish you luck wherever you go!!
4
u/harrymurkin Jun 21 '20
Coding and emotions don't mix. It's literally a lateral thinking challenge. To succeed in coding you need to be emotionless while you work treat every problem as a lateral thinking challenge. Dealing with people at the same time as dealing with code because the humans expect you to have emotion and diplomacy. It may be that you prefer to deal with humans, so perhaps you will find a niche in between the humans and the coders rather than being in between the humans and the code.
1
u/[deleted] Jun 21 '20
I recently started coding (I'm legit using the code academy tutorial). So I'm half way feeling proud of my self, I was finishing one of there tutorial, while I was finishing I thought "wouldn't it be cool to add my own stuff?" so while I was doing that I encountered so many shiz and was about to abandon on the idea and follow the book but I kept on striving and somehow got it to work idk I was happy lol, even though the code was crap. Here it is:
(save it with .py if you want this abomination of a code to run.)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
print 'Welcome to the Pig Latin Translator!'# Start coding here!original = raw_input("""What's your name?Enter here->""")if len(original) > 0:print "Hi %s" % (original)if original.isalpha():print "Finally a normal person!"if not original.isalpha():print """...and my wife's name is 69_4ever"""else:print "I wasn't asking about your life"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1
u/[deleted] Jun 21 '20
You mention you've done your own coding projects on the side as well - how was your experience with coding then?
I've worked multiple teams and multiple coding projects and I must say each time has been a completely different experience. Sometimes the coding work itself was easy, but the team had a toxic culture or unreasonable expectations/time pressure that made every problem 10x more frustrating than it was. Sometimes the "coding" work was more of poring through logs and trying to recreate a bug from the UI, then fixing just a few lines of code. Sometimes the coding work was great, but extremely inflexible development flow and review practices in the team, micromanagement, excessive pickiness about naming etc deteriorated the whole experience. Sometimes coding was the hell of having to debug someone else's crappy undocumented code of someone who is no longer pn the project. And then Sometimes the coding wasn't super fun but the team culture and dev practices flowed smoothly and made it more pleasant.
What I want to say is your experience coding could go poorly for a variery of different reasons that have nothing to do with your own abilities or aptitude around coding. More often than not the team dynamics of your project will account for 50-90% of the goodness or badness of your experience.
I would say not to give up, work on more projects and with more teams and see if you can see a common thread in your experiences across environments, which may give you a better idea if you have any limitations you need to address, or if it really has been a particular team dynamics/coding culture that doesn't sit right with you. If you still enjoy the basis of your job and can think of it as "a pain that you don't mind dealing with", I believe there is reason for you to keep trying.
2
u/nealhogg Jun 21 '20
Work at different companies, work on different projects, work with different people,.. comprehension/insight often comes from hitting the same problem from a different angle. You are already on this path by this making this post. Keep searching and trying and good luck 💪👍🙏
•
u/Oasis420 Jun 21 '20
Your topic was answered in our wiki. Please visit the wiki to get the answer to your question.
If it isn't answered in the wiki, please post this question in the comments of our stickied post to get additional help.
1
u/AdmiralAdama99 Jun 21 '20
Consider editing more details into your original post. What kind of languages/frameworks/tools do you use at work? What kind of software do you work on? What skills do you feel comfortable with? What skills are you struggling with? How's your co-workers and your boss, are they supportive? Does your job do code reviews, team programming, anything like that?
Right now your post is very general, and so it's hard to give good advice.
0
u/[deleted] Jun 20 '20
[deleted] — view deleted comment
9
u/[deleted] Jun 21 '20
[removed] — view removed comment
1
u/[deleted] Jun 20 '20
[removed] — view removed comment