lokimeyburg

Product Manager Interview Questions

General Questions:

• Tell me about yourself.
• Tell me about the most boring job you have ever had.
• What changes would you make if you came on board?
• What would you say to your boss if he is crazy about an idea, but you think it stinks?
• Assuming that you are selected, what will be your strategy for next 60 days?
• why are not you earning more money at this stage of your career?

danielgtaylor

Moving to ES6 from CoffeeScript

I fell in love with CoffeeScript a couple of years ago. Javascript has always seemed something of an interesting curiosity to me and I was happy to see the meteoric rise of Node.js, but coming from a background of Python I really preferred a cleaner syntax.

In any fast moving community it is inevitable that things will change, and so today we see a big shift toward ES6, the new version of Javascript. It incorporates a handful of the nicer features from CoffeeScript and is usable today through tools like Babel. Here are some of my thoughts and issues on moving away from CoffeeScript in favor of ES6.

While reading I suggest keeping open a tab to Babel's learning ES6 page. The examples there are great.

Punctuation

Holy punctuation, Batman! Say goodbye to your whitespace and hello to parenthesis, curly braces, and semicolons again. Even with the advanced ES6 syntax you'll find yourself writing a lot more punctuatio

paulirish

/* bling.js */

window.$ = document.querySelectorAll.bind(document);

Node.prototype.on = window.on = function (name, fn) {
  this.addEventListener(name, fn);
}

NodeList.prototype.__proto__ = Array.prototype;

pcreux

# Postgresql fancy datatypes!

* array
* hstore (=~ hash)
* json
* jsonb


  Philippe Creux - [@pcreux](http://twitter.com/pcreux)

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

dypsilon

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

---

ryoppy

/**
 * Parse query string.
 * ?a=b&c=d to {a: b, c: d}
 * @param {String} (option) queryString
 * @return {Object} query params
 */
getQueryParams: function(queryString) {
  var query = (queryString || window.location.search).substring(1); // delete ?
  if (!query) {
    return false;

petehunt

/** @jsx React.DOM */
var MyRootComponent = React.createClass({
  getInitialState: function() {
    return {perMinute: '-', perDay: '-'};
  },
  componentDidMount: function() {
    var socket = io.connect(this.props.url);
    socket.on('business.clickout', this.setState.bind(this));
  },
  render: function() {

petehunt

/** @jsx React.DOM */
var MyComponent = React.createClass({
  getInitialState: function() {
    // set up the initial state. used for "logical" initialization code
    return {perMinute: '-', perDay: '-'};
  },
  componentDidMount: function() {
    // fired only once, when the component is added to the DOM
    // used for initialization code that has "side effects" i.e. i/o, jquery plugins, etc
    var socket = io.connect(this.props.url);

zpao

/** @jsx React.DOM */
var MyComponent = React.createClass({
  render: function() {
    // Defaults in case the props are undefined. We'll have a solution for this
    // soon that is less awkward.
    var perMinute = this.props.perMinute || '-';
    var perDay = this.props.perDay || '-';
    return (
      <div>
        <h3>Clickouts</h3>