These are the Kickstarter Engineering and Data role definitions for both teams.
--- | |
# https://help.github.com/en/actions/automating-your-workflow-with-github-actions | |
# https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows | |
# https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions | |
# https://help.github.com/en/actions/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions | |
# https://help.github.com/en/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners | |
name : debug | |
on : | |
push : | |
branches : [ "master" ] |
I would like to tell my story of burnout at Amazon, considering the fact that there is so many stories out there on both sides of the issue. My story is also on both sides of the issue, and I've had a lot of time to think about why people can see the same culture but come away with completely different conclusions. This is a throwaway because I still work there and I don't plan on changing that, and I don't exactly trust the company to take this in good faith, despite the fact that I mean this as a purely constructive criticism for a company that I really do like.
I am an autodidact (my formal education only tangentially describes what I can do), and a polymath (capable of holding my own amongst PhD-level Operations Researchers, Statisticians, Econometricians, Data Scientists, Computer Scientists, as well as Software Engineers). I love to solve real world problems, and in many ways am the perfect type of person for Amazon's culture. I started in a level 5 position, but felt from the beginning that I warrant
Graph databases are now one of the core technologies of companies dealing with highly connected data.
Business graphs, social graphs, knowledge graphs, interest graphs and media graphs are frequently in the (technology) news. And for a reason. The graph model represents a very flexible way of handling relationships in your data. And graph databases provide fast and efficient storage, retrieval and querying for it.
Neo4j, the most popular graph database, has proven that ability to deal with massive amount of high connected data in many use-cases.
- 9h00
- Keynote d'ouverture
- 9h30
- A State of Mind. Sebastian Bergmann
- Slides : http://thephp.cc/dates/2014/forum-php/a-state-of-mind
<?php | |
namespace App\EventListener; | |
use Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent; | |
use Symfony\Component\HttpKernel\Exception\HttpExceptionInterface; | |
class ExceptionRethrowListener | |
{ | |
public function onKernelException(GetResponseForExceptionEvent $event) |
module.exports = function(grunt, env) { | |
var defaults = config = { | |
//Write here your configuration , grunt style, in the standard way | |
//Extract informations from package.json | |
pkg: grunt.file.readJSON('package.json'), | |
//Define a global banner |