This document now exists on the official ASP.NET core docs page.
- Application
- Request Handling
<html> | |
<head> | |
<link rel="stylesheet" href="https://pyscript.net/latest/pyscript.css" /> | |
<script defer src="https://pyscript.net/latest/pyscript.js"></script> | |
</head> | |
<body> | |
<h1>Some places I have visited over the years:</h1> | |
<div id="folium"></div> | |
<py-config> | |
packages = ["folium"] |
This document now exists on the official ASP.NET core docs page.
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't really have SREs and they make engineers pretty much do everything,
public void saveMap() | |
{ | |
IMapDocument mapDocument = new MapDocumentClass(); | |
mapDocument.Open("C:\\temp\\Teste.mxd", string.Empty); | |
//if (mapDocument.get_IsReadOnly(@"[path to your .mxd]")) | |
//{ | |
// System.Windows.Forms.MessageBox.Show("Map document \"" + @"[path to your .mxd]" + "\" is read only!"); | |
// mapDocument.Close(); | |
// return; | |
//} |
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset='utf-8' /> | |
<title></title> | |
<meta name='viewport' content='initial-scale=1,maximum-scale=1,user-scalable=no' /> | |
<link href='https://unpkg.com/[email protected]/dist/mapillary.min.css' rel='stylesheet' /> | |
<link rel="stylesheet" href="https://openlayers.org/en/v5.2.0/css/ol.css" type="text/css"> | |
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.css"> |
import { useState } from 'react'; | |
export function useCounter(initial = 0) { | |
const [count, setCount] = useState(initial); | |
return [count, () => setCount(count + 1)]; | |
} |
Assume IIS is installed. My machine already had IIs 8.5. | |
Install Python | |
============== | |
1. Download web installer (Python 3.6.3). | |
2. Run as Administrator. | |
3. Select custom installation for all users. | |
4. Choose install directory such that there are no white spaces in the path. Not sure if it needs to be done. Just being cautious. | |
5. Check the box for "Add Python 3.6 to PATH". |
Once you are ready to hire a developer, what should you do to mitigate execution / build risk?
Writing a good functional specification is key to getting the build phase of this project right. It's not easy to do but it's mostly just about thinking hard and writing out all the boring details of your desired outcome. The best guide for this is Joel Spolsky (recently sold Trello for $425M). He wrote a 4 part series on this, starting here, and also has an example (real) spec on his website here (the PDF link is broken, this is the real one)
Before you start on a spec, trim down your functionality to the absolute bare minimum - and be brutal with it! Imagine you had to complete it in one day, or imagine it was only a single feature... take away everything that isn't fundamental
This is an anchor-linked version of the excellent, amazing original opus magnum by Michael Tandy.
Counterexample: Royal Opera House, Covent Garden, London, WC2E 9DD, United Kingdom.
Counterexample: 1A Egmont Road, Middlesbrough, TS4 2HT