Fundamentals of English Grammar #1

That's a great textbook table of contents! It covers the fundamental tenses in English.

Here is a summary of the highlighted sections, with example sentences and key learning tips.

PRESENT TIME

ItemTopicExample Sentence(s)Learning Summary
1-1The simple present and the present progressiveSimple Present: The sun rises in the east. (Fact/Habit) / Present Progressive: She is studying for her exam right now. (Action in progress)Simple Present is for facts, habits, and routines. Present Progressive is for actions happening at the moment of speaking or temporary situations.
1-3Frequency adverbsI always drink coffee in the morning. / He is never late for class.These adverbs (always, usually, often, sometimes, rarely, never) describe how often an action occurs. Their position is key: before the main verb, but after the verb to be or auxiliary verbs.
1-4, 1-5Final -s / Spelling of final -s/-esHe reads a book. / She watches TV.The final -s (or -es) is added to the main verb only in the Simple Present tense when the subject is he, she, or it (third-person singular). Pay attention to spelling rules (e.g., adding -es after s, sh, ch, x, z).
1-6Non-action verbsI know the answer. (NOT: I am knowing the answer.)Non-action (stative) verbs (know, believe, love, need, own, etc.) express states or feelings, not actions, and are almost never used in progressive (continuous) tenses.

PAST TIME

ItemTopicExample Sentence(s)Learning Summary
2-1, 2-2Expressing past time: the simple past / Forms of the simple past: regular verbsI walked to work yesterday. / They finished the project last week.The Simple Past is for completed actions at a specific time in the past. Regular verbs form the past by adding -ed.
2-6, 2-7The principal parts of a verb / Irregular verbs: a reference listPrincipal Parts: go - went - gone / Simple Past Example: She went to the store an hour ago.You must memorize the Simple Past form of irregular verbs (e.g., go/went, see/saw, eat/ate), as they do not follow the simple -ed rule.
2-8, 2-9The simple past and the past progressive / Forms of the past progressivePast Progressive: I was studying when the phone rang. / Simple Past: The phone rang.The Past Progressive (was/were + -ing) is for an ongoing action in the past. It is often used to set the scene or to show an ongoing action that was interrupted by a shorter Simple Past action.
2-11Expressing past habit: used toI used to play soccer every weekend, but now I don't.Used to + base form of the verb expresses a habit or a situation that existed regularly in the past but does not exist now.

FUTURE TIME

ItemTopicExample Sentence(s)Learning Summary
3-1Expressing future time: be going to and willBe going to: I am going to visit my aunt next month. (Pre-planned) / Will: It's cold. I think I will close the window. (Spontaneous decision/Prediction)Use be going to for plans, intentions, or predictions based on present evidence. Use will for spontaneous decisions, promises, offers, or general predictions (often with I think).
3-5Be going to vs. willLook at those dark clouds. It's going to rain. (Evidence) / Don't worry, I will help you with your homework. (Promise)This distinction is crucial. Going to is for plans and evidence; will is for sudden decisions, promises, and opinions about the future.
3-7, 3-8Using the present progressive and the simple present to express future timePresent Progressive: I am meeting a client tomorrow afternoon. (Fixed arrangement) / Simple Present: The bus leaves at 3:00 PM. (Fixed schedule/timetable)These present tenses can also talk about the future: Present Progressive for personal, confirmed arrangements, and Simple Present for schedules (like trains, movies, or school terms).

This summary should provide a clear starting point for studying these core English grammar topics! Which section looks the most interesting to you?

댓글

댓글 쓰기

이 블로그의 인기 게시물

Gradle multi-module project

In a Gradle multi-module project , it's common to define shared dependencies in the parent project (root project) to avoid duplication across modules. This structure allows child modules to inherit or access those dependencies. Below are some best practices on how to correctly share dependencies between parent and child modules in a multi-module Gradle project . Project Structure Example multi-module-project/ ├── build .gradle .kts (Parent/root project) ├── settings .gradle .kts ├── module-a/ │ └── build .gradle .kts ├── module-b/ │ └── build .gradle .kts Step 1: Configure settings.gradle.kts In a multi-module project, the settings.gradle.kts file should declare all the modules that are part of the build. // settings.gradle.kts rootProject .name = "multi-module-project" // Include child modules include ( "module-a" , "module-b" ) Step 2: Define Shared Dependencies in the Parent build.gradle.kts The root build.gradle.kts ca...
자세한 내용 보기

Boilerplate for typescript server programing

Here are some recommended boilerplates and frameworks for TypeScript server programming, depending on your requirements: 1. NestJS (Highly Recommended for Enterprise-Grade Applications) NestJS is a progressive Node.js framework built with TypeScript. It provides an opinionated structure and is excellent for building scalable and maintainable server-side applications. Features : Dependency injection Modular architecture Built-in support for WebSockets, GraphQL, REST APIs Easy integration with tools like Swagger, TypeORM, and Mongoose Getting Started : Install Nest CLI: npm i -g @nestjs/cli nest new project-name Boilerplate is automatically generated with ready-to-use configurations for controllers, services, and modules. Website : https://nestjs.com/ 2. Express with TypeScript Express.js is lightweight and minimal, making it ideal for developers who prefer flexibility over opinionated frameworks. Boilerplate : You can start with an official or community-maintai...
자세한 내용 보기

HTML Inline divisions at one row by Tailwind

To arrange a **variable number of inline ` ` elements in a row** using **Tailwind CSS**, you can utilize several approaches, depending on your layout needs. Below are some common methods to align multiple divs in a row: ### 1. **Using Flexbox (`flex`)** Tailwind's `flex` utilities provide a straightforward way to align a variable number of ` ` elements inline in a row. Flexbox will ensure that they stay in a row, wrapping if necessary. #### **Example Using Flexbox** ```html Div 1 Div 2 Div 3 Div 4 ``` #### **Explanation:** - `flex`: Puts the child elements (the divs) in a row. - `flex-wrap`: Ensures that if there are too many divs to fit in one row, they will wrap to the next line. - `space-x-4`: Adds horizontal spacing between the divs (adjust as needed). ### 2. **Using Grid (`grid`)** Another way to align divs in a row is by using Tailwind's `grid` utilities. Grid layouts are very flexible and allow control over the number of columns. #### **Example Using ...
자세한 내용 보기

How to split a list into chunks of 100 items in JavaScript, 자바스크립트 리스트 쪼개기

To split a list into chunks of 100 items in JavaScript, you can create a function that loops through the list and slices it into smaller subarrays of size 100. Here’s how you can do it: Example Code: function splitListBy100( array ) { const chunkSize = 100 ; const result = []; for ( let i = 0 ; i < array .length; i += chunkSize) { result .push( array .slice(i, i + chunkSize)); } return result ; } // Example usage: const myArray = [... Array ( 350 ).keys()]; // Creating an array of numbers from 0 to 349 const chunks = splitListBy100(myArray); console.log(chunks); Explanation: chunkSize : Defines the size of each chunk, which in this case is 100. for loop : Iterates over the array, incrementing the index by 100 each time. array.slice(i, i + chunkSize) : Extracts a chunk from the array starting from index i and ending at i + chunkSize . result.push() : Adds the chunk to the result array. The function returns an array of arrays (...
자세한 내용 보기

CDPEvents in puppeteer

In Puppeteer , CDPEvents refers to events emitted by the Chrome DevTools Protocol (CDP) . Puppeteer leverages CDP to interact with and control a Chromium-based browser. CDP provides detailed, low-level access to browser internals, such as network traffic, console logs, page lifecycle events, and more. You can listen to these CDP events through Puppeteer’s API to monitor or intercept browser activity. How to Listen for CDP Events in Puppeteer Enable the Required CDP Domain: Some events require enabling a particular domain (e.g., 'Network' , 'Page' , 'Runtime' ). Use page._client() to Access the CDP Session: Although it’s a bit lower-level, Puppeteer allows access to DevTools through the page._client() API. Example: Listening for Network Requests This example demonstrates how to intercept and log network requests using CDP. const puppeteer = require( 'puppeteer' ); ( async () => { const browser = await puppeteer.launch({ headless...
자세한 내용 보기

가속도 & 속도

F = ma 에서 가속도(( a ))는 속도(( v ))의 시간(( t ))에 대한 미분이므로, 수식으로 표현하면 다음과 같습니다. \[a = \frac{dv}{dt}\] 또한, 속도(( v ))는 위치(( x ))의 시간 미분이므로, 이를 포함하여 가속도를 표현하면 \[a = \frac{d}{dt} \left( \frac{dx}{dt} \right) = \frac{d^2 x}{dt^2}\] 즉, 가속도는 위치의 이阶 미분(두 번째 미분)입니다.
자세한 내용 보기

Sparse encoder

A Sparse Encoder refers to a variant of neural network architectures where sparsity is introduced in the encoding process. This can mean either: Sparse Input Representations : The input features to the encoder are sparse (many values are zero). Sparse Output Representations : The encoder is designed to produce sparse outputs where most of the encoded feature values are zero. Sparse encoders are often used to improve model interpretability, efficiency, and generalization. They can be applied in various contexts, including traditional neural networks, autoencoders, and even transformer-based models. Key Characteristics of Sparse Encoders Sparsity in Representations : The model learns a feature representation where only a subset of neurons is active for a given input. This mimics how biological neurons operate, promoting interpretability and reducing noise in representations. Reduced Computational Cost : Sparse operations often result in lower computational overhead since...
자세한 내용 보기

How to checkout branch of remote git, 깃 리모트 브랜치 체크아웃

To check out a branch from a remote Git repository, you can follow these steps: 1. Fetch the remote branches First, ensure that your local repository is aware of the remote branches by using git fetch . This updates your local references to the remote branches. git fetch origin 2. Check out the remote branch Once the remote branches are fetched, you can check out the desired branch using git checkout -b and specifying the remote branch. Command: git checkout -b < local -branch- name > origin/<remote-branch- name > Explanation: <local-branch-name> : The name you want to give to your local branch. origin/<remote-branch-name> : Refers to the branch on the remote called origin (which is the default name for the main remote repository) and the branch you want to check out. Example: If the remote branch is called feature-branch and you want to create a local branch with the same name, you would run: git checkout -b feature -branch origin / feature -...
자세한 내용 보기

Declaration of custom object or type in Node.js

In Node.js, when you want to assign one object to another that is declared by a custom type or class, you typically need to ensure compatibility between the source object's structure and the target class's expectations. Here's a breakdown: Scenario 1: Assigning Plain Objects to Class Instances If you have a custom class and want to assign properties from a plain object to an instance of that class, you can use one of the following methods: Example: class CustomType { constructor (name, age) { this .name = name; this .age = age; } } // Plain object const plainObject = { name : "John" , age : 30 }; // Assign using Object.assign() const customInstance = new CustomType(); Object .assign(customInstance, plainObject); console .log(customInstance instanceof CustomType); // true console .log(customInstance); // CustomType { name: 'John', age: 30 } Scenario 2: Using a Constructor You can modify your class to accept an object in the c...
자세한 내용 보기

To switch to a specific tag in a Git repository

To switch to a specific tag in a Git repository, you can use the git checkout or git switch command. Here's how you can do it: 1. List Available Tags First, you may want to see a list of all available tags in the repository: git tag 2. Checkout a Specific Tag Once you know the tag you want to switch to, you can use either git checkout or git switch (if you're using a newer version of Git, which recommends git switch for checking out branches). Using git checkout : git checkout <tag- name > Using git switch (recommended for newer versions of Git): git switch -- detach <tag- name > The --detach flag is necessary because tags are not branches; they are just pointers to specific commits. Using --detach makes your HEAD point to the tag without modifying any branch. 3. Verify the Checkout After switching to the tag, verify that you're on the correct commit: git status This will show the tag you're currently on (you'll see somethi...
자세한 내용 보기