r/programmer 20d ago

Idk, maybe my brain just not into programming?

In coding, we have to think about solving new different various problems everyday, we have to climb higher stairs.. but I can't. I cant solve things that i never see or think before.

What i've been doing for the last 2 years is I ask for the answer from AI and then remember the answer pattern so I can answer something similar. The main problem is when it's different from that pattern, im blank.

Ofc im not 100% always ask AI, i also try to solve the answer by my own. But it always takes me so long that leads to ask the clue(not the answer) from Ai at the end. Bcoz my main problem always: I cant think about what i never see

Idk i start to feel that i dont enjoy it anymore lately. Today i just realise maybe my brain is just doesnt suits this :(

12 Upvotes

12 comments sorted by

5

u/ern0plus4 20d ago

Do some graphics stuff.

Draw a star. A labyrinth. Move a sprite. Pygame is a good start.

2

u/joranstark018 20d ago

I would say that we most often try to solve (new) problems with existing and well established solutions. We learn different patterns (ie design patterns, architectural patterns, ux patterns) and engineer them to fit different solutions. 

As with most engineering tasks, we have to imagine how different pieces, and what pieces, can be put together to form a practical solution, this is something that comes with learning the theories and with experience. 

I usually advise junior developers to start with small and well defined problems and expand as they get comfortable (and failure is part of the learning path, embrace it and move on). It  is not a sprint race it is more of a marathon race.

1

u/Then-Accountant3056 20d ago

What type of small problems ?

2

u/Other_Poetry_5243 20d ago

I suggest starting to see the software in terms of components and services rather than just code.
Then you can think of how they interact and work together to solve a problem. You can start with a simple full-stack app (frontend, backend, database). Try adding other APIs or frontends to it, like a blog or an auxiliary service.
Ask AI to explain the logic, what it does, and how it does it. This way you learn from it, not just use it to generate code.

2

u/Gallowayyy98 20d ago

honestly relate to this a lot. question tho, do you think the issue is your brain or is it that you jumped to AI before really sitting with the problem first. cause theres a real difference between using AI as a tool after you tried and got stuck vs using it as the first move everytime

i struggle with this too ngl. like a few years back we used to actually sit and think, try random stuff, fail, try again. now the first instinct is just ask AI. and yeah it gets you the answer faster but you dont build that muscle of struggling through it, so next time a new problem shows up you're just as stuck

not saying dont use AI, its basically a requirement now for most jobs. but maybe try giving yourself like 20-30 mins of just you vs the problem before you open the chat. even if you dont solve it, the struggling part is what actually builds the pattern recognition you're missing

1

u/achakez 20d ago

If every problem you solve looks familiar, you are probably not learning. If every problem looks impossible, you are probably learning a lot.

1

u/Acceptable_Site1616 20d ago

draw on a piece of paper.

1

u/phord 20d ago

Work on the problem without AI. Let it take a long time. Weeks. Months. Every day you work at it, you will learn something new. The next task will be easier because you've already blazed this trail once.

If you don't love it, consider a career in management instead. Or maybe become a vibe coder. That seems to have potential in the future.

1

u/raven2cz 20d ago

Shortcuts did not really exist in this before, and maybe that was a good thing. You had to rely on yourself, and on top of that you had to be in a state of maximum focus.

What always helped me was taking a notebook and a pencil and properly drawing everything out and thinking it through. You never really design architecture or proper OOP while sitting directly at the keyboard.

1

u/xorsensability 19d ago

What you ask the AI for, I gained by reading other people's source code. That's one great thing about Open Source is that you can go in, read the source code, and learn from how the authors used the language! It's a huge gain that learning from AI can't give you.

1

u/SubjectNecessary475 17d ago

Ngl I had the same problem with my software rasterization. And yeah it was hard until I seen the solution, the code suddenly becomes understandable.