Peter Naur's classic 1985 essay "Programming as Theory Building" argues that a program is not its source code. A program is a shared mental construct (he uses the word theory) that lives in the minds of the people who work on it. If you lose the people, you lose the program. The code is merely a written representation of the program, and it's lossy, so you can't reconstruct
<?xml version="1.0" encoding="utf-8" ?> | |
<TrustFrameworkPolicy xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | |
xmlns:xsd="http://www.w3.org/2001/XMLSchema" | |
xmlns="http://schemas.microsoft.com/online/cpim/schemas/2013/06" | |
PolicySchemaVersion="0.3.0.0" | |
TenantId="yourtenant.onmicrosoft.com" | |
PolicyId="B2C_1A_Identifier_signin" | |
PublicPolicyUri="http://yourtenant.onmicrosoft.com/B2C_1A_Identifier_signin" | |
DeploymentMode="Development" | |
UserJourneyRecorderEndpoint="urn:journeyrecorder:applicationinsights"> |
import React, { Component } from 'react'; | |
import { WebView, BackHandler } from 'react-native'; | |
export default class WebViewMoviezSpace extends Component { | |
constructor(props) { | |
super(props); | |
this.WEBVIEW_REF = React.createRef(); | |
} | |
componentDidMount() { |
version: '2' | |
services: | |
api: | |
build: . | |
command: npm run watch | |
volumes: | |
- .:/code | |
- /code/node_modules # Protects this path on api from being mounted with node_modules from local machine |
This recent reddit thread reveals discontent among the web development community about the sheer volume of stuff in a typical node_modules
dir. 140MB in this case!
Opinions in the thread varied from "I'm surprised npm even works" to "everything is fine". I'm not going to offer an opinion, just these two observations:
node_modules
dirs typically do contain lots of stuff that doesn't need to be there.- The latest version mitigates overall size by flattening the dependency tree, but some of the bloat is beyond npm's control.
Use Ubuntu 14.10.
Wifi driver: http://chrono.i0i0.me/firmware/usb8797_uapsta.bin
( Personal mirror of http://git.marvell.com/?p=mwifiex-firmware.git;a=blob;f=mrvl/usb8797_uapsta.bin
, to be wgettable. Apart from that, the original link does not seem to be correct, maybe corrupted.)
Put this file in '/lib/firmware/mrvl'. ( Create the directory if it doesn't exist already. )
Kernel 3.17.6 for better wifi stability and for the cover.
- Create a new directory;
mkdir Apple\ Enterprise
cd Apple\ Enterprise
- Generate a certificate signing request
openssl req -nodes -newkey rsa:2048 -keyout ios_enterprise.key -out CertificateSigningRequest.certSigningRequest
#!/usr/bin/env python | |
def curry(func): | |
""" | |
Decorator to curry a function, typical usage: | |
>>> @curry | |
... def foo(a, b, c): | |
... return a + b + c |
def get_count(q): | |
count_q = q.statement.with_only_columns([func.count()]).order_by(None) | |
count = q.session.execute(count_q).scalar() | |
return count | |
q = session.query(TestModel).filter(...).order_by(...) | |
# Slow: SELECT COUNT(*) FROM (SELECT ... FROM TestModel WHERE ...) ... | |
print q.count() |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.