1. Go through each photo in this folder
2. Look at what is actually in it — the location, the subject, what I photographed
3. Don't use filenames or dates — I want the grouping based on what you see in the photo
4. Propose 2–3 ways to organise them into subfolders
5. Show me the structure before moving anything
On it — I'll go through each photo and look at what's actually in it.
I've looked at all 50 photos. Here are groups based on what's actually in the images:
| Folder | Photos | What I saw |
|---|---|---|
01-Rome-Colosseum/ | 8 | Exterior and interior of the Colosseum, Roman Forum visible |
02-Venice-Canals/ | 14 | Canals, gondolas, Rialto Bridge, narrow streets and bridges |
03-Florence-Duomo/ | 7 | Cathedral exterior, dome from various angles, Baptistery |
04-Cinque-Terre/ | 11 | Colourful cliff-side villages, coastal paths, sea views |
05-Food-and-Markets/ | 6 | Market stalls, pasta, gelato, trattoria meals |
06-Misc/ | 4 | Train stations, hotel rooms, maps and tickets |
Shall I move everything? I'll leave original filenames intact inside each folder.
Yes, move them. Also write a CSV with every photo's new path, capture date, and GPS location.
Done — 50 files moved, inventory written.
Read each file in this folder and understand what was actually discussed. Organise so that the top level separates by category of outcome — things the team decided, things noted as problems but not resolved, and planning conversations. Within each, create sub-folders by ongoing initiative or recurring topic — you decide what counts as a recurring thread based on what you find across the files.
I've read all 890 files. Here's how I've routed them:
meeting-notes/
├── Decisions-Made/ 234 files
│ ├── Product-Direction/ 67 files
│ ├── Technical/ 89 files
│ ├── Hiring/ 41 files
│ └── Process-and-Policy/ 37 files
├── Problems-Not-Resolved/ 67 files
│ ├── Infrastructure/ 35 files
│ ├── External-Dependencies/ 20 files
│ └── Team-Dynamics/ 12 files
└── Planning-Conversations/ 589 files
├── Sprint-Planning/ 201 files
├── 1-1-Meetings/ 166 files
├── Roadmap-Sessions/ 134 files
└── OKR-Reviews/ 88 files
Ready to move when you are. Original filenames preserved.
Read every file in this folder and understand what it actually is — a flight booking, a hotel, a meal, a car rental. Figure out what trips are represented across all of them based on dates and destinations. Create a folder for each trip named by destination and dates. Within each trip, organise by category and rename the files so they make sense for expense reporting.
I've read all 89 receipts. Here's the structure I found — 4 trips:
receipts/
├── NYC-2023-09-14/ 23 receipts
│ ├── Flights/ United SFO→JFK + return
│ ├── Hotels/ Marriott Times Square — 4 nights
│ ├── Meals/ 8 restaurant receipts
│ └── Transport/ Lyft, subway — 12 receipts
├── Chicago-2024-01-08/ 18 receipts
│ ├── Flights/ ...
│ ├── Hotels/ ...
│ └── Meals/ ...
├── London-2024-03-22/ 34 receipts
│ └── ...
└── Miami-2024-06-15/ 14 receipts
└── ...
Every file has been renamed to include date, vendor, and amount — e.g. 2023-09-14_United_SFO-JFK_$312.pdf. Flagged 7 receipts that could belong to either NYC or Chicago — want me to show you those before I move anything?
Read everything in this folder — every review, comparison note, and evaluation I've saved. I'm not giving you categories. Find what actually matters when choosing between these products and give me a table comparing them.
On it — I'll read each file to understand what it's actually evaluating.
I've read all 19 files. Here's what actually matters across all of them — and how the products compare on each dimension:
| Dimension | Uplift V2 | FlexiSpot E7 | Autonomous SmartDesk Pro |
|---|---|---|---|
| Stability at height 17 of 19 sources | ⭐⭐⭐⭐⭐ Best across all sources | ⭐⭐⭐⭐ Very stable | ⭐⭐⭐ Some wobble noted at max height |
| Motor noise | Quiet — consistent finding | Moderate, load-dependent | Moderate, similar to FlexiSpot |
| Weight capacity | 355 lbs | 275 lbs | 310 lbs |
| Warranty | 15 yr frame / 5 yr motor | 10 yr frame / 3 yr motor | 5 yr frame / 2 yr motor |
| Price range | $599–$799 | $499–$549 | $399–$449 |
The dimension every source agreed on: stability at standing height matters more than anything — it came up in 17 of 19 files. Strong consensus that the budget tier underperforms; the mid-tier is the clear sweet spot.
Help me organise the information from these job applicant resumes into tables that help me understand how each candidate matches up to the job description. Read the job description and the resumes in this folder. Figure out what criteria the JD is looking for, then pull the relevant information from each resume into a table — one table per candidate.
On it — I'll read the job description first to find the criteria, then pull the relevant information from each resume.
From the JD, I found six criteria the role focuses on. Here's what each resume actually says about each one:
Candidate 1
| JD criteria | What the resume says |
|---|---|
| Python / Go proficiency | 7 years Python (Django, FastAPI); 2 years Go — services at Stripe internship |
| Distributed systems at scale | Led monolith-to-microservices migration at Acme Co.; event-driven architecture, 50k req/s |
| Financial systems / compliance | 6-month contract at fintech client — payment reconciliation module |
| Team or technical leadership | Not mentioned |
| Communication and documentation | Engineering blog (12 posts); maintainer of open-source library, 2.3k GitHub stars |
| System design depth | Designed real-time trading system; architecture presented at internal tech talks |
Candidate 2
| JD criteria | What the resume says |
|---|---|
| Python / Go proficiency | 4 years Python (Flask, SQLAlchemy); Go not listed |
| Distributed systems at scale | Built data ingestion pipelines (Kafka, Spark); batch processing systems at DataCorp |
| Financial systems / compliance | 6 years at PayFlow Inc.; PCI-DSS certified; worked on fraud detection system |
| Team or technical leadership | Engineering manager for team of 5, 2 years; ran quarterly planning cycles |
| Communication and documentation | Two conference talks — PyCon 2022, FinTech Summit 2023 |
| System design depth | Designed payment reconciliation platform; led data warehouse migration |
The criteria above come from the JD. Each cell is pulled directly from the resume — nothing added or inferred.
Zip the organised folder as italy-trip-2024.zip.
Done.
📦 italy-trip-2024.zip — 1.4 GB, in your home folder. Ready to copy to an external drive or upload anywhere.
Create an HTML photo gallery I can open in a browser — one section per folder, thumbnail grid, captions from the CSV.
On it — I'll read the inventory CSV and build the gallery from it.
Opening in your browser. The gallery has:
- A home page with all 6 category cards and photo counts
- Per-folder pages with a responsive thumbnail grid
- Click-to-expand lightbox with capture date and GPS location
- Light / dark mode toggle
That's Organise → Display chained. The structure you built becomes something you can browse and share.