Lesson 5
SKILLS DEVELOPMENT
Today’s topics
1 Reading comprehension
2 Discussion and Writing
3 Extra vocabulary
1
Reading Comprehension
Read the text “A day in the life of a programmer” and answer the questions.
1. What time does Mariana usually start her day?
2. Where does Mariana work from?
3. What does Mariana do first in the morning?
4. How does Mariana ensure her communication is smooth during virtual
meetings?
5. What drink does Mariana enjoy in the afternoon?
6. How does Mariana end her workday?
7. How does Mariana feel about working remotely?
8. Why does Mariana sometimes watch online tutorials?
9. What does Mariana do in the evening to relax?
2
Discussion and Writing
Discussion prompts
1. Do you think working remotely is a good option for programmers? Why or why
not?
2. How can programmers improve their skills?
3. What kind of projects do you think a junior programmer like Mariana might work
on?
4. What are some advantages and disadvantages of working from home?
3
Writing
Writing
Writing Prompt:
Write a short paragraph about your daily routine as a programmer. Use at
least five adverbs from the lesson (always, usually, often, sometimes, never).
Example Answer:
I always start my day with a cup of coffee. I usually check my emails before
starting my work. I often attend online classes in the morning. During lunch, I
sometimes read a book or go for a short walk. In the afternoon, I work on my coding
assignments. I never forget to take a break every hour to stretch and relax. I finish
my day by reviewing my tasks and planning for the next day.
ra!
ext
Common phrases and frequency
adverbs
Adverbs of frequency
Always: 100% of the time
Usually: Approximately 90% of the time
Frequently: About 80% of the time
Often: Roughly 70% of the time
Sometimes: Approximately 50% of the time
Occasionally: About 30% of the time
Seldom: Roughly 10% of the time
Rarely: Around 5% of the time
Hardly ever: Less than 5% of the time
Never: 0% of the time
Usage tips
Adverbs of frequency are usually placed before the main verb in a sentence but after the verb 'to be'.
Before Main Verb:
Developers always test their code.
The system frequently updates itself.
After Verb 'To Be':
The server is often busy during peak hours.
The developers are usually careful with their commits.
Negative Sentences:
When forming negative sentences, place the adverb before the main verb.
Developers rarely fail to meet their deadlines.
We never skip code reviews.
Questions:
In questions, the adverb of frequency is placed after the subject.
Do developers often encounter such errors?
Does the software usually require manual intervention?
Coding and development
Write code: To create and edit code in a programming language.
Debug code: To find and fix errors in the code.
Refactor code: To improve the structure and readability of code.
Test the program: To run tests to check the functionality of a program.
Deploy the application: To release the application for use by others.
Optimize performance: To enhance the efficiency and speed of code.
Design the architecture: To plan the structure of a software system.
Implement a feature: To add new functionality to a program.
Commit changes: To save code updates to a version control system.
Push code to the repository: To upload code changes to a remote server.
Merge branches: To combine code changes from different development branches.
Create a pull request: To propose code changes for review and merging.
Roll back changes: To revert code to a previous state.
Write unit tests: To create tests that verify individual components of a program.
Coding and development
Fix bugs: To resolve issues or errors in the code.
Generate documentation: To create detailed descriptions of code functionality.
Review code: To examine code for quality and adherence to standards.
Implement an algorithm: To apply a specific method or procedure in code.
Use libraries or frameworks: To incorporate external code into a program.
Follow coding standards: To adhere to guidelines for writing code.
Analyze code: To study code for optimization and error detection.
Perform code review: To evaluate and provide feedback on code quality.
Schedule a build: To set up a plan for compiling code at regular intervals.
Prepare release notes: To document changes and updates for a software release.
Create a prototype: To develop a preliminary version of a program.
Develop a module: To build a self-contained component of a software system.
Write pseudocode: To outline code logic using plain language.
Coding and development
Perform integration testing: To test how different components work together.
Implement data structures: To organize and store data efficiently.
Use version control: To manage code changes and track history.
Collaborate on a project: To work together with other developers on a software project.
Deploy to production: To launch a final version of a program for users.
Implement design patterns: To use best practices for solving common problems.
Set up continuous integration: To automate testing and deployment processes.
Perform regression testing: To verify that changes do not break existing functionality.
Implement a REST API: To create an interface for communication between systems.
Follow agile methodologies: To use iterative and flexible approaches for software
development.
Implement a database schema: To define the structure of a database.
Perform a code audit: To evaluate code for security and compliance.
Coding and development
Perform load testing: To evaluate system performance under heavy usage.
Implement security protocols: To protect applications from unauthorized access.
Write SQL queries: To retrieve and manipulate data in a database.
Conduct a code walkthrough: To review code with team members for feedback.
Implement unit testing: To verify the functionality of individual code units.
Use containerization tools: To package applications for deployment.
Conduct a sprint review: To assess progress and plan future work.
Use a task tracker: To manage tasks and project milestones.
Follow the development roadmap: To adhere to planned project timelines.
Thanks!
