| import java.text.ParseException; | |
| import java.text.SimpleDateFormat; | |
| import java.time.LocalDate; | |
| import java.time.ZoneId; | |
| import java.util.Date; | |
| /** | |
| * This pattern has the following benefits: | |
| * | |
| * - Date formats are referenced as a strong type |
| # Guide setup GlobalProtect Portal on Linux | |
| ## Setup GlobalProtect | |
| sudo apt update | |
| Download GlobalProtect: https://github.com/jundat95/GlobalProtectVPN/raw/master/PanGPLinux-5.0.8-c6.tgz | |
| Go to folder Downloads and Unzip: tar -xvzf PanGPLinux-5.0.8-c6.tgz |
NB: In order to access the Api Gateway through the public DNS of the VPC endpoint, a curl request has to have the api id as header. See also here
curl -i -H "x-apigw-api-id: " https://vpce-.execute-api..vpce.amazonaws.com/
It seems that it does not matter what timezone is on the server as long as you have the time set right for the current timezone, know the timezone of the datetime columns that you store, and are aware of the issues with daylight savings time.
On the other hand if you have control of the timezones of the servers you work with then you can have everything set to UTC internally and never worry about timezones and DST.
Here are some notes I collected of how to work with timezones as a form of cheatsheet for myself and others which might influence what timezone the person will choose for his/her server and how he/she will store date and time.
| fun ViewManager.appBarLayout(init: AppBarLayout.() -> Unit = {}) = | |
| __dslAddView({ AppBarLayout(it) }, init, this) | |
| fun ViewManager.collapsingToolbarLayout(init: CollapsingToolbarLayout.() -> Unit = {}) = | |
| __dslAddView({ CollapsingToolbarLayout(it) }, init, this) | |
| fun ViewManager.coordinatorLayout(init: CoordinatorLayout.() -> Unit = {}) = | |
| __dslAddView({ CoordinatorLayout(it) }, init, this) | |
| fun ViewManager.floatingActionButton(init: FloatingActionButton.() -> Unit = {}) = |
It seems that it does not matter what timezone is on the server as long as you have the time set right for the current timezone, know the timezone of the datetime columns that you store, and are aware of the issues with daylight savings time.
On the other hand if you have control of the timezones of the servers you work with then you can have everything set to UTC internally and never worry about timezones and DST.
Here are some notes I collected of how to work with timezones as a form of cheatsheet for myself and others which might influence what timezone the person will choose for his/her server and how he/she will store date and time.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| var CryptoJS = require("crypto-js");//replace thie with script tag in browser env | |
| //encrypt | |
| var rawStr = "hello world!"; | |
| var wordArray = CryptoJS.enc.Utf8.parse(rawStr); | |
| var base64 = CryptoJS.enc.Base64.stringify(wordArray); | |
| console.log('encrypted:', base64); | |
| //decrypt | |
| var parsedWordArray = CryptoJS.enc.Base64.parse(base64); |
| - [ ] Math | |
| - [ ] Linear Algebra | |
| - [ ] Lay - Linear Algebra | |
| - [ ] 18.06 Linear Algebra | |
| http://www.scotthyoung.com/blog/mit-challenge/#more-link1806 | |
| - [ ] Burke Lecture Notes | |
| http://www.math.washington.edu/~burke/crs/407/lectures/ | |
| - [ ] Coding The Matrix | |
| http://www.amazon.com/dp/0615880991/?tag=coursera-course198-20 | |
| - [ ] Quantifying Uncertainty |