Skip to content

Commit

Permalink
Removed commented tabs-code
Browse files Browse the repository at this point in the history
  • Loading branch information
@jwanglof
jwanglof committed Aug 11, 2016
1 parent dd30b4d commit 893a35a
Showing 1 changed file with 36 additions and 72 deletions.
108 changes: 36 additions & 72 deletions cv/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -63,25 +63,13 @@ <h3>E-mail</h3>
<span><i class="icon-at"></i><a href="https://www.liu.se/?l=en&sc=true" target="_blank">Linköping university</a></span>
<span>2011 - 2016</span>
</div>
<!--<div class="text tabs two">-->
<!--<input id="liu-tab-tldr" type="radio" name="liu-tab-group" checked />-->
<!--<label class="pseudo button toggle" for="liu-tab-tldr">TL;DR</label>-->
<!--<input id="liu-tab-long" type="radio" name="liu-tab-group" />-->
<!--<label class="pseudo button toggle" for="liu-tab-long">Longer</label>-->
<!--<div class="row">-->
<!--<div class="tab">-->
Innovative programming is a bachelors degree for developers. During these years I've learned a lot of different languages which have given me a very broad syntax-understanding for any languages.
Innovative programming is a bachelors degree for developers. During these years I've learned a lot of different languages which have given me a very broad syntax-understanding for any languages.
<br />
<!--</div>-->
<!--<div class="tab">-->
I learned how to work in smaller, and bigger, groups. In these groups we mainly used agile development which I really like, we also read about other methodolgies but didn't use them in practice. My thesis was how to cache emails from a Gmail-account in the browser to minify the traffic to a server.
<br />
<strong>Languages used</strong>: Python, JavaScript, Java, C#/.Net, Ruby, C++/C
<br />
<strong>Other</strong>: Git, Android, SQL, Linux
<!--</div>-->
<!--</div>-->
<!--</div>-->
I learned how to work in smaller, and bigger, groups. In these groups we mainly used agile development which I really like, we also read about other methodolgies but didn't use them in practice. My thesis was how to cache emails from a Gmail-account in the browser to minify the traffic to a server.
<br />
<strong>Languages used</strong>: Python, JavaScript, Java, C#/.Net, Ruby, C++/C
<br />
<strong>Other</strong>: Git, Android, SQL, Linux
</div>

<!--UMU-->
Expand Down Expand Up @@ -172,37 +160,25 @@ <h3>E-mail</h3>
<span><i class="icon-at"></i><a href="https://briteback.com" target="_blank">Briteback</a></span>
<span>04/2015 - <i>present</i></span>
</div>
<!--<div class="text tabs two">-->
<!--<input id="briteback-tab-tldr" type="radio" name="briteback-tab-group" checked />-->
<!--<label class="pseudo button toggle" for="briteback-tab-tldr">TL;DR</label>-->
<!--<input id="briteback-tab-long" type="radio" name="briteback-tab-group" />-->
<!--<label class="pseudo button toggle" for="briteback-tab-long">Longer</label>-->
<!--<div class="row">-->
<!--<div class="tab">-->
Briteback is a start-up that builds a communication app that focuses on businesses. It combines e-mail, calendar and chat seamlessly where you can share an e-mail to a chat-room, to be able to discuss it further without having to forward it to the correct people, or vice versa, you can create an e-mail from a chat-message. I had many responsibilities since we were only a team of 6, and I were one of the first employees.
<br />
I set-up our infrastructure, I developed on both backend and frontend, and also helped choosing what technologies we should use when we started developing. I worked at Briteback parallel while finishing my studies.
<br />
I'm still employed at Briteback but on a need-help basis, meaning that I will only work if they need help with anything that are within my areas at Briteback.
<!--</div>-->
<!--<div class="tab">-->
<h3>Infrastructure</h3>
When Briteback was about to release their alpha version I was in charge to investigate, and set-up, Briteback's entire infrastructure. I spent many hours researching what other developers were saying that would fit the backend-structure. I came up with a plan that we tried, but failed because I didn't have the experience needed at that time. The second plan worked fine and that's the one Briteback is using today, with a few tweaks of course.
<br />
My thought through the whole process was to make sure that it would be very easy to use, so that any developer at Briteback could update the app without a hitch, and without me being present.
<br />
The infrastructure contains of VPNs from Digital Ocean that are running Docker-containers, which are easily managed from Docker Cloud. Behind these VPNs there are database-servers that do regular backups and can only be accessed from the office IP and by the different servers. Every server is monitored online on a big-screen TV at the office, with a log warning-system. The VPNs are running either Ubuntu or Debian. RethinkDB is used as database.
<br />
When version 3.0 was about to be release I created the migration-script for the new database-structure so all the old data was migrated correctly. The script was created for NodeJS and it took a couple of days to complete.

<h3>Backend</h3>
I created the skeleton that is used for all new servers Briteback creates. It consist of basic libraries that all the servers use and the folder-structure. All Briteback's servers are written in NodeJS with ES6 syntax.

<h3>Frontend</h3>
The frontend consist of BackboneJS and React with ES6 syntax. Since ES6 is used both on backend and frontend makes it easier to switch between them. The connection with the backend is based on WebSockets, with a wrapper called Deepstream that makes the communication via the WebSocket a bit easier and also gives more functions that makes working with data easier.
<!--</div>-->
<!--</div>-->
<!--</div>-->
Briteback is a start-up that builds a communication app that focuses on businesses. It combines e-mail, calendar and chat seamlessly where you can share an e-mail to a chat-room, to be able to discuss it further without having to forward it to the correct people, or vice versa, you can create an e-mail from a chat-message. I had many responsibilities since we were only a team of 6, and I were one of the first employees.
<br />
I set-up our infrastructure, I developed on both backend and frontend, and also helped choosing what technologies we should use when we started developing. I worked at Briteback parallel while finishing my studies.
<br />
I'm still employed at Briteback but on a need-help basis, meaning that I will only work if they need help with anything that are within my areas at Briteback.
<h3>Infrastructure</h3>
When Briteback was about to release their alpha version I was in charge to investigate, and set-up, Briteback's entire infrastructure. I spent many hours researching what other developers were saying that would fit the backend-structure. I came up with a plan that we tried, but failed because I didn't have the experience needed at that time. The second plan worked fine and that's the one Briteback is using today, with a few tweaks of course.
<br />
My thought through the whole process was to make sure that it would be very easy to use, so that any developer at Briteback could update the app without a hitch, and without me being present.
<br />
The infrastructure contains of VPNs from Digital Ocean that are running Docker-containers, which are easily managed from Docker Cloud. Behind these VPNs there are database-servers that do regular backups and can only be accessed from the office IP and by the different servers. Every server is monitored online on a big-screen TV at the office, with a log warning-system. The VPNs are running either Ubuntu or Debian. RethinkDB is used as database.
<br />
When version 3.0 was about to be release I created the migration-script for the new database-structure so all the old data was migrated correctly. The script was created for NodeJS and it took a couple of days to complete.

<h3>Backend</h3>
I created the skeleton that is used for all new servers Briteback creates. It consist of basic libraries that all the servers use and the folder-structure. All Briteback's servers are written in NodeJS with ES6 syntax.

<h3>Frontend</h3>
The frontend consist of BackboneJS and React with ES6 syntax. Since ES6 is used both on backend and frontend makes it easier to switch between them. The connection with the backend is based on WebSockets, with a wrapper called Deepstream that makes the communication via the WebSocket a bit easier and also gives more functions that makes working with data easier.
</div>

<!--Bo Tillsammans-->
Expand All @@ -212,29 +188,17 @@ <h3>Frontend</h3>
<span><i class="icon-at"></i><a href="https://www.botillsammans.nu" target="_blank">Bo Tillsammans</a></span>
<span>04/2014 - <i>present</i></span>
</div>
<!--<div class="text tabs two">-->
<!--<input id="botillsammans-tab-tldr" type="radio" name="botillsammans-tab-group" checked />-->
<!--<label class="pseudo button toggle" for="botillsammans-tab-tldr">TL;DR</label>-->
<!--<input id="botillsammans-tab-long" type="radio" name="botillsammans-tab-group" />-->
<!--<label class="pseudo button toggle" for="botillsammans-tab-long">Longer</label>-->
<!--<div class="row">-->
<!--<div class="tab">-->
Bo Tillsammans (eng. Live Together) is Sweden's only service to promote communal-living in an easy way. The project was started by Hanna Söderquist in 2014 after noticing that Sweden doesn't have the same communal-living society as Germany have, where she studied for a couple of years. She started to look for developers and found me and Alexander Häger at Linköpings university, and we came up with the different ideas that are up on the site today. The site is a side-project that has been developed by us in parallel with both finishing my studies and working.
<br />
We created the site from the ground up using <a href="http://flask.pocoo.org/" target="_blank">Flask</a> (a Python microframework) as backend and <a href="https://angularjs.org/" target="_blank">AngularJS</a> as frontend-framework and the site is growing every day with new users that are looking for and offering accommodations.
<!--</div>-->
<!--<div class="tab">-->
<h3>Infrastructure</h3>
We have gone through many iterations on our server with different configurations to find the correct one that scales well and is easily maintained. When we released our version 1.0 I re-did our server one more time, and now with Docker. I chose this configuration because I have really good experiences with Docker from my work at Briteback.

<h3>Backend</h3>
The backend is written in Python, using Flask as framework. I really like Python and that's mainly why we chose Flask as backend framework.

<h3>Frontend</h3>
The frontend is based on AngularJS as frontend-framework, with CSS and HTML5. Alexander chose AngularJS since he needed it for a web-design course at the university. The code-base is from we started, with a few iterations on it, but I'm currently migrating to an ES6 syntax so it's nicer, and also so it makes it easier to transform the app to Angular 2 if we choose.
<!--</div>-->
<!--</div>-->
<!--</div>-->
Bo Tillsammans (eng. Live Together) is Sweden's only service to promote communal-living in an easy way. The project was started by Hanna Söderquist in 2014 after noticing that Sweden doesn't have the same communal-living society as Germany have, where she studied for a couple of years. She started to look for developers and found me and Alexander Häger at Linköpings university, and we came up with the different ideas that are up on the site today. The site is a side-project that has been developed by us in parallel with both finishing my studies and working.
<br />
We created the site from the ground up using <a href="http://flask.pocoo.org/" target="_blank">Flask</a> (a Python microframework) as backend and <a href="https://angularjs.org/" target="_blank">AngularJS</a> as frontend-framework and the site is growing every day with new users that are looking for and offering accommodations.
<h3>Infrastructure</h3>
We have gone through many iterations on our server with different configurations to find the correct one that scales well and is easily maintained. When we released our version 1.0 I re-did our server one more time, and now with Docker. I chose this configuration because I have really good experiences with Docker from my work at Briteback.

<h3>Backend</h3>
The backend is written in Python, using Flask as framework. I really like Python and that's mainly why we chose Flask as backend framework.

<h3>Frontend</h3>
The frontend is based on AngularJS as frontend-framework, with CSS and HTML5. Alexander chose AngularJS since he needed it for a web-design course at the university. The code-base is from we started, with a few iterations on it, but I'm currently migrating to an ES6 syntax so it's nicer, and also so it makes it easier to transform the app to Angular 2 if we choose.
</div>

<!--Janitor-->
Expand Down

0 comments on commit 893a35a

Please sign in to comment.