The information presented was overall good and entertainingly presented. The material itself was a bit C-centric and UNIX-centric, and assumed a lot of background knowledge about C and operating system design. It would have been better to actually explain the necessary background rather than assuming that the listener already knew it. I can imagine some students (especially those that don't know C or UNIX administration) being quite confused and frustrated. Also, some of the code examples given were needlessly complex, and I think the time spent explaining them in detail could have been better used covering other topics.

The quizzes were sometimes quite frustrating, not so much because the information that they were testing was difficult, but because many of these questions were quite misleading due to poor, ambiguous or imprecise phrasing of questions and answers. I wouldn't have worried about this much except for Coursera's annoying 2-time limit for quiz retakes before a mandatory 8-hour wait. In some cases, having more knowledge actually made it harder to answer these questions correctly, since knowing that the "correct" answer was technically wrong and thus hard to distinguish from "wrong" answers could be a hindrance.

With these concerns noted, I did find the course valuable, and I think many people will learn useful skills from it.

l feel like the instructor's presenting content from the past quite a bit. l'd love to see the course content updated or applied practically to real world modern applications. A lot of the content seemed theoretical. While it's realistic to, 'program defensively', the content really doesn't hit home unless you're able to demonstrate exploitation. Modern day attacks are based around APIs and Stacks and while the material is more relevant to the C or C++ programmer, it would of been good to actually see the attacks talked about executed. We all know we have to program robustly or defensively, but show us what could happen if we don't. Sure smashing the stack for fun and profit is a great read, but try modernizing your content for the relevant generation taking the course on this platform. Found the overall course content pretty dry.

I felt the scope of this course is too narrow and focussed mainly one a few examples in C code. I would've got more out of it and found it more interesting if the scope was broader and the examples were a higher level, perhaps written in pseudo-code.

Very good material to understand the concepts.

Kindly include the latest technologies as well like Javascript.

Good introduction of fundamentals. Basic concepts are very well explained. Practices classes are less useful as there are some missing explanations/in-depth analysis to catch the whole picture.

Matt Bishop is an excellent Secure Coding Trainer. I enjoyed the sessions all the way and it was totally engaging with practical examples.

Good introduction, at times the explanations are a bit dry and lengthy. A couple more real world stories would spice things up and make principles more memorable.

The course was an exceptional one. And helped me to lot to understand what Robust and Secure coding really means. Thank you so much tutor.

good information and presentation.

I suggest updating the coding example source to include a main file and integrate with MS Studio.

Very interesting course! The teacher is very clear and provides clear and useful samples! For sure I recommend it!

It is a good course to take. It gives you a good lecture about what you should take into account when coding

Nice course for secure coding.

Learnt how the code should be and how the code should not be.

Clear and fast point of view from the security perspective

Good in general. More code examples would be better.

Very good overview of Secure Coding principles!

Course content is really good, well explained.

Good Foundational Learning for secure coding.

I learned a lot, Thanks very much.

Very good videos

good learning

Great course!

Thanks a lot

good

Good

The course provides good insights in secure coding and robust programming. However, I think there should more than 10 questions for each module for assesment.