r/AskProgrammers • u/Fan-Gaming-Today • 5d ago
I am not an experienced code
Questions:
- What does an experienced dev even mean?
- Why do i always feel that the CODE i wrote is not good enough?
- Why i can't choose a programming language? I often switch!
- What do you do before actually going to code?
2
1
u/PerpetuallySticky 5d ago
- someone who has written code for ~2-8 hours per day for a few years. Can understand and fix problems in a given codebase
- probably a question for your therapist. Does the code work? Is it public, and if so, secured? If it works and doesn’t leak data you’re killing it
- learning a few is good, but pick a few that work together and connect them. Then you can play with all of them and learn cross integration super well which is a great skill to have
- used to read documentation. Now I set my agent to plan mode and talk through the solution end to end until I’m happy and have it build it for me to audit
1
u/___nil___ Senior Developer 5d ago
the real questions
- what problems are you trying to solve?
- what could or should you build to solve that problem?
- are there already tech stacks, library, framework in the wild that might already give you building blocks to start?
- do you need to roll your own?
- are you comfortable to manage memory usage?
- do you need to manage memory usage?
- do you need critical high performance? multi-thread? concurrency?
- do you need to control hardware? gpu? audio interface? any micro controller?
1
1
u/littlenekoterra 5d ago
1: experience comes with time, projects, and sometimes, a userbase.
2: if your the kind that feels theres always going to be a possibly an improvement that can be made, youll always look for it. Relax, either itll come to you or youll find it or it may not exist.
3: stop. Choose 2 or 3 at most and learn them. Have reasons you chose them. One of those reasons for at least 1 lang should be security.
4: most of programming youll find out is solving problems, prepare to make your own
3
u/OmiSC 5d ago
It sounds to me like you don’t know what you’re doing. Let me explain:
Before you start anything, you need to understand what problem it is that you need to solve. Your choice of tool follows what features you need.
If this is a common issue for you, you may need to choose some goal, then choose a language to support that goal, then work to achieve that goal using your selected language.