Refine
Year of publication
- 2017 (6) (remove)
Document Type
- Workingpaper / Report (3)
- Bachelor Thesis (1)
- Master's Thesis (1)
- Study Thesis (1)
Language
- English (6) (remove)
Has Fulltext
- yes (6) (remove)
Keywords
- Angehörigenpflege (1)
- Cross-Plattform Entwicklung (1)
- Entwicklung (1)
- Hip Hop (1)
- M (1)
- Masterthesis (1)
- NativeScript (1)
- Progressive Web Apps (1)
- Satire (1)
- Senegal (1)
Investing as Random Trial
(2017)
We introduce an investment algorithm for a market of individual securities. The investment algorithm is derived from constraints depending on investment parameters in order to limit the risk and to take into account an individual investor. One constraint is devoted to trading costs. Purchased securities are selected randomly among securities that meet the buy condition, making trading a random trial. Simulations with historical price data are demonstrated for a simple example: The buy condition is evaluated on the basis of the price relationship for two subsequent trading days and the sales condition is defined by holding securities only for one day. A trading expert evaluates the expected return for the investment algorithm with respect to the random selection. Thus, the expert informs precisely on how many market players perform using the same investment algorithm. Its findings are for a parametrized set of buy conditions simultaneously, which makes a trading expert a valuable tool for theorists as well as for practitioners. In our example, the trading expert demonstrated clearly a significant mean reversion effect for a horizon of one day.
Progressive web applications (PWAs) seem to be the next big thing in the mobile landscape. These are web applications with “super-powers” which are meant to provide the kinds of user experiences previously only native mobile applications could. Therefore they are able to match native applications in their capabilities but still thrive on the reachability of the web. They achieve this by implementing certain characteristics which originate from innovative standards and sophisticated best practices. Conveniently, as it is the web, PWAs are working seamlessly cross-platform. One of the closest things to a PWA so far may be an application created with the NativeScript framework. Such an application is also developed with web technologies yet able to use any native interface directly. This is made possible by using a designated runtime for mediating between JavaScript and the mobile system. Eventually, NativeScript is able to offer a high degree nativity yet also of convenient abstraction during development. This paper is set out to deliver further insight into both approaches by contrasting them based on the characteristics of PWAs. For this purpose, these characteristics are elaborated and adjusted to be applicable to native mobile applications. Hence a reasonable basis for what to expect from a native application is derived. Then NativeScript is assessed on this basis by the means of transferable concepts and technologies as well as a prototypic mobile application. Finally, an informed discussion and conclusion is performed based on the results. The comprehensive characteristics of PWAs resolve previous shortcomings with well thought out concepts and new technologies. These are transferable to native mobile applications to a far extent and may also be put into practice with NativeScript. The framework’s approach may be very well called ingenious, however, in the long run it might fall short of the innovative concept of PWAs. Having said this, it is still able to serve as a practical measure for creating appealing user experiences for multiple systems with arguably little effort. Due to large overlap a transformation between the two application types is a realistic option. Either way, web technologies are far from what they used to be and it is exciting to see how the mobile and web landscape will evolve in the future.
While developing for multiple platforms at once seems like a convenient solution, there are several challenges arising when trying to abstract the entire mobile development. This paper is meant to evaluate current cross-platform development for mobile applications. The background for its necessity, its conceptual approach and the problems to face when developing cross-platform were determined and explained in detail. Afterwards, certain solutions were evaluated against the former insights. Based on the results, an informed discussion and conclusion was performed. The mobile environment consist of only two big players by now, Android and iOS. These operating systems differ in architecture, design and consequently in the way applications are developed for each of them. Therefore, high demands are made towards cross-platform solutions. Tools which allow for the creation of applications for multiple platforms at once have to match native applications in regard to user experience and performance. At the same time they need to be able to optimize developments with the goal of being cost efficient. Apache Cordova, Xamarin and NativeScript were selected for evaluation in regard to their ability to meet these requirements. Cordova acts as the comparison group of cross-platform tools. It is the big player in the field and there are reasons for this. However, aspiring solutions with higher nativity and ambitious approaches are emerging. Xamarin and NativeScript deliver top quality results while offering loosely coupled developments. Therefore it is possible to develop high quality applications and still benefit from the advantages of platform-independent solutions. As a consequence mobile development is about to change in the foreseeable future. More sophisticated approaches may lead to a higher number of developments done cross-platform, and rightfully so.
Reconciling work and family life is one of the main issues of welfare state policies in the fields of childcare and long-term care. On that account, policy and research are focused almost exclusively on women – often on the reconciliation of work and childbearing – and social policy at the state level. In our study, we concentrate on men who reconcile gainful employment with elderly care, and we include the company level – a level of analysis often neglected in traditional theoretical approaches and typologies of comparative welfare state research. In Germany, during the last decade, the share of sons who are responsible for taking care of their elderly relatives has remarkably increased. In our qualitative research, we carried out comparative case studies in eleven German companies. We conducted around 60 interviews with male employees caring for an elderly relative, as well as with members of the works councils and human resources departments in different kinds of companies. We analysed which familial, social, professional, legal as well as occupational resources are central for these men, how they cope with reconciling work and care, and which gaps in the welfare system they identify. Interestingly, the overwhelming majority of the caring sons claim not to have problems in reconciling work and care, although they spend significant time on caring. In this paper we try to explain this pattern by looking at their typical care arrangements. We found that while women tend to organise employment around care, men rather seem to organise care around their employment. Given the feminist critique of the “adult worker model” this is an interesting result and needs theoretical reflection. Do men have the solution to the care-blindness of the “adult worker model” without falling into the “cold modern model of care”? Which resources are mainly used in “adult worker care arrangements”? Where are the limits of the approach?