this post was submitted on 13 Jul 2023
6 points (100.0% liked)

General Programming Discussion

7831 readers
1 users here now

A general programming discussion community.

Rules:

  1. Be civil.
  2. Please start discussions that spark conversation

Other communities

Systems

Functional Programming

Also related

founded 5 years ago
MODERATORS
[email protected]
[email protected]
6
Today I feel dumb. Less than two months into my first Software Developer role and I am starting to get to grips with the codebase, but everyday I feel like I’m just making poor choices (feddit.uk)
submitted 1 year ago by [email protected] to c/[email protected]
12 comments fedilink hide all child comments
 

I have to say that since starting I’ve had a lot less support than I was expecting and I’ll be given something to do but very sparse direction. I’ll go away and do my best and usually be told that based on the little guidance I have done good but maybe we could do it this way or that way, which is great as that’s how we learn right?

Also, preface saying that I’m working on a Typescript React app alone as the others have other projects.

So queue today. I’ve got a todo list of questions about my implementation and things I could do better, which they like my diligence of keeping track. Well I was working on a component and like an idiot I hard coded a lot of the data that is subject to change if say they add a new let’s say PetType. So the SE comes over, tears my code to shreds and like a wizard makes it work even better with only dynamic use of data.

I don’t mind the tearing my code to shreds as again it’s a learning experience but my self esteem has dropped off a cliff.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

There's a difference between iterating on your code patterns until you get something working and iterating on the solution as requirements evolve. You're only two months in so you still have loads to learn, but eventually you'll come to know all the "best practices" so that when you're presented with a problem, you can immediately know what the ideal solution should look like. The caveat there is that the ideal solution is subject to change as the situation changes.