bartoszgajda55

package playground

import org.apache.spark.sql.{SaveMode, SparkSession}
import org.apache.spark.sql.functions._

object TaxiETL {
  def main(args: Array[String]): Unit = {

    if(args.length != 2) { // prod version only
      println("Need two arguments: 1) input data path 2) output data path")

bartoszgajda55

<mat-card>
  <mat-card-title>Number of RSVPs created</mat-card-title>
  <mat-card-subtitle
    >Counted number of events created, within every 10 second
    window</mat-card-subtitle
  >
  <mat-card-content>
    <canvas
      baseChart
      width="600"

bartoszgajda55

##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#

bartoszgajda55

import { NgModule } from '@angular/core';
import { ActionSheetComponent } from './action-sheet/action-sheet';
import {IonicModule} from "ionic-angular";
@NgModule({
	declarations: [ActionSheetComponent],
	imports: [
    // Add this module and every component that need access to Ionic directives
    IonicModule.forRoot(ActionSheetComponent)
  ],
	exports: [ActionSheetComponent]

bartoszgajda55

vs Questions

---

1. http://stackoverflow.com/questions/804115 (rebase vs merge).
2. https://www.atlassian.com/git/tutorials/merging-vs-rebasing (rebase vs merge)
3. https://www.atlassian.com/git/tutorials/undoing-changes/ (reset vs checkout vs revert)
4. http://stackoverflow.com/questions/2221658 (HEAD^ vs HEAD~) (See git rev-parse)
5. http://stackoverflow.com/questions/292357 (pull vs fetch)
6. http://stackoverflow.com/questions/39651 (stash vs branch)
7. http://stackoverflow.com/questions/8358035 (reset vs checkout vs revert)

bartoszgajda55

https://web-push-book.gauntface.com/

https://developers.google.com/web/fundamentals/engage-and-retain/push-notifications/

bartoszgajda55

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules