- Because you're on a greenfield project, you have the option to use Python3. Seriously consider it - you lose access to a few old, less-maintained libraries, but you gain infinitely less Unicode woes, which was the big change from python to python3
- To parse DAT XML, you're going to want to look at lxml and BeautifulSoup. lxml provides the Proper Parser For XML, and BeautifulSoup sits on top of it and does things like "does its best to guess at how to deal with broken xml" and "provides a pretty, pythonic search interface".
- Django comes with so much User Auth out of the box. There's a pre-baked User model that you should use as your core 'user' model. There are pre-built views providing login, registration, and password-reset. Because there's a pre-cooked User model that the system provides for you, and it might not always have all of the fields that you need to attach to a user, a common pattern is to create a "UserPreferences" application, containing just the one UserPreference model, and views t
- What exactly, would you say it is that HR does, here? I think, as far as I can understand from the Wikipedia article, it's:
- Providing a fair, unbiased mediation process for employees experiencing conflict, particularly the kind of conflict that can end in costly lawsuits or negative media attention. (Sexual harassment, discrimination, accusations of nepotism...)
- Preventive maintenance, so that (Sexual harassment, discrimination, nepotism...) is less likely to occur.
- Recruitment, analysis of such. (How many people are applying here? Why so few techies? Is something scaring them off?)
- Retention, analysis of such. (What's churn? Why are so many people leaving?)
- Hiring, analysis of such. (More anti-sexual-harassment/discrimination/nepotism layers here)
- If there's a union, Dealing With Union Bullshit (generally ignored in software)
- If there's government regulation dealing with employment law, making sure those regulations are being followed. (generally ignored in software)
#!/bin/python3 | |
# -*- coding: utf-8 -*- | |
""" | |
Intro | |
----- | |
 | |
Hi, I'm Curtis Lassam! | |
I'm awesome! |
If you think THAT's impressive, wait'll you see the upcoming Blackberry watch. It weighs over 10lbs, 9 of which are semi-precious metals
The upcoming Blackberry Watch will have falcon wing doors.
The upcoming BlackBerry watch was designed as a luxury piece, which is why it contains over 6 ounces of precious, precious bauxite
The upcoming BlackBerry watch will be preloaded with a surprisingly good spoken-word William Shatner album
The upcoming BlackBerry watch can be used to auto-pay at over 500 Tim Hortons locations worldwide. (498 of which are in Canada)
Cube Drone: Walt, why in the world are we working for a Telecom?
Walt: When a lioness chases after a herd of antelopes, she doesn't chase the strong ones - she chases the slow, weak, old ones who are no longer useful to the pack.
Cube Drone: And we're the lionesses? Walt: What? No, I was watching Animal Planet on my iPhone.
/* | |
* scep.c -- scep command line client | |
* | |
* (c) 2001 Dr. Andreas Mueller, Beratung und Entwicklung | |
* | |
* $Id: scep.c,v 1.13 2002/02/25 23:01:06 afm Exp $ | |
*/ | |
#include <stdlib.h> | |
#include <stdio.h> | |
#include <config.h> |
After a local VanJS meetup, my friends and I were tossing around project ideas. Someone referenced a website that would procedurally generate terrible ideas for video games. "A tycoon game where you draw horses indefinitely".
What a wonderful, terrible, awful idea for a game.
In this presentation, we go through the 1000 lines of Javascript and two weeks of drunken after-work coding required to produce the world's only horse drawing tycoon simulator, with Canvas, Twitter integration, the legendary HorseHash™ algorithm, HorseCurrency™, and HorseStamps®!
You'll pay for the whole seat but you'll only need the edge.
Marketing Survey:
- Salary: $250,000+
- Gender: Female
- How did you hear about us: Radio Ad
Cube Drone is sitting at his computer "Submit, Submit, Submit, Submit, Submit"
Walt (to Milo): "I think Cubes has been modifying our architecture diagrams on the wiki." | |
Long middle panel: | |
(Take an openstack architecture diagram and write your own notes over top of it. Be as silly as you want.) | |
Milo: "No, that's just OpenStack." |
- Create a list of skills that you feel would be valuable to the team. ("Android Development", "Conflict Resolution", "Ability To Eat Many Hot Dogs") For each skill, decide which member of your team would be best equipped to evaluate that skill.
- For each skill, have the subject-matter-expert on your team prepare two to three open-ended non-trivia questions about that skill. ("How many hot dogs would you say that you can eat?" "Describe a time when you have eaten many hot dogs.")
- Prepare a five-point scale for every skill, with a loose definition of what a person should be expected to know for each point on the scale.
- Pick a language that nobody has ever programmed in, ever, like Rust, Eiffel, O'Caml, or M.
- Choose a trivial problem space that is very well defined, like "Scoring Poker Hands", or "Scoring Yahzee".
- Think of a single thing to change about the problem space, after the fact. "2s are now wild".
- Let your prospective candidate know every step in the hiring process from the get-go, wi