Peter Gfader's brain noise
What is your engineer per user ratio? #whatsApp rocks
WhatsApp has 430Mio active users with 25 engineers+20 customer support
-> WhatsApp:100 Mio users per engineer (active users!)
FaceBook has over 1 Million users per engineer
Do you know where to get inspiration as a frontend web developer?

CodePen is a playground for the front end side of the web. It’s all about inspiration, education, and sharing.

On Hugo Giraudel’s blog you can find a comparison to other CSS Playgrounds like JsFiddle. 

How to make your Single Page Application SEO friendly (if you want that really)

Prerender servers you full rendered HTML via phantomJS 

On the importance of “Culture” within Scrum
What every *mobile* web developer should care about?

Additionally to this list What every web developer should care about?

  • Latency
  • Connectivity
  • Form factors

Thx to Marc Bächinger

I just realized that a mobile web developer life might be harder than others ;-)

What every web developer should care about?
  • Managing State: Session, client or server
  • Managing browser history = challenge (Back button)
  • Speed
  • URLs
  • Search Engine Friendliness and making the web app more accessible
  • Data Privacy in every sense via Patrick
  • And making the end user happy
What ways do you know to “branch” your code?

Great blog post that explains how “Branch by Abstraction” works.

Think about this as an alternative to using version-control branching.

Only tests let me sleep like a baby at night.

Only tests let me sleep like a baby at night.

Peter Gfader

Supposing babies have a great night sleep. Don’t know, can’t remember…

Agile Architecture (by Allan Holub)

Great video about Architecture with lots of great side stories (Agile Architecture by Allan Holub)

Talks about
- Architecture and goals of Architecture
- Agile and !Agile
- Microsoft and Object Orientation
- Object Orientation VS Procedural
- SOLID principles
-… lots of good stuff in that talk

In the agile project, each Sprint or iteration is a complete project - via @kschwaber

Great blog post from Ken Schwaber that explains “Value” and a “Value Metric” 

In the agile project, each Sprint or iteration is a complete project.
It has requirements, budget, and due date. At the end, it has a completed set of software functionality. Based on what is completes, another project may or may not be initiated, adding more functionality to the functionality just completed. Each Sprint is measured on its own.

Value Metrics are combined into a single metric: Agility Index

Full Article: Agile Value (Ken Schwaber)

Do you know = Business Model Canvas on steroids!

Manage your product (or startup, or whole enterprise) and keep track of the experiments you’re running

A SPA adheres to SoC! #web

A SPA “Single Page Application” adheres to the “Separation of Concerns” Design Principle by splitting the template and the data into 2 separate things that happen on the server. Nice!

What is the effect of getting rid of job titles, managers and hierarchies?

Interesting bit:

It’s not leaderless. There are certainly people who hold a bigger scope of purpose for the organization than others. What it does do is distribute leadership into each role. Everybody is expected to lead and be an entrepreneur in their own roles, and Holacracy empowers them to do so.

From the article:
Zappos is going holacratic: no job titles, no managers, no hierarchy

While travelling in Switzerland

"All this technology is making us antisocial."
(HT to @niamhhughes)

While travelling in Switzerland

"All this technology is making us antisocial."

(HT to @niamhhughes)

Why not a Single Page Application (SPA)?

A SinglePageApplication is more than just a fluid user experience with lots of stuff happening in the client (browser). A SPA is about bringing the state from the server to the client.

SPA goal: Stateless Server. Stateful Client. Nothing more.

Don’t create a Single Page Application if:

  • Your team has huge skills in classic web development
  • You want to avoid Javascript like the pest
  • Your team doesn’t follow all the latest and greatest script kiddies
  • You don’t care about HTTP, HTML, CSS and just want to get your job done ASAP
  • You don’t mind ugly URLs and don’t care about the browser history as long as your app works
  • Your application startup time is critical (no progress bars allowed)
  • The view rendered by the server is never touched by the client
  • Your pages need to be crawled (without any tricks)

In these scenarios another Client Architecture might be better for you.

Did I mention that building a SPA is not easy?