Review your notes¶
Either discuss with peers in class or on the GitHub (asynch) discuss commonalities in your IDE notes.
In person¶
What different tasks did all of you use an IDE for?
What features of an IDE did you all use?
Which features were used but not very much?
Share the most helpful IDE feature you use?
Update your individual IDE notes with 1-2 things you learned from your peers.
Asynchronous¶
Update your individual IDE notes in your KWL repo with links to your post and replies.
Learn more¶
In person¶
In class with your peers you can divide these up and read one and then share key points with others.
With your group, build a large list of IDE attributes or features that would be important, and make a table of how would you evaluate attribute? Which ones would you evaluate by just if it exists or not? Which ones would you evaluate in different degrees, what attributes of them would you evaluate?
Discuss with your group how you would rank them. You do not all have to agree on a final ranking, but notice the differences.
Asynchronous¶
After reading the above, also read at least 3 different articles about the “best IDE” for your favorite language or for multiple languages.
Notice what IDE attributes or features the authors think is important, and how they evaluate each criterion. Which ones are evaluted as present/missing? Which ones are evaluated in more detail.
In your experience report summarize what you found the most important criteria to be and if you personally agree or not.
Experience Reports¶
Answer the questions in your experience report
Prepare for Next Class¶
Think about things you have learned in this class and how they relate to using abstraction. Reflect on what you have found most/least valuable and interesting throughout the semester.
Post bullet points on your prepare issue.
Badges¶
Review the notes from today
Try a new IDE and review it in newide.md. Your review should be 3 secictions: Summary, Evaluation, and Reflection. Summary should be 1-3 sentences of your conclusions. Evaluation should be a detailed evaluation according to your group’s criteria and one other group’s criteria. In Reflection, reflect on your experience: What is easy? hard? What could you apply from the ones you already use? Were there features you had trouble finding?
Review the notes from today The first two tasks are the practice task, the thirds is a pre-approved explore badge. Hover it on your issue to create an independent issue to track it. Title the new issue
Explore: IDE. On the explore badge, when it is ready for submission, request a review from Dr. Brown.In bestide.md, compare two IDEs using your group’s table from class, to evaluate each of them. Your review should have an introduction that justifies the ranking and defines the criteria, a section describing each IDE with respect to all of the criteria and your overall experience with that IDE, and a conclusion that explains which of the 3 is the best based on your evaluation.
Configure your VS Code preferences to your github account. add settingssync.md with a description of what settings you customized and synced and reflect on why this is an important feature and what prerequisites to it might be.
(explore badge opportunity) Create a small repo owned by compsys named
ide-USERNAMEwhereUSERNAMEis your gh username with some example code, a vscode/codespace devcontainer file that installs CodeTour and your favorite extension(s). Write a CodeTour that walks someone through using your favorite extension to do something with the code. The example code can be any language, can be very simple, can even have a bug in it if that helps your example. You can use an-IDE integrated LLM (eg GitHub Co-pilot, not the chat version) to generate some code for this purpose if you do not have some available to you already, but you cannot share solutions to a course assignment without that instructor’s permission.