simojo / simon-jones.netlify.app Goto Github PK

SE12 - Very good in-depth summary of the chapter. I liked the two sections that pertain to antipatterns and testing public API. This really improved my knowledge of this chapter.

DB3 - Good use of the code segment to improve knowledge of the chapter and explanation of what it does. I agree with your point of assertions and user input I think it could be beneficial.

FB8 - I believe this blog post was also effective as you started with an effective summary of the work the was given in the article but then you moved into a meaningful reflection that gave your true thoughts on the matter which gave a greater level of insight onto different ways to think about this article.

SE8 - The great formatting of this article with quotations and code segments allows for a great summary of why you need effective rules in a software development team. The reflection was also very helpful as you were able to attach it to your project and show how this article could help you and the team In the future.

SE5: You cover the content of the chapter in depth. I liked the italics and the quotes that you used. I also appreciated the abundance of examples that you used, both general and personal. The list of key points helps lead the article to the conclusion. I appreciate your frankness in the conclusion; it shows that you are open and considerate of other people's struggles and hardships. The list at the end gives a clear idea of how this chapter applies to our work on chasten.

FB5: You adequately cover the content of the chapter. The code segments and examples pulled from the chapter help the reader understand the concepts being discussed. You provide an example of how we could implement grammar and fuzzing into our program and why it would be beneficial. I think you could have added more explanations for the examples, but overall the article is well-written

SE6: You did a good job of showing how in a managerial position you must be able to make life easier for your workers rather than managing them as individuals. Your analysis gave a deep insight into all the different aspects of being a great manager and applied it well to our case.

FB6: There was not as much information to go in-depth into in this article besides the summarization of grammar fuzzing. However, you summarised the content very well and made it clear what the goal was with this section, especially with the code segments.

SE4: I like your inclusion of the table, and I appreciate the note about the environment of our class/project. I think you've got a really clear read on the situation, especially when one takes into consideration workload from other classes. Your 'stop doing' action is a good point as well; it'd be better if we could utilize Discord's pin feature more, but it requires either the server owner or someone granted permissions by the server owner to have the power to do that.

FB4: I think you do a great job of picking which segments of code to focus on for a summary, and it fits in well with your precis as a whole. I admit to being a bit confused about your remarks regarding other languages not having an AST, since as far as I'm aware that's a fundamental part of every language, unless you were referring specifically to the accessibility of it? But that's just a confusion on my part. Your action items segment continues to be an effective element.

DB2: The language used here is very appropriate and helps move your article and ideas very well, also the use of italic and code segment help certain words pop. At the same time, I believe more effort could be put into the action items section as to where we could use this code.

SE11: The detail in this article is amazing as many concepts are explained in a very clean tone. The use of bullet points and quotes allows this article to be very nice to read. In comparison, your summary again lacks the style and content of the summary.

SE10: Breaking down the five major/biggest points into the list is an effective way of both displaying and highlighting that which is most important, especially as each has its own summary in its title. Your reflection on our work and how your own habits have changed is a good insight as well.

DB1: The points are well-condensed in your summary, and I agree with your point noting that the chapter was perhaps longer than entirely necessary.

SE3: You did a great job at laying out all of the main points from the article in a concise and clear manner, and make good points regarding criticism and incident reports.

FB3: Fuzzing is certainly a lot to try and figure out, and I agree that it would be to our benefit if several team members were able to take the time to study it and give it the time necessary to make effective fuzzing tests.

SE7: I think you do a great job of capturing the key points of management in your summary here. In your Action Items and Reflections section, I note that you mention "we are not in a stable position", but the other statements surrounding it seem to be contradicting that. Perhaps this note, if it is intentional, could be expanded on?

FB7: Much respect for making the calculation/evaluation of the O notation of the scaling of the simple grammar fuzzer. I think your insight into the scale not being a good fit for our current project is a good one, although I wonder at the possibility of scaling it down or perhaps using the ideas presented to help consider new perspectives with which to tackle testing, at least in subsections of the project.

I think you did an excellent job on this article. I appreciate that you linked to the chapter, as well as used quotation marks and italics to emphasize words and phrases. I also liked that you included a bulleted list at the end of the article. I think you explain everything well and adequately cover the chapter. My only recommendation would be to underline or bold the headings to make sure they stand out.

Very in-depth summary of the first two chapters!

Overall, the format and presentation of this blog are very sharp. Using code blocks, italics, bold, and bullet points gives the article emotion where needed and allows a reader to read otherwise incomprehensible topics. This is done exceptionally well in "SE2" where sentence topics are clearly differentiated with innovative structure allowing for complex software engineering topics such as Hyrum's Law and cost trade-offs to be explained simply.

That being said something I found potentially lacking in these blogs was a large reflection that more accurately showed your opinion or thoughts on what was being said in the article. For me, the summary is the time to explain what was said in a condensed format, but the reflection is a time to give your own thoughts on what these articles mean to you and how you can use the information given by the articles in your own work.