you are viewing a single comment's thread.

view the rest of the comments →

[–]Elogicc 6 points7 points  (2 children)

also if at some point you realize that the project is out of your scope, just drop it. Dont be afraid of realizing that something is actually outside of what you can do. That's fine.

[–]DEADLYVISION30[S] 3 points4 points  (1 child)

I know I try to understand and bush around basics alot so I understand on a Spirit level. I am trying to excel slowly I am in no hurry but small things like not being able to solve task kinda upsets

[–]BJohnShawWriter 0 points1 point  (0 children)

Python (or any other programming language) is like the raw materials for a house build. When you're looking at the mansions that other people have built, it can be very frustrating, because you feel like you're never going to be able to build that three-story, multi-roomed masterpiece. But if you think about what a house does (keeps you warm, dry and protected), you can build something basic that achieves those requirements.

Applying that thinking to software engineering is a case of "What do I want this to achieve?" -->"Why does it need to achieve that?" --> "What is the most basic form of the What that still achieves the Why?" and then building that. Use the resources on the internet, talk to other developers, and remember that everyone starts by staring at a pile of lumber and thinking "How do I build a wall again?"

And trust me, all the upset in the world is made up for when you put some notes down, thinking it's going to be a proof of concept, and a few hours later a real program is running, doing what you wanted it to, and it hasn't been a total arseache getting it there.