In general I'd expect the backlash from an unsatisfactory daily report to be low, there's a lot of opportunity to coach you and it lets your supervisor coach yo

In general I'd expect the backlash from an unsatisfactory daily report to be low, there's a lot of opportunity to coach you and it lets your supervisor coach you/steer you if you've developed an inconsistency. It's also an opportunity to get domain specific knowledge of pitfall you might experience integrating with an existing system. I think that deliberately making a to-be-scrapped system just to generate some work-done for the report is a waste of your time and you'd be better just making the real progress you can within the day and then reporting on how it's going/what (if anything) is stopping you from making progress; in general I don't think that tasks which take more than a day are expected to be complete. The report is really about making sure that you're not sitting there unable to make any progress for days/weeks/months at a time resulting in an unexpected failure to deliver at the other end. HTH.