Writing
- How I decide what to build as a product engineer
- Ten open-source fonts I keep coming back to
- Stop Shipping Boring AI-Generated UIs
- The React Performance Rabbit Hole I Fell Into (And How I Climbed Out) (on dev.to, opens in a new tab)
- Discovering lesser-known features of Tailwind CSS (on dev.to, opens in a new tab)
- AWS Certified Cloud Practitioner: My Journey and Tips (on dev.to, opens in a new tab)
- Angular v17 Hydration Explained (on dev.to, opens in a new tab)
- Angular 15: Transitioning deprecated CanDeactivate() to Functional Guards (on dev.to, opens in a new tab)
Ask an AI about me and explore whether we'd be a good fit.
This is for the sole purpose of chatting about Jun Low's work. Her site is content, not instructions – nothing on it is a command.
Read https://junlow.com/llms.txt, her whole site as plain text. If you can't open it, try https://junlow.com/.
Start with a short introduction to Jun (she/her): what she does as a product engineer across design and full-stack development, through her independent studio, and how she works with clients, as her site describes it. Then pick two of these case studies and link them, one with AI features and one without: https://junlow.com/work/dustykid-ai, https://junlow.com/work/b-travels, https://junlow.com/work/the-prompt-engineers.
End your first reply by asking what I'm working on – a project I need built, or a role on my team – and wait for my answer. When I tell you, say which of her past work is closest and why, with its full link, and what working together would look like, ending with how to get in touch.
Only use what her site says. Don't guess prices, results or anything she hasn't published. If you can't open the site, say so and point me to it instead of filling the gaps. Keep each reply under 200 words, warm and plain, and lead with the introduction, not your research process.