The document discusses the second stage of assessment which is determining acceptable evidence of student learning, such as how teachers will know if students have achieved desired results and standards. It explains that teachers should think about what types of assessment evidence is needed to show students have achieved the goals outlined in stage 1. The document also provides examples of how students can demonstrate their understanding through explanation, interpretation, application, perspective, empathy, and self-knowledge.
The document discusses the second stage of assessment which is determining acceptable evidence of student learning, such as how teachers will know if students have achieved desired results and standards. It explains that teachers should think about what types of assessment evidence is needed to show students have achieved the goals outlined in stage 1. The document also provides examples of how students can demonstrate their understanding through explanation, interpretation, application, perspective, empathy, and self-knowledge.
This document discusses the growing impact of technology on education and presents strategies for effectively integrating technology into teaching. It notes that while technology has advanced rapidly, education curriculums have not fully embraced technology's importance. The document also addresses challenges like balancing technology with traditional instruction and increasing testing pressures. Additionally, it cautions against overreliance on tools like PowerPoint and advocates using technology visually to engage audiences while addressing complex topics that cannot be overly simplified.
Delivering software - process and infrastructureRune Sundling
This document discusses processes and infrastructure for delivering software. It describes a development process of developing, testing, and fixing errors before release. It then outlines roles in the process like developers, business, and operations. The document details a delivery process with commit and acceptance test stages to increase confidence in a build's readiness for production through faster feedback. It advocates for continuous delivery using tools like source control, continuous integration, and configuration management.
The document discusses different models and theories related to health and wellness. It covers the medical model which focuses on treating disease, injuries, and disabilities with drugs and surgeries. It also mentions the environmental model which considers social and physical factors. A holistic model is described that takes a broader view of health as physiological, mental, emotional, social and spiritual well-being. The dimensions of health and wellness are defined along with several theories of health behavior change.
The document summarizes theories of continental drift and plate tectonics. In 1915, Alfred Wegener first proposed the theory of continental drift, which states that parts of the Earth's crust slowly drift atop a liquid core. Wegener hypothesized that around 200 million years ago, all the continents were joined together in a supercontinent called Pangaea. Pangaea later broke apart into smaller supercontinents, and by the end of the Cretaceous period the continents had separated into their modern positions. In the 1960s, Harry Hess proposed the theory of seafloor spreading, which provided support for continental drift by showing how ocean floors spread outward from underwater ridges. Plate tectonics expanded on these ideas
Static code analysis involves using tools to analyze source code for potential issues. It can find bugs, code quality issues, and other problems but is not a replacement for testing. Several experts note that combining static analysis, inspections, and testing leads to better defect removal than only using testing. Common static analysis tools include FxCop, StyleCop, ReSharper, and NDepend. Integrating static analysis into the development process can provide benefits but obstacles like resources and unrealistic expectations must be addressed.
Being able to code does not make you a good developerRune Sundling
Rune Sundling argues in his blog post that being able to code alone does not make someone a good developer. He lists several soft skills that are also important for developers, including taking responsibility, cooperation, communication, listening skills, and considering colleagues, meetings, feedback and one's well-being. Sundling emphasizes that good development requires both technical coding ability as well as soft skills like communication, responsibility and collaboration.
Kartlegge varsling og psykososialt arbeidsmiljøRandi Hoff
Nye krav til varslingsrutiner, gir ansatte anledning til å varsle om kritikkverdige forhold. Arbeidsgiver er pliktig til å legge tilrette for at rutiner for mottak, behandling og og oppfølging av varsling er ivaretatt.
Med HR- Innsikt, gir vi ledelsen anledning til å kartlegge og å dokumentere om de ansatte har kjennskap til bedriftens varslingsrutiner, og er trygge på at varslere blir ivaretatt i henhold til krav om anonymitetsbeskyttelse.
Foredrag om "godt nok" ledelse på samling hos Future Leaderskarptom
Ledelse er et konsept det er knyttet mye forventninger til, for mye forventninger. Ledere gjør ikke alltid det de skal og det er mange grunner til det. Kanskje skal vi derfor i stedet for effektiv ledelse snakke om "god nok" ledelse.
Forelesning, metodekurs for masterstudenter i statsvitenskap, om mitt delprosjekt "Menneskesyn i omstillingsprosessene i Store Norske", del av prosjektet "Konjunktur og kultur. En analyse av omstillingsprosessene i Store Norske.
This document discusses the growing impact of technology on education and presents strategies for effectively integrating technology into teaching. It notes that while technology has advanced rapidly, education curriculums have not fully embraced technology's importance. The document also addresses challenges like balancing technology with traditional instruction and increasing testing pressures. Additionally, it cautions against overreliance on tools like PowerPoint and advocates using technology visually to engage audiences while addressing complex topics that cannot be overly simplified.
Delivering software - process and infrastructureRune Sundling
This document discusses processes and infrastructure for delivering software. It describes a development process of developing, testing, and fixing errors before release. It then outlines roles in the process like developers, business, and operations. The document details a delivery process with commit and acceptance test stages to increase confidence in a build's readiness for production through faster feedback. It advocates for continuous delivery using tools like source control, continuous integration, and configuration management.
The document discusses different models and theories related to health and wellness. It covers the medical model which focuses on treating disease, injuries, and disabilities with drugs and surgeries. It also mentions the environmental model which considers social and physical factors. A holistic model is described that takes a broader view of health as physiological, mental, emotional, social and spiritual well-being. The dimensions of health and wellness are defined along with several theories of health behavior change.
The document summarizes theories of continental drift and plate tectonics. In 1915, Alfred Wegener first proposed the theory of continental drift, which states that parts of the Earth's crust slowly drift atop a liquid core. Wegener hypothesized that around 200 million years ago, all the continents were joined together in a supercontinent called Pangaea. Pangaea later broke apart into smaller supercontinents, and by the end of the Cretaceous period the continents had separated into their modern positions. In the 1960s, Harry Hess proposed the theory of seafloor spreading, which provided support for continental drift by showing how ocean floors spread outward from underwater ridges. Plate tectonics expanded on these ideas
Static code analysis involves using tools to analyze source code for potential issues. It can find bugs, code quality issues, and other problems but is not a replacement for testing. Several experts note that combining static analysis, inspections, and testing leads to better defect removal than only using testing. Common static analysis tools include FxCop, StyleCop, ReSharper, and NDepend. Integrating static analysis into the development process can provide benefits but obstacles like resources and unrealistic expectations must be addressed.
Being able to code does not make you a good developerRune Sundling
Rune Sundling argues in his blog post that being able to code alone does not make someone a good developer. He lists several soft skills that are also important for developers, including taking responsibility, cooperation, communication, listening skills, and considering colleagues, meetings, feedback and one's well-being. Sundling emphasizes that good development requires both technical coding ability as well as soft skills like communication, responsibility and collaboration.
Kartlegge varsling og psykososialt arbeidsmiljøRandi Hoff
Nye krav til varslingsrutiner, gir ansatte anledning til å varsle om kritikkverdige forhold. Arbeidsgiver er pliktig til å legge tilrette for at rutiner for mottak, behandling og og oppfølging av varsling er ivaretatt.
Med HR- Innsikt, gir vi ledelsen anledning til å kartlegge og å dokumentere om de ansatte har kjennskap til bedriftens varslingsrutiner, og er trygge på at varslere blir ivaretatt i henhold til krav om anonymitetsbeskyttelse.
Foredrag om "godt nok" ledelse på samling hos Future Leaderskarptom
Ledelse er et konsept det er knyttet mye forventninger til, for mye forventninger. Ledere gjør ikke alltid det de skal og det er mange grunner til det. Kanskje skal vi derfor i stedet for effektiv ledelse snakke om "god nok" ledelse.
Forelesning, metodekurs for masterstudenter i statsvitenskap, om mitt delprosjekt "Menneskesyn i omstillingsprosessene i Store Norske", del av prosjektet "Konjunktur og kultur. En analyse av omstillingsprosessene i Store Norske.
Om ”kurset”. Et slags inspirasjonskurs. Det er mer en veiledning, vi gir noen råd og tips til de som kanskje går og planlegger en spørreundersøkelse eller er interesserte av andre årsaker.
16. Kommunikasjon - lytte Måten ting blir sagt Konsentrasjon Øyekontakt Tålmodighet Å dømme Forstå kontra tenke på motsvar Forklare hva du har forstått
21. Egenutvikling Effektivisere tiden man har Podcasts Software Engineering Radio Hanselminutes Herding code Elegant code Deep Fried Bytes The ThirstyDeveloper .NET Rocks