London | Nadika Zavodovska | Module-Tools | Sprint 2 | Shell-Pipelines

[nadika-zavodovska]

Hi,

I've done all the tasks for the shell-pipelines.

Self checklist

• I have committed my files one by one, on purpose, and for a reason
• I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
• I have tested my changes
• My changes follow the style guide
• My changes meet the requirements of this task

Thank you.

[ehwus]

This is really great work Nadika, the scripts read well and perform in exactly the way that we've required. This shows a great understanding of how and when to use shell pipelines, building on your solid foundation of shell tooling in general.

[ehwus]

question: This works well, but can we find the nth row of a file more efficiently?

[nadika-zavodovska]

Thank you for your great question, @ehwus Alex. I think sed -n '2p' is faster than head -n 2 | tail -n 1 because it prints the second line directly without extra steps, making it simpler and better for large files.

[ehwus]

question: this works well, but could we allow tr to access the file directly and save having to use two programs?

[nadika-zavodovska]

That's a great question, and it's a new insight for me. Yes, we can access the file without using the cat command by running tr '!' '.' < text.txt.

[nadika-zavodovska]

This is really great work Nadika, the scripts read well and perform in exactly the way that we've required. This shows a great understanding of how and when to use shell pipelines, building on your solid foundation of shell tooling in general.

Thank you, @ehwus Alex, for your really helpful review. I appreciate your insightful questions that helped guide my approach. Your encouraging feedback motivates me to keep improving!