We found 11 results that contain "link"

 Teaching Commons: “an emergent conceptual space for exchange and community among faculty, students, and all others committed to learning as an essential activity of life in contemporary democratic society” (Huber and Hutchings, 2005, p.1) What Is the #iteachmsu Commons?    You teach MSU. We, the Academic Advancement Network, The Graduate School, and The Hub for Innovation in Learning and Technology, believe that a wide educator community (faculty, TAs, ULAs, instructional designers, academic advisors, et al.) makes learning happen across MSU. But, on such a large campus, it can be difficult to fully recognize and leverage this community’s teaching and learning innovations. To address this challenge, the #iteachmsu Commons provides an educator-driven space for sharing teaching resources, connecting across educator networks, and growing teaching practice. #iteachmsu Commons content may be discipline-specific or transdisciplinary, but will always be anchored in teaching competency areas. You will find blog posts, curated playlists, educator learning module pathways, and a campus-wide teaching and learning events calendar. We cultivate this commons across spaces. And through your engagement, we will continue to nurture a culture of teaching and learning across MSU and beyond. How Do I Contribute to the #iteachmsu Commons? Content is organized by posts, playlists and pathways.

Posts: Posts are shorter or longer-form blog postings about teaching practice(s), questions for the educator community, and/or upcoming teaching and learning events. With an MSU email address and free account signup, educators can immediately contribute blog posts and connected media (e.g. handouts, slide decks, class activity prompts, promotional materials). All educators at MSU are welcome to use and contribute to #iteachmsu. And there are no traditional editorial calendars. Suggested models of posts can be found here.
Playlists: Playlists are groupings of posts curated by individual educators and the #iteachmsu community. Playlists allow individual educators to tailor their development and community experiences based on teaching competency area, interest, and/or discipline.
Pathways: Pathways are groupings of educator learning modules curated by academic and support units for badges and other credentialing.

There are two ways to add your contribution to the space:

Contribute existing local resources for posts and pathways: Your unit, college, and/or department might already have educator development resources that could be of use to the wider MSU teaching and learning community. These could be existing blog posts on teaching practice, teaching webinars, and/or open educational resources (e.g classroom assessments, activities). This content will make up part of the posts, playlists, and pathways on this site. Educators can then curate these posts into playlists based on their individual interests. Please make sure to have permission to share this content on a central MSU web space.
Contribute new content for posts: A strength of the #iteachmsu Commons is that it immediately allows educators to share teaching resources, questions and events through posts to the entire community. Posts can take a variety of forms and are organized by teaching competency area categories, content tags, date, and popularity. Posts can be submitted by both individual educators and central units for immediate posting but must adhere to #iteachmsu Commons community guidelines. Posts could be:




About your teaching practice(s): You discuss and/or reflect on the practices you’re using in your teaching. In addition to talking about your ideas, successes, and challenges, we hope you also provide the teaching materials you used (sharing the assignment, slidedeck, rubric, etc.)
Responses to teaching ideas across the web or social media: You share your thoughts about teaching ideas they engage with from other media across the web (e.g. blog posts, social media posts, etc.).
Cross-posts from other teaching-related blogs that might be useful for the #iteachmsu community: You cross-post content from other teaching-related blogs they feel might be useful to the #iteachmsu community.
About teaching-related events: You share upcoming teaching related events as well as their thoughts about ideas they engage with events at MSU and beyond (e.g. workshops, conferences, etc.). If these events help you think in new ways about your practice, share them with the #iteachmsu community.
Questions for our community: You pose questions via posts to the larger community to get ideas for their practice and connect with others considering similar questions.



What Are the #iteachmsu Commons Policies?Part of the mission of the #iteachmsu Commons is to provide space for sharing, reflecting, and learning for all educators on our campus wherever they are in their teaching development. The commons is designed to encourage these types of interactions and reflect policies outlined by the MSU Faculty Senate.  We maintain the right to remove any post that violates guidelines as outlined here and by MSU. To maintain a useful and safer commons, we ask that you:

Follow the MSU Guidelines for Social Media.
Engage across the #iteachmsu commons in a civil and respectful manner. Content may be moderated in accordance with the MSU Guidelines for Social Media.
Do not share private or confidential information via shared content on the #iteachmsu Commons.

Content posted on the #iteachmsu Commons is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International license. Learn more about this licensing here. Posted comments, images, etc. on the #iteachmsu Commons do not necessarily represent the views of Michigan State University or the #iteachmsu Commons Team. Links to external, non-#iteachmsu Commons content do not constitute official endorsement by, or necessarily represent the views of, the #iteachmsu Commons or Michigan State University. What if I Have #iteachmsu Commons Questions and/or Feedback?If you have any concerns about #iteachmsu Commons content, please email us at iteach@msu.edu. We welcome all feedback and thank you for your help in promoting a safer, vibrant and respectful community.  

Fish farming is an ideal business idea for investors with available land, and it doesn’t always require a large body of water. You can start a fish farm either by creating fish ponds or investing in fish tanks; it’s a highly scalable business idea. Once you have the proper knowledge of fish raising, you will be able to decide the type of fish to raise. According to FinModelsLab, a well-run fish farm can produce a return on investment (ROI) of 15% to 40% annually, with many fish farmers achieving a full return on their investment within three to five years.
Fish such as tilapia, cod, trout, and catfish are popular because they are easy to raise and in high demand. Small-scale farms are the usual suppliers of fish in their local supermarkets and restaurants.
Other popular varieties of commercially-raised fish include:

Yellow Perch
Eel
Grass Carp
Tuna
Salmon

Not all fish are raised for food. Goldfish and koi are popular fish to farm as well. For non-food fish, focus on cultivating premium species that will fetch a higher price when you sell. Whether you are raising fish for food or not, adopting sustainable farming practices will be better for both your business branding and your long-term operational costs.
The decision as to which fish you want to raise will ultimately rely on your skill, financial capacity, market demand, and agro-climatic condition. This refers to the normal soil types, rainfall, temperature, and water availability that affect the type of vegetation in the area.

Direct interaction:
API tests send requests directly to API endpoints and analyze the responses to ensure they meet expected outcomes.This involves checking status codes, response times, and the structure and content of the data returned.








Focus on business logic:
API testing primarily validates the underlying business rules and data flow within an application, independent of the user interface.








Early defect detection:
By testing APIs early in the development lifecycle, issues can be identified and resolved before they become more complex and costly to fix in later stages.








Automation potential:
API tests are highly automatable, allowing for frequent and efficient execution, which is crucial for continuous integration and continuous delivery (CI/CD) pipelines.








Types of API tests:
This can include functional testing (verifying core functionality), performance testing (measuring response times under load), security testing (identifying vulnerabilities), and integration testing (ensuring seamless communication between APIs and external services).