On 14-04-2022 13:50, Abhradeep Chakraborty wrote:
Kaartic Sivaraam <kaartic.sivaraam@xxxxxxxxx> wrote:
That's good to know. Do let us know if you have any experience with C
and shell programming outside of your contributions to Git.
Thank you for reviewing my proposal. I used C language in my B.tech
classes. I never used C in practical/real world projects before. So,
putting altogether, no, I didn't use C and shell in real world projects
before.
That's good to know. Thanks.
Taylor has shared feedback on the proposal and timeline which I hope are
helpful to you. Specifically, Taylor said:
So I think it makes sense to try and find a way you can dip your toes
into 2-3 of the sub-projects and get a sense for what feels most doable
and interesting, then focus on that before allocating time for more
projects in the future.
>
I agree with this. It's better to be practical than ambituous when
planning the proposal.
Okay, I am willing to work on first sub-project then. Should I remove the
other subprojects then?
Rather than deciding the plan in haste, I would recommend that you put
some more thought into deciding the plan for your proposal. Take some
time to reflect on the different parts required for the project,
potential things that might interfere with the project etc. This would
help you come up with a more refined plan.
This might need some deeper understanding of the project that you would
be working on. Do feel to ask us in case you face any issues with this.
Also, you could use Taylor's suggestion as a possible starting point for
the plan:
> If you end up working on this, I would suggest budgeting a week or so
> to try out a couple of different sub-projects, and then decide where
> to spend your time from there.
Hope this helps,
Sivaraam
