Method matters more than the answer
In engineering exams the marks are in the working. An answer that materialises with no derivation earns almost nothing, and a derivation in a convention your course never used earns a puzzled look and a lower mark. What you need is not the solution — it is the solution *as your module would write it*.
Because your slides and problem sheets sit in the space, the homework solver follows the approach your material uses. Ask it to solve by mesh analysis and it does mesh analysis. Ask it to use the method from lecture six and, with lecture six uploaded, it will.
The single best way to use it
Not "solve this". Instead: photograph your own attempt and ask it to find the first line that's wrong. It stops at the error rather than steamrolling to the answer, which means you keep the part of the problem you had already solved, and you learn precisely the thing you didn't know. This is the difference between a tool that helps and a tool that quietly replaces the learning with a completed problem sheet.
Also good at
- Reading circuit diagrams, free-body diagrams and schematics from a photo, including hand-drawn ones.
- Keeping mathematical notation as mathematics rather than mangling it into plain text.
- Deep-explain mode — a stronger model, slower, for the derivation you genuinely cannot follow.
- Turning a failed problem into a card, so the concept you missed comes back before the exam rather than after it.
- Lab reports — interrogating your own method and results, not writing them for you.