The Span API does not at this time require any authentication. This will probably change in the future.
Description: Gets panel summary, firmware version, door state, serial number, network status Request: GET /api/v1/status Response:
{
"software": {
"firmwareVersion": "spanos2/r202216/04",
| Copy all the files to the build directory. | |
| Copy icudtl.dat to the build directory. (you can find it in the vscode downloads ex for linux). | |
| chromium version in port is 52.0.2743.116. | |
| This was built with FreeBSD 11.0-RELEASE-p1. If building with other versions probably need to change | |
| the freebsd versions in diff files (ex. freebsd11 => freebsd10) | |
| Installed | |
| node => v6.9.1 | |
| npm => 3.9.2 | |
| >chmod 755 vscode_build.sh |
| <link rel="stylesheet" href="/css/instagram.css" type="text/css" /> | |
| <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js"></script> | |
| <script src="https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.18/jquery-ui.min.js"></script> | |
| <div class="instagram"></div> | |
| <div class="load-more btn">Gimme more photos...</div> | |
| <div class="error">Oops, there was an error getting the photos...</div> | |
| <script src="/js/instagram.js"></script> |
| { | |
| "vars": { | |
| "@gray-base": "#000", | |
| "@gray-darker": "lighten(@gray-base, 13.5%)", | |
| "@gray-dark": "lighten(@gray-base, 20%)", | |
| "@gray": "lighten(@gray-base, 33.5%)", | |
| "@gray-light": "lighten(@gray-base, 46.7%)", | |
| "@gray-lighter": "lighten(@gray-base, 93.5%)", | |
| "@brand-primary": "darken(#428bca, 6.5%)", | |
| "@brand-success": "#5cb85c", |
“Talk is cheap. Show me the code.” — Linus Torvalds
Free Code Camp offers 1,200 hours of interactive coding challenges. These are 100% focused on the practical skill of building software. You code the entire time. You learn to code by coding.
You can learn theory through free online university courses. Free Code Camp will focus instead on helping you learn to code and practice by building apps.
With that practical focus in mind, let’s talk about the requirements for our coding challenges. (Note that these requirements do not apply to our algorithm challenges, checkpoint challenges, or projects.)
| license: gpl-3.0 | |
| height: 960 |
| 'use strict'; | |
| const http = require('http'); | |
| function addGracefulShutdown(server) { | |
| const oldClose = server.close; | |
| const connections = {}; | |
| let shouldDestroy = false; | |
| let connectionId = 0; | |
| function destroy(socket) { |
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".
I hereby claim:
To claim this, I am signing this object:
