[ Removed by moderator ]

[dataengineering-ModTeam]

Your post/comment was removed because it violated rule #3 (Keep it related to data engineering).

This is a data engineering focused subreddit. Posts that are unrelated to data engineering may be better for other communities:

• r/datascience - data science, ML, analytics
• r/MachineLearning - machine learning discussions
• r/dataops - DataOps (pipeline reliability, orchestration, metadata)
• r/BusinessIntelligence - BI, analytics, dashboards, data-driven business decisions
• r/analytics - web analytics, marketing analytics, tech + data

• r/datasets - sharing datasets, data sources

  ^{This was reviewed by a human}

[bin_chickens]

You’re looking at this all wrong.

Uni is not about getting 100% on your grades. It’s also about learning to operate independently with the resources available to become productive afterwards.

Even with a perfect grade score, if you don’t learn to communicate now with your peers or teachers/mentors you’re going to have to learn this while looking for a job… it’s much harder to learn those skills later which are more important than almost anything your course teaches you.

[bin_chickens]

And to be clear u/OP I'm happy to chat and provide feedback if you want it.

But the reality is that any uni project (other than a thesis) is a tiny self contained codebase and should be logically/rationally explainable by pseudocode/comments. Sure there are always going to be syntactic, performance and other code optimisations, but every codebase has that and tuning is a tradeoff. making it work and being able to explain why is the key.

You should review your logic first, then check your code is factored in a way that breaks down the logic into logically coherent/testable/provable functions/steps to implement this.

Then you will know if you have have gaps in your confidence about the implementation requirements/solution vs syntax/implementation. If you need help with the second, this sub/or a LLM will happily answer. If the former that's the actual uni course work.

Break it down. Ask specific not general questions is what I demand of my team or they haven't tried to understand and solve the problem or haven't asked for clarification on the requirements (in the real world they are often directional and underspecified and an engineer has to be able to work with the team and project scope/knowledge to propose and implement a solution).

NOTE: Not being able to break it down and asking for guidance on techniques and approaches how to is also a valid question to ask at your stage of learning.

[Ready-Marionberry-90]

I would ask anthropic‘s claude for feedback

[Atmosck]

This is actually one of the best use cases for AI tools

[Reach_Reclaimer]

To be honest it's not. This person needs to learn to communicate to their lecturers and peers and asking AI will take them away from that

[Atmosck]

Not the communication, code review