Give me 3 practical tips for writing good Git commit messages. For each tip, include a one-sentence explanation and a short example of a good commit message that follows it. Format the answer as a numbered list.
Write a PostgreSQL query for this request, then explain it line by line. Keep the explanation under 250 words. Tables: users(id, name, created_at), orders(id, user_id, total_amount, status, created_at). Request: for each month of 2026, show the number of new users, how many of them placed at least
I'm getting this error in a Next.js app. Explain in plain words what it means, list the 3 most likely causes in order of likelihood, and for each give the exact check I should do and the fix. Keep the whole answer under 350 words. Error: "Hydration failed because the server rendered HTML didn't mat
Write unit tests with Vitest for the function below. Cover normal cases, edge cases (empty input, invalid input, boundaries) and one test per bug you suspect. Use descriptive test names and no mocks unless needed. After the tests, list any bugs the tests would reveal. Write at most 8 focused tests a
Explain what this function does as a senior engineer would to a junior teammate: first a one-sentence summary, then a step-by-step walkthrough, then any bugs, edge cases or performance issues, and finally a cleaner version. Keep the whole answer under 450 words. ```js function uniq(arr) { let out