<commit_before>{
    "project": {
        "title": "To BEM or not to BEM",
        "description": "a series of interviews on BEM methodology",
        "basepath": "http://www.didoo.net/to-bem-or-not-to-bem"
    },
    "interviews": [
        {
            "id" : "01",
            "nameslug" : "christoph__reinartz",
            "title" : "Interview with <NAME>",
            "date" : "2016-05-06",
            "status" : "public",
            "quote" : "BEM was not designed to be pretty but to scale. In general I think it is quite bulletproof. And it helped us a lot.",
            "interviewee": {
                "avatar": "img/christoph+reinartz.jpg",
                "fullname": "<NAME>",
                "minibio": "ux engineer & frontend architect, fullstack css developer, team lead ui/ux engineering at trivago",
                "links": {
                    "website": "http://www.creinartz.de",
                    "twitter": "https://twitter.com/pistenprinz",
                    "github": "https://github.com/creinartz"
                }
            }
        },
        {
            "id" : "02",
            "nameslug" : "razvan__spatariu",
            "title" : "Interview with <NAME>",
            "date" : "2016-05-15",
            "status" : "public",
            "quote" : "BEM does not translate to “making sense of things”. If it's a logical decision that can be understood and extended by anyone in your team just by reading the code/documentation, then it's the right decision. And don't assume it will auto-magically solve your scalability issues. It is a good start, but there is a lot of work to be done.",
            "interviewee": {
                "avatar": "img/razvan+spatariu.jpg",
                "fullname": "<NAME>",
                "minibio": "frontend engineer at Funding Circle UK<br>co-organiser of london sass meetup",
                "links": {
                    "twitter": "https://twitter.com/RazvanSpatariu",
                    "github": "https://github.com/RazvanDH",
                    "codepen": "http://codepen.io/RazvanDH/"
                }
            }
        },
        {
            "id" : "03",
            "nameslug" : "sam__thurman",
            "title" : "Interview with <NAME>",
            "date" : "2016-06-15",
            "status" : "public",
            "quote" : "I have preached BEM, and I think it's a good solution to a lot of CSS semantic issues. But I think having a well documented naming scheme is more important than having a perfect one, and being dogmatic doesn't help anyone.",
            "interviewee": {
                "avatar": "img/sam+thurman.jpg",
                "fullname": "<NAME>",
                "minibio": "front end developer working at the intersection of development and design at BuzzFeed",
                "links": {
                    "website": "http://www.samthurman.com/",
                    "twitter": "https://twitter.com/sam_thurman",
                    "github": "https://github.com/samthurman"
                }
            }
        },
        {
            "id" : "04",
            "nameslug" : "micah__godbolt",
            "title" : "Interview with <NAME>",
            "date" : "2016-06-22",
            "status" : "public",
            "quote" : "While I really like the flat selector approach that BEM defines, I prefer to not clutter my elements with a bunch of classes. My decision was then to use data attributes to apply my modifiers and contexts.",
            "interviewee": {
                "avatar": "img/micah+godbolt.jpg",
                "fullname": "<NAME>",
                "minibio": "frontend architect, blogger, podcaster, trainer, speaker<br>author of Front End Architecture for Design Systems",
                "links": {
                    "website": "https://micah.codes",
                    "twitter": "https://twitter.com/micahgodbolt",
                    "github": "https://github.com/micahgodbolt"
                }
            }
        },
        {
            "id" : "05",
            "nameslug" : "varya__stepanova",
            "title" : "Interview with <NAME>",
            "date" : "2016-07-12",
            "status" : "public",
            "quote" : "If you have to imagine this kind of pain, think about new versions of Bootstrap. And multiply it by 1000 due to the bigger size of the library and the amount of projects. These were the problems which BEM offered to solve.",
            "interviewee": {
                "avatar": "img/varya+stepanova.jpg",
                "fullname": "<NAME>",
                "minibio": "Frontend developer for Zalando. Previously: SC5, TMG and Yandex. React lover, BEM adept and a cat fan",
                "links": {
                    "website": "http://varya.me/",
                    "twitter": "https://twitter.com/varya_en",
                    "tech blog": "http://varya.me/en/posts/"
                }
            }
        },
        {
            "id" : "06",
            "nameslug" : "adam__onishi",
            "title" : "Interview with <NAME>",
            "date" : "2016-08-05",
            "status" : "public",
            "quote" : "BEM fits so easily with the way I want to write CSS now. I’ve been focusing more on a component based architecture long before I joined the Origami team, and for that BEM just makes sense.",
            "interviewee": {
                "avatar": "img/adam+onishi.jpg",
                "fullname": "<NAME>",
                "minibio": "Front-end developer working in the Origami team at the Financial Times in London. Co-creator of 12 Devs of Xmas and author of the book Pro WordPress Theme Development.",
                "links": {
                    "website": "http://adamonishi.com/",
                    "twitter": "https://twitter.com/onishiweb",
                    "github": "https://github.com/onishiweb"
                }
            }
        },
        {
            "id" : "07",
            "nameslug" : "stephanie__rewis",
            "title" : "Interview with <NAME>",
            "date" : "2016-11-16",
            "status" : "public",
            "quote" : "Though nothing is perfect, I really appreciate the way BEM's structure makes it easy to tell at a glance exactly how selectors relate to each other.",
            "interviewee": {
                "avatar": "img/stephanie-rewis.jpg",
                "fullname": "<NAME>",
                "minibio": "Principal UI Developer at Salesforce Lightning Design System. Front-end developer, passionate about web standards and accessibility, speaker and author.",
                "links": {
                    "medium": "https://medium.com/@stefsull",
                    "twitter": "https://twitter.com/stefsull",
                    "github": "https://github.com/stefsullrew"
                }
            }
        },
        {
            "id" : "08",
            "nameslug" : "jof__arnold",
            "title" : "Interview with <NAME>",
            "date" : "2016-01-10",
            "status" : "public",
            "quote" : "BEM definitely promotes more CSS. We've moved away from it for that reason.",
            "interviewee": {
                "avatar": "img/jof-arnold.jpg",
                "fullname": "<NAME>",
                "minibio": "Frontend developer, Y Combinator alumnus and one of the humans at BOTS.sh. When not at his desk he can be found on his bike or staring at art.",
                "links": {
                    "website": "http://www.jofarnold.com/",
                    "twitter": "https://twitter.com/JofArnold",
                    "github": "https://github.com/JofArnold"
                }
            }
        },
        {
            "id" : "09",
            "nameslug" : "katia__utochkina",
            "title" : "Interview with <NAME>",
            "date" : "2017-01-24",
            "status" : "public",
            "quote" : "I think BEM is easy to pick up. It is very logical. It also allows for better code readability. I think it makes my code more consistent and logical.",
            "interviewee": {
                "avatar": "img/katia-utochkina.jpg",
                "fullname": "<NAME>",
                "minibio": "A budding software engineer, recently converted to a programming career from a journalism background. Codebar student. In love with HTML/CSS, JavaScript and Python.",
                "links": {
                    "website": "https://katia-utochkina.github.io/",
                    "blog": "http://iheartcoding.herokuapp.com/",
                    "github": "https://github.com/katia-utochkina"
                }
            }
        },
        {
            "id" : "10",
            "nameslug" : "mark__dalgleish",
            "title" : "Interview with <NAME>",
            "date" : "2017-02-01",
            "status" : "public",
            "quote" : "One of the most exciting things about CSS Modules for me is that it takes the principles behind BEM, but makes it look and feel like regular global CSS.",
            "interviewee": {
                "avatar": "img/mark-dalgleish.jpg",
                "fullname": "<NAME>",
                "minibio": "CSS Modules co-creator, MelbJS organiser. Full-stack ECMAScript addict, interaction craftsman + coffee drinker. DesignOps Lead at SEEK.",
                "links": {
                    "website": "http://markdalgleish.com/",
                    "twitter": "https://twitter.com/markdalgleish",
                    "github": "https://github.com/markdalgleish"
                }
            }
        },
        {
            "id" : "THE-END",
            "nameslug" : "michele__bertoli",
            "title" : "Interview with <NAME>",
            "date" : "2017-xx-xx",<commit_msg>updated interview date<commit_after>{
    "project": {
        "title": "To BEM or not to BEM",
        "description": "a series of interviews on BEM methodology",
        "basepath": "http://www.didoo.net/to-bem-or-not-to-bem"
    },
    "interviews": [
        {
            "id" : "01",
            "nameslug" : "christoph__reinartz",
            "title" : "Interview with <NAME>",
            "date" : "2016-05-06",
            "status" : "public",
            "quote" : "BEM was not designed to be pretty but to scale. In general I think it is quite bulletproof. And it helped us a lot.",
            "interviewee": {
                "avatar": "img/christoph+reinartz.jpg",
                "fullname": "<NAME>",
                "minibio": "ux engineer & frontend architect, fullstack css developer, team lead ui/ux engineering at trivago",
                "links": {
                    "website": "http://www.creinartz.de",
                    "twitter": "https://twitter.com/pistenprinz",
                    "github": "https://github.com/creinartz"
                }
            }
        },
        {
            "id" : "02",
            "nameslug" : "razvan__spatariu",
            "title" : "Interview with <NAME>",
            "date" : "2016-05-15",
            "status" : "public",
            "quote" : "BEM does not translate to “making sense of things”. If it's a logical decision that can be understood and extended by anyone in your team just by reading the code/documentation, then it's the right decision. And don't assume it will auto-magically solve your scalability issues. It is a good start, but there is a lot of work to be done.",
            "interviewee": {
                "avatar": "img/razvan+spatariu.jpg",
                "fullname": "<NAME>",
                "minibio": "frontend engineer at Funding Circle UK<br>co-organiser of london sass meetup",
                "links": {
                    "twitter": "https://twitter.com/RazvanSpatariu",
                    "github": "https://github.com/RazvanDH",
                    "codepen": "http://codepen.io/RazvanDH/"
                }
            }
        },
        {
            "id" : "03",
            "nameslug" : "sam__thurman",
            "title" : "Interview with <NAME>",
            "date" : "2016-06-15",
            "status" : "public",
            "quote" : "I have preached BEM, and I think it's a good solution to a lot of CSS semantic issues. But I think having a well documented naming scheme is more important than having a perfect one, and being dogmatic doesn't help anyone.",
            "interviewee": {
                "avatar": "img/sam+thurman.jpg",
                "fullname": "<NAME>",
                "minibio": "front end developer working at the intersection of development and design at BuzzFeed",
                "links": {
                    "website": "http://www.samthurman.com/",
                    "twitter": "https://twitter.com/sam_thurman",
                    "github": "https://github.com/samthurman"
                }
            }
        },
        {
            "id" : "04",
            "nameslug" : "micah__godbolt",
            "title" : "Interview with <NAME>",
            "date" : "2016-06-22",
            "status" : "public",
            "quote" : "While I really like the flat selector approach that BEM defines, I prefer to not clutter my elements with a bunch of classes. My decision was then to use data attributes to apply my modifiers and contexts.",
            "interviewee": {
                "avatar": "img/micah+godbolt.jpg",
                "fullname": "<NAME>",
                "minibio": "frontend architect, blogger, podcaster, trainer, speaker<br>author of Front End Architecture for Design Systems",
                "links": {
                    "website": "https://micah.codes",
                    "twitter": "https://twitter.com/micahgodbolt",
                    "github": "https://github.com/micahgodbolt"
                }
            }
        },
        {
            "id" : "05",
            "nameslug" : "varya__stepanova",
            "title" : "Interview with <NAME>",
            "date" : "2016-07-12",
            "status" : "public",
            "quote" : "If you have to imagine this kind of pain, think about new versions of Bootstrap. And multiply it by 1000 due to the bigger size of the library and the amount of projects. These were the problems which BEM offered to solve.",
            "interviewee": {
                "avatar": "img/varya+stepanova.jpg",
                "fullname": "<NAME>",
                "minibio": "Frontend developer for Zalando. Previously: SC5, TMG and Yandex. React lover, BEM adept and a cat fan",
                "links": {
                    "website": "http://varya.me/",
                    "twitter": "https://twitter.com/varya_en",
                    "tech blog": "http://varya.me/en/posts/"
                }
            }
        },
        {
            "id" : "06",
            "nameslug" : "adam__onishi",
            "title" : "Interview with <NAME>",
            "date" : "2016-08-05",
            "status" : "public",
            "quote" : "BEM fits so easily with the way I want to write CSS now. I’ve been focusing more on a component based architecture long before I joined the Origami team, and for that BEM just makes sense.",
            "interviewee": {
                "avatar": "img/adam+onishi.jpg",
                "fullname": "<NAME>",
                "minibio": "Front-end developer working in the Origami team at the Financial Times in London. Co-creator of 12 Devs of Xmas and author of the book Pro WordPress Theme Development.",
                "links": {
                    "website": "http://adamonishi.com/",
                    "twitter": "https://twitter.com/onishiweb",
                    "github": "https://github.com/onishiweb"
                }
            }
        },
        {
            "id" : "07",
            "nameslug" : "stephanie__rewis",
            "title" : "Interview with <NAME>",
            "date" : "2016-11-16",
            "status" : "public",
            "quote" : "Though nothing is perfect, I really appreciate the way BEM's structure makes it easy to tell at a glance exactly how selectors relate to each other.",
            "interviewee": {
                "avatar": "img/stephanie-rewis.jpg",
                "fullname": "<NAME>",
                "minibio": "Principal UI Developer at Salesforce Lightning Design System. Front-end developer, passionate about web standards and accessibility, speaker and author.",
                "links": {
                    "medium": "https://medium.com/@stefsull",
                    "twitter": "https://twitter.com/stefsull",
                    "github": "https://github.com/stefsullrew"
                }
            }
        },
        {
            "id" : "08",
            "nameslug" : "jof__arnold",
            "title" : "Interview with <NAME>",
            "date" : "2016-01-10",
            "status" : "public",
            "quote" : "BEM definitely promotes more CSS. We've moved away from it for that reason.",
            "interviewee": {
                "avatar": "img/jof-arnold.jpg",
                "fullname": "<NAME>",
                "minibio": "Frontend developer, Y Combinator alumnus and one of the humans at BOTS.sh. When not at his desk he can be found on his bike or staring at art.",
                "links": {
                    "website": "http://www.jofarnold.com/",
                    "twitter": "https://twitter.com/JofArnold",
                    "github": "https://github.com/JofArnold"
                }
            }
        },
        {
            "id" : "09",
            "nameslug" : "katia__utochkina",
            "title" : "Interview with Kat<NAME>",
            "date" : "2017-01-24",
            "status" : "public",
            "quote" : "I think BEM is easy to pick up. It is very logical. It also allows for better code readability. I think it makes my code more consistent and logical.",
            "interviewee": {
                "avatar": "img/katia-utochkina.jpg",
                "fullname": "<NAME>",
                "minibio": "A budding software engineer, recently converted to a programming career from a journalism background. Codebar student. In love with HTML/CSS, JavaScript and Python.",
                "links": {
                    "website": "https://katia-utochkina.github.io/",
                    "blog": "http://iheartcoding.herokuapp.com/",
                    "github": "https://github.com/katia-utochkina"
                }
            }
        },
        {
            "id" : "10",
            "nameslug" : "mark__dalgleish",
            "title" : "Interview with <NAME>",
            "date" : "2017-02-01",
            "status" : "public",
            "quote" : "One of the most exciting things about CSS Modules for me is that it takes the principles behind BEM, but makes it look and feel like regular global CSS.",
            "interviewee": {
                "avatar": "img/mark-dalgleish.jpg",
                "fullname": "<NAME>",
                "minibio": "CSS Modules co-creator, MelbJS organiser. Full-stack ECMAScript addict, interaction craftsman + coffee drinker. DesignOps Lead at SEEK.",
                "links": {
                    "website": "http://markdalgleish.com/",
                    "twitter": "https://twitter.com/markdalgleish",
                    "github": "https://github.com/markdalgleish"
                }
            }
        },
        {
            "id" : "THE-END",
            "nameslug" : "michele__bertoli",
            "title" : "Interview with <NAME>",
            "date" : "2017-02-07",
{'fraction_non_alphanumeric': 0.12857142857142856, 'fraction_numerical': 0.011613566289825282, 'mean_word_length': 1.5711454617518827, 'pattern_counts': {'":': 170, '<': 49, '<?xml version=': 0, '>': 49, 'https://': 42, 'lorem ipsum': 0, 'www.': 8, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5792122', 'n_tokens_mistral': 5706, 'n_tokens_neox': 5249, 'n_words': 1617}