Biolinguistics or Physicolinguistics? Is The Third Factor Helpful Or Harmful In Explaining Language?

Noam Chomsky (2005) proposed that a ‘third factor’, consisting of general principles and natural laws, may explain core properties of language in a principled manner, minimizing the need for either genetic endowment or experience. But the focus on third-factor patterns in much recent bio-linguistic work is misguided for several reasons: First, ‘the’ third factor is a vague and disparate collection of unrelated components, useless as an analytical tool. Second, the vagueness of the third factor, together with the desire for principled explanations, too often leads to sweeping claims, such as syntax “coming for free, directly from physics”, that are unwarranted without a case-by-case causal analysis. Third, attention is diverted away from a proper causal analysis of language as a biological feature. The point with biolinguistics is to acknowledge the language faculty as a biological feature. The best way forward towards an understanding of language is to take the biology connection seriously, instead of dabbling with physics.

Student Thesis Level: Master’s Thesis in Business Administration Corporate Social Responsibility (CSR) networking : A case study on why members join CSR network and why are they sharing their knowledge

Purpose – This research focuses on finding the reasons, why members from different sectors join a cross-sector/multi-stakeholder CSR network and what motivates them to share (or not to share) their knowledge of CSR and their best practices. Design/methodology/approach – Semi-structured interviews were conducted with members of the largest cross-sector CSR network in Sweden. The sample base of 15 people was chosen to be able to represent a wider variety of members from each participating sectors. As well as the CEO of the intermediary organization was interviewed. The interviews were conducted via email and telephone. Findings – The findings include several reasons linked to the business case of CSR such as stakeholder pressure, competitive advantage, legitimacy and reputation as well as new reasons like the importance of CSR, and the access of further knowledge in the field. Further reasons are in line with members wanting to join a network, such as access to contact or having personal contacts. As to why members are sharing their CSR knowledge, the findings indicate to inspire others, to show CSR commitment, to be visible, it leads to business opportunity and the access of others knowledge, and because it was requested. Reasons for not sharing their knowledge would be the lack of opportunity, lack of time and the lack of experience to do so. Originality/value – The research contributes to existing studies, which focused on Corporate Social Responsibility and cross-sector networking as well as to inter-organizational knowledge sharing in the field of CSR.

Passive MVC och MVVM designmönster i Android : En jämförelse av kodkomplexitet mellan Passive MVC och MVVM

Det mobila operativsystemet Android är idag ett ganska dominerande operativsystem på den mobila marknaden dels på grund av sin öppenhet men också på grund av att tillgängligheten är stor i och med både billiga och dyra telefoner finns att tillgå. Men idag har Android inget fördefinierat designmönster vilket leder till att varje utvecklare får bestämma själv vad som ska användas, vilket ibland kan leda till onödigt komplex kod i applikationerna som sen blir svårtestad och svårhanterlig. Detta arbete ämnar jämföra två designmönster, Passive Model View Controller (PMVC) och Model View View-Model (MVVM), för att se vilket designmönster som blir minst komplext med hjälp av att räkna fram mätvärden med hjälp av Cyclomatic Complexity Number (CCN). Studien är gjord utifrån arbetssättet Design & Creation och ämnar bidra med: kunskap om vilket mönster man bör välja, samt om CCN kan peka ut vilka delar i en applikation som kommer att ta mer eller mindre lång tid att testa. Under studiens gång tog vi även fram skillnader på om man anväder sig av den så kallade Single Responsibilyt Principle (SRP) eller inte. Detta för att se om separerade vyer gör någon skillnad i applikationernas komplexitet. I slutändan så visar studien på att komplexiteten i små applikationer är väldigt likvärdig, men att man även på små applikationer kan se skillnad på hur komplex koden är men också att kodkomplexitet på metodnivå kan ge riktlinjer för testfall.