import ApiError from './ApiError';
interface NotFetched {
kind: 'NotFetched'
}
interface IsFetching {
kind: 'IsFetching'
}
interface Fetched {
// inspired by https://github.com/tj/git-extras/blob/master/bin/git-line-summary | |
const util = require("util"); | |
const exec = util.promisify(require("child_process").exec); | |
const execSync = require("child_process").execSync; | |
const DIR = "/Users/poshannessy/FB/code/react-clean"; | |
const REF = "origin/master"; | |
const AUTHOR = "Paul O’Shannessy"; | |
const PERIOD_DAYS = 1; |
I bundled these up into groups and wrote some thoughts about why I ask them!
If these helped you, I'd love to hear about it!! I'm on twitter @vcarl_ or send me an email [email protected]
https://blog.vcarl.com/interview-questions-onboarding-workplace/
- How long will it take to deploy my first change? To become productive? To understand the codebase?
- What kind of equipment will I be provided? Will the company pay/reimburse me if I want something specific?
DISCLAIMER: I'm quite new to Qt, QML and SailfishOS development.
But after researching for a while, I didn't find a flawless way to test QML applications.
- testing framework: QtTest with
TestCase
QML type- write tests in javascript
- tests can be run in 2 different ways:
- C++ harness with
QUICK_TEST_MAIN
macro
- C++ harness with
- qmltestrunner (separate program, can be depended on as a package)
This is a CFP for ReactiveConf 2017's open call for Lightning talks. If you'd like to see this talk become a reality, please ⭐ star this gist. #ReactiveConf
// paste this to chrome console on anybody's twitter page | |
// and it'll turn into an instant presentation :) | |
(function TweetPresent() { | |
const presenter = $(`<div id="tpd" style=" position: fixed; top: 0; left: 0; height: 100vh; width: 100vw; padding: 10vh 10vw; box-sizing: border-box; background-color: white; font-size: 5vw; text-align: center; z-index: 9999; display: flex; align-items: center; justify-content: center;"></div>`); | |
const tweets = $$(`div.tweet p.js-tweet-text`) | |
.map(el => el.innerHTML) | |
.map(t => ({t, s: Math.random()})) | |
.sort((a, b) => a.s > b.s ? -1 : 1) | |
.map(c => c.t); |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
⇐ back to the gist-blog at jrw.fi
Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso