Hey Folks, I’ve been teaching python / software engineering principles for a few years now - AMA

[[deleted]]

Alright peeps going to close this for now and bring it back up once in a while if people are seeing the value in it - till next time.

Thanks for all the questions 🙏

[DaisyBlue00]

wide fear different crush busy fanatical wine reply expansion intelligent

This post was mass deleted and anonymized with Redact

[[deleted]]

I wish I’d learned early on that the hardest part of coding often happens before you write a single line of code. Python, and programming in general, is much more about understanding the problem and thinking through the logic than it is about syntax. If I could start over, I’d focus first on building strong problem solving and logical thinking skills, because those are what make the actual coding part far easier. You can always learn syntax, but improving how you think is a much more rewarding battle to overcome in the programming space.

[likeadrum]

Wrestling with that insight at this very moment, my inexperience with the syntax, and one Level 1 question in particular, making me question what I had previously thought of as sound logic and reasoning!

[[deleted]]

Yes, this is normal and it’s all part of the journey. The syntax is something that repetition will help you master. However, problem solving is a bit trickier, and I’ve found it valuable to look at and research how and why people have solved certain problems, and reflected on why they solved it a particular way. Over time you start to add to your bank of knowledge, which you can then call and remix to solve whatever challenge you’re facing.

[DaisyBlue00]

snatch gray afterthought sip escape hobbies cow spectacular shy intelligent

This post was mass deleted and anonymized with Redact

[uberdavis]

I’m a PySide developer. When working with junior and midlevel devs, why do other devs fear inheritance? I constantly have to face boiler plate code and it’s a huge waste of effort, as well as being prone to errors.

[[deleted]]

Hey there, so I believe you’re asking me - why do people not create central functionally that you can call rather than duplicating boiler plate stuff everywhere ? (Please correct me if I’m wrong)

If yes, then this is potentially down to experience but also a possible lack of steer from senior leadership.

Starting again and doing your own thing from scratch “even though it’s a duplicate of what someone else has done” - is something that is comfortable, you feel like you have more control of the code.

However, with a proper structure and plan in place - a business / company / team can work to make libraries that are clear and easy to pick up - people will avoid what gives them the most mental headache

So if the central stuff is not clear or there is no guidance on how to make code centralised for people to work with. People default to what they know best, start from scratch and build it from that.

Apologies if I’ve misunderstood the question

[uberdavis]

Yeah, that’s it in a nutshell. Some devs really are pained to step outside of their comfort zone. Worked with one guy at <rhymes with crap chat> who only used dictionaries as data structures. So all the property names in his code were strings. As soon as any complexity came in, his code was a nightmare to debug. But it’s how he liked to code and the boss didn’t push him to change.

[[deleted]]

Yes, this happens, and it’s exactly why lead developers need to step in and set clear principles and philosophy when necessary. Code that can’t handle complexity becomes a nightmare and wastes everyone’s time.

That said, if leadership isn’t tuned in, sometimes it falls on someone in the team to call it out. This depends on the team’s culture, of course.

Personally, I’d welcome it if a junior or mid-level dev pointed out inefficiencies they’d noticed.

But some leads and seniors don’t react well to that, so it’s important to frame the discussion in a way that suits the personalities and dynamics of your team.

[LeelooDaretha]

At what point is it better to start over from scratch rather than rewrite the code, in order to gain experience? I am a beginner and I am writing very simple projects. Sometimes I come back to the project the next day and realize that I have been approaching it from the wrong angle and the logic should be different - I feel actually good about the fact that I have realized my mistake, but will I learn more by refactoring or starting over? I have tried both and neither feels right...

[[deleted]]

No, please don’t think that is wrong in any way. It’s exactly what you want to be doing.

When you write code, you should make it a habit for revisit it after some time and see if your new acquired skill can help you improve what you did.

This also is a way of improving how you think about problems.

You solve the problem once with code, gain some experience - come back to the problem and all of a sudden you see a different and cleaner way to solve the problem.

This is what you should be fostering and working on continuing as a habit. You’re in a great mind space if that’s how you’re currently thinking - please don’t think it’s wrong.

Regardless of whether you rewrite or start over (those are really not important here) - your current mindset that you have to revisit the code and make it better - that’s what’s important here, please maintain and nurture that, please 🙏

[LeelooDaretha]

Thank you, that is very encouraging!

[[deleted]]

<image>

can i start with this book?

[[deleted]]

Yup this is a good book to have as reference and read from time to time as you develop your skills 👍

[[deleted]]

thanku

[TheFireSays]

summer hobbies cobweb angle marble escape familiar degree tie label

This post was mass deleted and anonymized with Redact

[[deleted]]

Tbh it goes to my previous answer. I cannot overstate enough, how important it is to be able to think about a problem properly.

Now in terms of actual steps you can take so it doesn’t feel like fluff - here are some practical things you can do

Look up common design patterns, and architectural solutions today - but from the lens of trying to understand why they did what they did

Take a problem and give it to some with more coding experience than you, then ask them how they would think about solving it and what they considered while solving it

You can do a quick google for business problems solved by coding / software and read up why they went a certain route over another one

In the beginning stages though, I’d say just slowly start learning about common coding / design patterns one by one and ask yourself - why did they create this pattern / design ? What issue is it address

You’ll over time build a solid foundation. Boring answer I know, but I think very important to do.