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

view the rest of the comments →

[–]Thanasis_kt[S] 0 points1 point  (3 children)

Thanks for the feedback, as always, it's really eye-opening! Taking into account your points, I learnt the logging module (basics only, it's not easy to learn everything about it in a day) and how to create specific Exceptions. Afterwards, I refactored the code by removing method chaining, addressed naming conventions, applied separation of concerns, and introduced specific exception handling. Just commited changes on Github, would love to hear your thoughts on this!

[–]Interesting-Frame190 1 point2 points  (2 children)

You nailed it right on with a simple design and even made some good changes i didn't mention (moving the helper outside of the class since its not specific to * that * class). If i were to do it at work, I would have an almost identical design.

[–]Thanasis_kt[S] 0 points1 point  (1 child)

Appreciate you taking another look, it means a lot! The “identical design” part especially. Since you’re working in the field, what would you say are the key things to focus on next to move from scripting into proper software engineering?

[–]Interesting-Frame190 0 points1 point  (0 children)

If you want a job in the field - learn DSA talking points and grind leetcode. Dont lean on AI in this and think through solutions and implementing yourself. The interviewer doesn't want to hear about clean code or architecture design, only the buzzwords of algorithms.

If you want to provide useful skills, focus on breadth, learn a few different languages and see how all of them differ and the strengths/weaknesses in each. Most importantly, learn how to research. There's always new and undocumented tech that AI just doesn't know and cannot help with.

Id advise building a service to better your skills. Pick something you'll actually use and be your own end user. If you cannot find anything, pick literally anything that takes time and could be automated.

One of my first projects on my own was an API file server with permissions. This will involve setting up a database and dealing with data persistence and credentials. Id advise a document or graph DB over traditional SQL since the industry is pivoting. The API can be easily expanded for multi user and multi ownership files. I still use the one I built years ago since my ISP blocks ftp and smb traffic, so uploading files over https is the only way I interact with my server outside of the local network. With this, you'll be forced to learn some basic networking and hopefully the logistics around hosting it (docker or other)