Tiếp theoHướng dẫn tiếp theo
Cách viết tập lệnh bảng tính và macro bằng AI
kỹ thuật
HƯỚNG DẪN KỸ THUẬT
Writing regular expressions with AI means describing the text pattern you want in plain words, getting a regex back with a piece-by-piece explanation, and testing it against real and tricky examples before using it.
Nghe hướng dẫn nàyAI thuật lại · ~3 min
It matters because regex is compact and hard to read, so AI saves real time, but a pattern that looks right can still match too much or too little.
A regular expression is a mini-language for describing text patterns. \d matches a digit, + means one or more, [A-Z] is a character class, ^ and $ anchor to the start and end, and parentheses create groups you can capture. Regex works in almost every programming language and in text editors, command-line tools such as grep, and spreadsheet functions. It is also notoriously hard to read, which is exactly why AI helps: you describe the pattern in words and ask for both the regex and a token-by-token explanation. The quality of your description decides the quality of the result. Say what should match and what should not, give three to five positive examples and several negative ones, and name the flavor or engine: JavaScript, Python's re module, PCRE, Java, .NET, POSIX grep, or Google Sheets, which uses RE2. Flavors differ. Lookbehind support, named group syntax and Unicode handling vary, and RE2 deliberately leaves out backreferences and lookaround so that it can guarantee matching in linear time. Then test. Paste the pattern into a tester such as regex101, which highlights matches and explains each part, and run it on edge cases: empty strings, extra whitespace, very long inputs, non-English characters and near-misses. You can ask the AI to generate tricky test strings too, but check them yourself. Common misconceptions include thinking that a regex that matches your examples is correct (it may also match things you never considered), that email or URL validation needs one perfect regex (the full email address standard is very complex, and most teams use a simple sanity check plus a confirmation email), and that regex suits every parsing job. HTML, JSON and nested structures are better handled by a real parser.
A support team lead asks for a pattern that finds order numbers like "ORD-2024-00417" in email text, then tests it on "ORD-24-1" and "word-2024-00417" to confirm both are rejected.
A developer asks for a JavaScript regex that validates US ZIP codes in 5-digit or ZIP+4 form, anchored with ^ and $ so that "123456" fails.
A writer cleaning a manuscript in a code editor asks for a find-and-replace regex that collapses double spaces after periods into single spaces, using a capture group in the replacement.
A system administrator asks for a Python regex with named groups to extract the timestamp, log level and message from application log lines, then checks it on lines with long messages and missing fields.
AI assistants are now built into many code editors, so generating a regex in place is becoming routine. What will not change is that regex behavior depends on the engine and the input, so testing remains the responsibility of whoever ships the pattern. Tools that pair generation with suggested test cases and warnings about risky constructs are a natural direction. For many tasks, a good assistant may also recommend a clearer alternative, such as a small parsing function or a library built for dates or emails, which is often easier to maintain than a clever one-line pattern.
Bản tin miễn phí
Ba câu chuyện AI đã được xác minh vào mỗi buổi sáng các ngày trong tuần, được viết bằng tiếng Anh đơn giản. Miễn phí mãi mãi, không có quảng cáo.
Một email mỗi ngày trong tuần. Hủy đăng ký trong một cú nhấp chuột. Chúng tôi không bao giờ bán hoặc chia sẻ địa chỉ của bạn.
Tự kiểm tra
Phản hồi tức thì về mọi câu trả lời và chứng chỉ có thể chia sẻ với ID có thể xác minh sau khi bạn vượt qua khóa học.
Hỗ trợ giáo dục AI miễn phí. AI Understanding là tổ chức phi lợi nhuận 501(c)(3) — không bao giờ có quảng cáo, không có tường phí. Hãy quyên góp
Writing regular expressions with AI means describing the text pattern you want in plain words, getting a regex back with a piece-by-piece explanation, and testing it against real and tricky examples before using it. It matters because regex is compact and hard to read, so AI saves real time, but a pattern that looks right can still match too much or too little.
Without ^ and $ (or word boundaries), the pattern only needs five digits somewhere in the text, so longer invalid inputs still pass.
Positive and negative examples define the boundary of the pattern, and naming the flavor avoids syntax your engine does not support.
RE2 omits backreferences and lookaround so it can guarantee linear-time matching, which means some patterns from other flavors will not work there.
Backtracking engines can try an explosive number of combinations with nested quantifiers. Attackers can exploit this in a denial of service called ReDoS.
Greedy .* consumes as much as possible and then backs off only enough to find the final >, so it spans both tags. The lazy version <.*?> matches just "<a>".
Tiếp tục học hỏi
Đã chọn thêm hướng dẫn cho chủ đề này
Tiếp theoHướng dẫn tiếp theo
Cách viết tập lệnh bảng tính và macro bằng AI
kỹ thuật