Jens Tandstad Email & Phone Number

Bergen, Vestland, No

Oslo Area, Norway

Senior consultant in Vivende, with diverse full stack background. Started out with Business Intelligence and SAS, progressed into fullstack web developer with about 50/50 frontend backend. Lately been working on developing legacy software in highly complex environments (linux and docker). Experience with python, numpy and statistical tools. Studies physics part time with focus on Python and numerical simulations.Technology experience:SvelteKit : (4 months)@HTML/CSS : 15 years experienceC# Net , C# .Net Core , Entity Framework : 10 years experiencePython, numpy : 5 years experienceReact-native (iOS and Android app framework) : 2 yearsJava/Groovy, Hibernate, Spring : 4 years experienceAngularJs, Angular : Total of 5 years experiencePHP : More than 10 years experience, less later yearsSQL (MySQL/MariaDb, MSSQL, Postgres) : 12 years, 14 years, and 8 years respectively.TSQL : 4 yearsSAS Base : 2 years experienceDocker, docker-compose, podman : 6 yearsLinux : 7 yearsDNS servers : 5 yearsSearch/index/caching:Elasticsearch, Sphinx search : 3 years.Business Intelligence technologies:SAS Base, SAS DI Studio, Microsoft BI, Qlikview, Tableau - 3 years.Opinions/Values: 0. Lets separate the "why and what" phase of possibilities, from the "how and do" phase of execution. The separation is careful, thought-out decisions between clearly described alternatives.1. Using a well designed RDBMS for a given storage need will probably be fast enough, and save you from horrible consistency bugs, race-conditions and data corruption mishaps. I agree, you could be looking at an exception, but you're probably not.2. Ask for documentation written by the person preceding you, you might be lucky.3. Treat yourself as someone you are responsible for helping. This is relevant for writing system technical documentation. If you can, tell the next developer where to find it!5. Hugh Everett is probably right.