Developer kit: the small jobs around the code
Small daily jobs: colours, JSON, diffs.
Most of a developer's tools live in the editor. The rest live in a long row of browser tabs: a colour converter, a JSON formatter, a diff site, a regex tester, a timestamp decoder. They are small, they are used all day, and they are never in the same place twice. This kit puts them next to a to-do list and a note, so what you tested and what you decided do not disappear when you close the tab.
The work it covers is the work around the feature, not the feature. Taking a colour from a design and turning it into an ARGB value for the app. Making an API response readable to find why a field is null. Comparing two configs to see why staging works and production does not. Writing a bug report that another person can act on. Checking a release for the differences nobody compared. None of these are hard, and each is easy to do badly in a hurry.
The kit is built for people who do these things every day, which is why the first template is a scratchpad you keep open, not a one-off. It is also built to be quick: every tool takes pasted text and answers on the same screen, and ⌘K searches the tools, your jobs, tasks and files together.
The board
The Space has 3 columns, Inbox, Doing, Done. A job moves from left to right, and the last column counts as done.
Inbox
Everything that arrives goes here first: a bug someone mentioned, a config to check, a payload to look at. Do not sort at this stage. One line is enough.
Doing
The one or two things you are working on now. A short Doing column is the point: it shows you when you have started too many things at once.
Done
Finished work, with the result kept in the note: the report you filed, the diff you found, the checklist as it was ticked. Jobs in Done are a log, and a log is useful the next time the same problem comes back.
Job templates
Each template is a ready list of tasks. Open one to read why every step is there, or add it to your Space from its page.
- Daily scratchpad – Colours, JSON, diffs and regexes in one place, with the useful ones kept in a note. 5 tasks, 4 with a tool.
- Bug report – Steps, log, config diff and a small screenshot, ready to paste into the tracker. 6 tasks, 4 with a tool.
- Release check – A short checklist plus a diff of the config that changes between environments. 6 tasks, 3 with a tool.
- JSON to CSV for a sheet – Turn an API response into rows someone can open in a spreadsheet. 5 tasks, 2 with a tool.
Tools in this kit
The tools in this kit take text or a small file and give an answer. They run locally, so a pasted payload is not sent to anyone, though you should still keep real secrets out of any scratch space.
- Color Picker – Reads a colour from an image and shows it as HEX, RGB, RGBA and ARGB, the form Android code uses.
- JSON Formatter – Formats, validates and minifies JSON, with sorted keys and your choice of indentation.
- JSON to CSV Converter – Converts a JSON array to CSV and back, with the delimiter and header options.
- Compare Text – Compares two texts line by line, side by side or inline, with options to ignore whitespace and case.
- Regex Tester – Tests regular expressions live against your samples.
- JWT Decoder – Shows the header and claims of a token. Decoding is not the same as verifying.
- Timestamp Converter – Turns Unix time into readable dates, and the other way round.
- Image Compressor – Shrinks a screenshot so a tracker or chat accepts it.
A week with this kit
You start the week with a scratchpad job and keep the note open. A designer sends a screenshot, you pick the colour and the note now has the ARGB value and what it is for. Midweek, QA reports a login failure, and the bug report template collects the steps, the response, the decoded token and the config diff in one job, in the order a reader needs them.
On Friday you prepare a release with the release check. The config diff shows that a feature flag is on in staging and missing in production. That would have been a Saturday call. Instead it is a line in the note: "intended? no".
The point is not that these tools are special. It is that the result of each small job has somewhere to go, and the next time you need it, it is a search away.
Questions
Is it safe to paste real data?
The tools run in your browser and send nothing to a server, which you can confirm in the Network tab. Still, keep real credentials out of any scratch space; use placeholders.
Can I use it offline?
Once a page has loaded, the text tools work without a network. Tools that fetch a larger component, such as video, need to load it once.
Does it sync between my computers?
No. It stores data in one browser. Export a backup file and import it elsewhere when you need to move.
Where do the JSON, diff and regex tools live without the kit?
Each has its own page under Tools. The kit just keeps them together with a note and a checklist.
Other kits
- Send & submit – Fix a file, then send or submit it.
- Design & craft – Logos to vector, colour palettes.