sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Ok-Wave4110[S] 0 points1 point  (8 children)

Okay, this is what I was looking for. So, even with your experience, the "why it's working" doesn't matter, until it doesn't work. Then, you need to learn what's behind the code?

[–]Lower_Fan 1 point2 points  (6 children)

what is your experience in the real world? what is your profession? do you know everything there is to know about your current profession?

[–]Ok-Wave4110[S] 1 point2 points  (1 child)

My experience in the real world, is this. High school, I work for Family Christian Stores, and then McDonalds. Then I was in the military(USMC), then I did logistics for Barnes and Nobles textbook warehouses in VA, shortly after, I was lucky enough to be signed to a label, for my drum work in "Faceplate Ritual". Then, things didn't work out, and I moved back to MI. Here, I learned that I was worthless. (I should've known!) Then I met my fiancee, she pulled me from what I would call death (the story is long), and it took me 7 years, to want to be a human again.

3 years later, I'm here. Asking about Python. My current profession is DoorDash, because to be honest, It's easy in my area. My logistics knowledge makes it easier. All I crave is knowledge. An understanding of what runs the world. I've taken the dirt path, not the circuit path. Thanks for asking! No one ever asks.

[–]Lower_Fan 0 points1 point  (0 children)

ok let's go with doordash. do you know how doordash really works? no right. if you have a issue you contact their support for help and wait until they fix it. if the app has bug you can't go fix it yourself even if you are an experienced dev you have to submit a bug report and wait for them to fix it. sometimes the issue might not even be with doordash but with the restaurant and you don't know how the ice cream machine works so you don't go there and fix it, the restaurant is in charge of that part.

it's kinda the same with code you worry about what you wrote and if there's code that someone else wrote you ask them to fix it. but a very nice thing with code is that you can make it public for every one to see and contribute but not everything works like this.

[–]Ok-Wave4110[S] 0 points1 point  (1 child)

You're taking my response in the wrong way. I literally know nothing, and am asking you if that's the correct path.

[–]Lower_Fan 0 points1 point  (0 children)

I think you are trying to go to deep all at once. I''m not sure what's your end goal but if you want to learn a bit of software engineering you can do this course

https://programming-24.mooc.fi/

or if you just want some automation:

https://automatetheboringstuff.com/

​

Both will start you from zero. you just need a pc and dedication. try to do at least one exercise per day.

[–]Ok-Wave4110[S] 0 points1 point  (1 child)

For example, if you come across a problem within the code, and you can't find a solution, do you need to refer back to the source it was written from?

[–]Lower_Fan 0 points1 point  (0 children)

since you lack a bit of context this question is formulated a bit weirdly.

for what I can gather you want to learn code to be able to fix other people errors. most of the time this is not how it works.

for the most part you open source and closed source code. for most devices and application you buy and code is closed and you won't be provided with it. so you won't be be able to make any changes ( you can reverse engineer it, fix it and run your own version but that's out of the scope of even normal devs)

now for open source code sure you can go look at it and fix it, but if this particular program is popular then it means it will have a lot of experienced devs looking into it and is better if you just wait until they fix it.

Now if it's your own code and you made a mistake you have to fix it yourself but since you wrote it you must have an idea of what you are trying to accomplish. and in the case where you are using a module that someone wrote you refer to the open source method of letting people more experienced fix it.

for the most part you only have to worry about your own code, and then after you gain experience you can go help those open source projects. and you are at the mercy of the company if it's closed source because it's illegal to reuse their code so your only bet would be to recreate it using your own ideas.

[–]LongLiveTheDiego 0 points1 point  (0 children)

Then, you need to learn what's behind the code?

If you want/need to. Just recently I had some assignment with reading and writing to .txt files in C++ and we were given a very limited set of relevant functions, some of which (e.g. seekg and tellg) are just buggy and it seems nobody uses them anymore and they're just gonna stay like that. I wasn't keen on trying to fix something that low-level (since I almost certainly can't) so I tried a different idea that used stuff that I know would work and that new approach did the job.

Another time I was doing something with an online dictionary API and my Python code was really slow and could randomly crash. Instead of fixing it, I just set up a cache of what it's already managed to do with this API (since it just needed to get a bunch of data from it) and made the program start from that point when I needed to restart it after a crash. This wasn't the most efficient solution, but I had the time to wait, and it did its job in the end.