selfteaching / selfteaching/selfteaching-python-camp

Day03 编程学习的感悟与求助

Open
#365 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

学习心得分享
Dominant language
Python
Stars
151
Forks
875
PR merge metrics
No merged PRs in 30d

Description

所属班级:100104
学习用时:6小时
收获总结:

  1. 今天只大概完成了1/3的任务,收获了满满的挫折感
  2. 白天阅读的时候,就感觉脑子要炸了,虽然前两天要阅读的内容并不少,但是当时觉得作业好完成,所以懵懵懂懂就算过了,对内心也没造成什么冲击。但一早看到今天有三个作业,而且不是那种很容易找到方法的,一下就懵了。尝试认真读文档才发现,涉及理论的,理解很粗浅;涉及实务的有极为庞杂,根本找不到头绪。一做题就更猛了。
  3. 晚上回家,把任务一点点的拆解成具体更具体的有通用价值的问题,搜索并尝试后基本完成了任务一。但搜索效率太低,任务二卡在如何排序上,看到时间临近,果断放弃。
  4. 感悟1:提出一个好问题很重要,你自己有贡献,别人也知道你到哪里了,怎么帮到你;问题是自己觉得自己提不出有意义的问题来,太低级的问题既不好意思问,也担心沟通不清花费更多的时间。问出好问题的前提是自己得懂。
  5. 感悟2:如何忍受不确定性?如何处理重点? :: 以任务为中心?那直接解决任务,那自己还能学到什么呢?如果你不懂,你又怎么知道哪个是重点呢?
  6. 小技巧:搞一个IDLE在旁边,阅读时的例子粘过来,可以直接执行试试,没明白就调整不同参数试试,非常有助于理解。
    遇到的难点与问题(是否解决):
  7. 看了一大堆的概念(numeric,iterator,sequence,set,mapping...),这么短的时间,有清晰的理解都不容易,操作就更谈不上了,全是难点,全是问题。
  8. 最后还因为README.md的版本冲突无法上传,现在处理中。

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue is a learning reflection rather than a defined change request. It mentions a README.md version conflict, but names no target section, tests, or expected outcome. Start by reviewing the README.md conflict and the surrounding issue context; the work is not complete until a specific documentation change and acceptance criteria are agreed.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.