Small Things, Big Impact: What Developers Think They Can Ignore (But Shouldn’t)
Developers love big problems. We like scaling, architecture, and clever algorithms. We skip small things. We think they don’t matter. They do. Small things break pipelines. They waste time. They hurt careers.
I’m Ermenildo Valdez Castro, Jr. Call me Ernie. I worked at Google, Microsoft, Amazon, and Zulily. I’ve pushed code at 2 a.m. I’ve fixed outages at dawn. I learned the hard way that little things change everything. 🧭
Why small things matter for software developers
Small things add up. One missing test. One unclear comment. One poorly named variable. They slow teams. They hide bugs. They cost hours and confidence. Businesses notice. Your manager notices. Your career notices.
1) Documentation and README
Most devs skip writing docs. They think code is self-explanatory. It rarely is.
Anecdote: At Microsoft, I landed on a team with no README. The repo had a dozen configs. I wasted a day. I wrote a one-page README that saved two weeks of guesswork. That tiny file improved developer productivity.
Tip: Write a README. Explain how to run tests. State expected environment variables. Keep it short.
2) Tests and small edge cases
Tests catch small breaks before they become big outages. You can’t test everything. But test the odd cases.
Anecdote: At Amazon, a failing timezone conversion broke nightly reports. The code worked for most users. It failed for a city nobody tested. A single unit test would have saved us an on-call night.
Tip: Add tests for edge cases. Use CI. Flaky tests are worse than no tests. Fix flakiness fast.
3) Logging, metrics, and alerts
If you can’t see the problem, you can’t fix it. Logs should tell a story. Metrics should scream when things go wrong.
Anecdote: At Zulily, we had sparse logs. An order flow failed quietly. Customers lost money. We added structured logs and a simple counter metric. The next incident was visible and short.
Tip: Log context. Use structured logs. Add a few high-priority alerts.
4) Timezones, locales, and data formats
Dates and numbers are small details. They break billing and reports.
Anecdote: Once, I shipped UI code that assumed US date formats. An EU partner read 01/06 as June instead of January. It was embarrassing and costly.
Tip: Use ISO formats. Normalize data early.
5) Code style and small conventions
Style is boring. Style prevents arguments. It reduces friction in code review.
Anecdote: At Google, style guides made reviews faster. At a smaller shop, we debated tabs vs spaces for an hour. Don’t debate. Agree and document.
Tip: Use linters and formatters. Automate style checks in CI.
6) Communication and expectation setting
The soft stuff is not soft. Clear messages save time.
Anecdote: In Seattle winters, I worked remote between meetings. I learned to over-communicate status. A quick note saved a sprint.
Tip: Say what you’ll deliver. Say when you’re blocked. Use short updates.
7) Security basics and secrets
Security is not optional. Small mistakes leak production secrets.
Anecdote: Early in my career, I checked a private key into git by accident. I rotated keys at midnight. It cost me sleep and humility.
Tip: Use secret stores. Scan commits before pushing.
8) Accessibility and small UX details
Tiny UX details lock out users. Accessibility is a small investment with big returns.
Anecdote: I added alt text to images in a marketing widget. Sales thanked us. A small fix, big result.
Tip: Run a quick accessibility check. Label form fields. Test keyboard flow.
9) Local development ergonomics
If setup hurts, devs avoid changes. Long setups block contributions.
Anecdote: I once spent a day spinning up a dev environment. I automated setup the next morning. New hires started coding the same day.
Tip: Script setup. Containerize when possible. Keep it simple.
Closing: Small things build reputation and software
Small things show care. They show craft. They keep systems healthy. They keep your job easier.
If you want more trust, fix a small thing today. Write one test. Add one log. Create a README.
I’m Ernie Castro. I know the nights and early mornings. I know the cost of the tiny errors. Fix them. It’s work you can do.
Call to action: Share one small thing you fixed this week. Comment below. I read them. 😊