
Meet FridgeLister: what's cooking
Using your own codebase? Skip ahead to Git: commit to it. You may want to come back for the tasks.
If you're not using your own codebase, make sure that you have checked out FridgeLister, as shown in Path A: No install or Path B: Your own machine.
The story
FridgeLister started as a project idea in my software engineering course at a university. Older people who live alone often have a fridge full of things past their best, and someone who helps with the shopping. FridgeLister gives them one shared list: what's in the fridge, what to use soon, who's shopping, and by when.
It was built the way many apps are built today: by a coding agent, feature by feature, with a human reviewing. It works, it has tests, the tests pass. And it has the problems code grown this way tends to have. They're there on purpose. The course takes you to each of them.
To be open about it: the Git history is staged. I replayed how an app like this grows, one feature per commit over a summer, so the history behaves like a real one when module 5 digs into it.
Click around
Log in as each demo user (the password is password for both) and spend
five minutes. Add something to the fridge, mark something as used, look at
What to buy. The exercises make more sense when you know the app.
| Who | |
|---|---|
| Grandma Inge, who owns the Kitchen fridge | grandma@example.com |
| Mads, who does her shopping | helper@example.com |
Fridge a mess? composer setup resets the demo data.
No spoilers
- Don't go hunting for the problems. Each module shows you how to find a kind of problem with a tool or a number. That's the skill. Spotting them by reading first teaches you less.
- Don't let your agent "clean up" first. Asked to "improve the code", it will happily rewrite half of it, and the exercises are left with nothing to chew on. Give it the tasks below instead.
Tasks to give your agent
Several exercises say "give your agent a small, real task". On your own code, pick one from your backlog. On FridgeLister, use these, in any order:
- Fridge names must be between 3 and 40 characters, with a test.
- Let the owner rename a fridge.
- Let the owner remove a helper from a fridge.
- Show "use soon" next to the number of things on the overview page.
- On the fridges page, show how many days until each helper's shopping date.
- On the history page, add a filter for "used this week".
- Let a helper change their shopping date after they have accepted.
Watch how the agent works, not just whether the feature works. Where does it put the code? Does it reuse what's there? Does it run the tests? That's what the course is about.
Next: Git: commit to it.
Kept in this browser. Sign in to keep it on every device.