Practical guides on AI, data, and digital access

A chatbot is a program you type to in plain language. You ask a question, the program answers in words, and you can keep the conversation going by asking follow-ups. The response is not a fact from a library. It is a prediction of what a helpful answer looks like based on patterns the program learned from a very large amount of text. That difference matters. Treat every answer as a first draft that a person still has to check.

Three free tools worth trying on a shared laptop or an older phone: ChatGPT at chat.openai.com, Google Gemini at gemini.google.com, and Microsoft Copilot at copilot.microsoft.com. All three work in a normal web browser. None of them require you to install anything. If your connection is slow, close other tabs and let the answer finish loading before you type again.

A useful prompt tells the tool who is asking, what you want, and any constraints. Instead of "help me write a letter," try "I am a parent in Cali. Write a short message in Spanish to my child's school asking for a meeting about a math grade. Keep it under 120 words and polite." The extra sentence changes the output more than most people expect.

Here is one worked example. Say a school sends home a notice in English about a schedule change. Paste the text into the chatbot and write: "Translate this into Spanish for a parent. Keep the meaning exact and mark any part where I should ask the school to clarify." Read what comes back next to the original. If a date or room number looks wrong, ask the tool to check that specific line, and then confirm with the school before you rely on it.

Another common use is drafting a message. If you are applying for a job at a bakery and want a short WhatsApp introduction, describe the job, your experience, and the tone you want. Ask for two versions. Pick the one that sounds like you and edit any word that does not.

Most charts you see online are either bar charts or line charts. A bar chart compares separate things at one moment. Number of students in each grade, for example, or votes for each candidate. A line chart shows how one thing changes over time. Bus arrivals per hour across a week is a line chart. If you try to read a bar chart as a trend, you will see a pattern that is not there.

Every chart has two axes. The horizontal axis at the bottom usually shows what is being compared or the time period. The vertical axis on the left shows the quantity. Before you look at the shape of the bars or the line, read the axis labels and the units. A chart with no unit on the vertical axis is telling you nothing, no matter how dramatic it looks.

Scale is where charts most often mislead. A vertical axis that starts at 40 instead of 0 will turn a small change into a cliff. If the axis is broken, the chart should mark that break clearly with a jagged line. When it does not, assume the difference is smaller than it appears. Also check whether the axis is linear or logarithmic. On a logarithmic axis each step is a multiplication, not an addition, and a straight line can hide very fast growth.

Here is a worked example using neighborhood data. Suppose the local transit office publishes a bar chart of bus frequency on Route 4 by day of the week. Monday shows 22 buses, Saturday shows 8. The bars for Saturday and Sunday are noticeably shorter. That is the story: weekend service is roughly a third of weekday service. Now check the axis. If it starts at 5 rather than 0, the drop looks even sharper than it is. Redraw the numbers in your head starting from 0 and the picture changes.

Two questions to ask of any chart before you share it. Where did the numbers come from, and does the person who made the chart benefit from you reading it a certain way.

A strong password is long, not clever. Sixteen random characters beat a short password with symbols mixed in. The easiest way to do this without memorizing is a password manager. Bitwarden has a free tier that works on a phone and on a computer. You remember one master password and the app fills in the rest. Write the master password down on paper and keep it somewhere only you can reach.

Turn on two-factor authentication on your email first, then on any account that holds money or personal records. Two-factor means that after your password, the service asks for a second code. Use an authenticator app such as Google Authenticator or Aegis rather than text messages when the site offers a choice. A phone number can be transferred to another SIM by someone who convinces your phone company they are you.

AI chatbots are useful, and they also keep records of what you type. Do not paste your national ID number, bank details, medical results, or a full copy of a private contract into a chatbot. If you need help with a document, remove the names and numbers first, then ask your question about the general text. Assume that anything you send to a free tool could be reviewed later by a person on the company's team, because in some cases it is.

Public wifi at a cafe or a bus terminal is fine for reading the news. It is not fine for banking or for signing into your primary email. If you have to do sensitive work away from home, use your phone's mobile data connection or turn on a reputable VPN app. Look for the small padlock in the address bar of the browser. If it is missing, the site is not encrypted and you should not enter a password.

Check your accounts every few months. Delete apps you no longer use. Go into the settings and revoke access for anything you do not recognize. Old accounts you have forgotten are the most common way personal data gets stolen years after you stopped caring about them.

Elected officials, principals, and utility managers listen more when you bring evidence than when you bring only opinion. The good news is that the evidence they respond to is often something you can gather with a notebook and a phone. You do not need statistical training to make a case. You need counts, dates, photographs, and a clear ask.

Start by writing down the specific problem in one sentence. Something like "The number 4 bus does not come after 7 pm on Sundays, and there is no sign posted about it." A sentence like this is easier to prove than a general complaint about bad transit. Now write down the outcome you want. Perhaps it is a posted schedule, or a request that the route be extended by two hours on Sundays.

Then collect evidence over a defined period. Two weeks is usually enough for a small case. Note the date, the time you arrived at the stop, the time the bus actually came, and how many other people were waiting. Take a photograph of the stop that shows there is no posted schedule. If other neighbors are willing, ask each of them to note one week of the same information. Ten people with two weeks of notes is stronger than one person with two months.

Present it simply. A one-page letter or email works better than a long report that nobody reads. Put the problem sentence at the top. Under it, a small table with the dates and times you collected. Attach two or three photographs. End with your ask in one sentence and a way to reach you. If you can, bring a printed copy to a public meeting or an office visit rather than sending only by email. A person holding a page is harder to ignore than a message in an inbox.

One more habit. Keep a copy of every submission and every response, with dates. When you go back a second or third time, the record of what you asked and what happened before is often the piece of evidence that moves the decision.