The old version of this post was stupid. Just use https://github.com/nxadm/rakudo-pkg
This is not a pipe.
This is not the painting entitled “The Treachery of Images” by Rene Margritte.
This is an image of the painting “The Treachery of Images” by Rene Margritte.
This is not a number.
This is a piece of text containing numerals, symbols which have numeric values associated with them, each individually, and also together as a whole.
Parsing is the process of interpreting the representation of an idea to get at the idea itself.
I’ve been a big podcast listener for several years. Here’s roughly the current list of podcasts I subscribe too, organized by how vehemently I recommend them.
Everyone Must Listen To
These are so good, it’s not worth explaining why, just listen to:
- This American Life 🔗
- Radiolab 🔗
- 99 Percent Invisible 🔗
- Freakonomics Radio 🔗
- Serial 🔗
- The Moth 🔗
- Invisibilia 🔗
- More Perfect 🔗
- Planet Money 🔗
- Tim Hartford 🔗
- Flash Forward 🔗
- BBC Analysis 🔗
- TED Radio Hour 🔗
- EconTalk 🔗
- Embedded 🔗
- BBC World Service Documentaries 🔗
- It’s downright humbling to realize how diverse the world is.
- BBC Seriously… 🔗
- This one gets extra credit for being so sonically interesting.
- Seminars about Long Term Thinking – The Long Now Foundation 🔗
I also listen to
Which is a recommendation in itself, just less strongly than the above.
- ProPublica 🔗
- C-Span After Words 🔗
- NPR Story of the Day 🔗
- Codebreaker 🔗
- Intelligence Squared 🔗
- The Infinite Monkey Cage 🔗
- Reply All 🔗
I don’t really listen to these, but that’s no fault of theirs. They are worth checking out.
I know nothing about design but this is a great logo. The two circular arcs that make up the body and antennae create a partial Venn diagram, referencing the set theory and relational algebra that form the theoretical foundation for this and any relational database. The shape on the back of the cockroach evokes a funnel, the universal symbol for filtering: a fundamental database operation.
I’ve considered both rebase- and merge-based workflows for my projects, and I’ve come up with an alternative I’d like to propose as an enhancement to git.
I propose a command that would behave according to this pseudocode:
git rebase <original target>
else if (rebaseWithoutConflictsPossible())
git rebase <original target>
git rebase <conflicting commit>~ # the parent of the conflicting commit
git merge <original target>
This has the following benefits:
- It results in a clean history whenever possible
- It highlights conflicts better than merging or rebasing
Traditional techniques in git are terrible at documenting conflicts. Conflicts are not easy to deal with. By their nature, they are encountered by only half of the people responsible for them. A prudent team should always review conflicts. In the best case, the conflict was preventable and the instigator needs to learn how to avoid creating conflicts going forward, e.g. by pulling more frequently, formatting frequently edited constants across multiple lines, or picking a random position for inserting new cases to frequently edited switch statements. In the typical case, at least both parties to a conflict should review the resolution.
A typical rebase completely hides conflicts, except when a user is diligent enough to document them in the commit message, although even in that case they will hardly pop out. It’s not even totally obvious where a rebase, successful or not, has happened. You have to notice that a commit has two different timestamps for when it was committed versus authored, and even then it might have been because it was cherry-picked.
A merge is almost as bad at documenting conflicts.
gitk doesn’t show the changes introduced by a merge commit. This is bad news, because it allows totally new changes to be hidden in merge commits.
This technique serves to highlight conflicts in history. Any divergence+merge was a conflict. It sticks out like a sore thumb. And relative to a merge-only workflow, you still have an easy to follow, mostly linear history.
This strategy is also optimal in the rare but possible case in which a rebase encounters a conflict that a merge would not have. This happens when a conflicting change exists in an intermediate commit in one branch, but a subsequent commit leaves the tip of the branch in a state that doesn’t conflict. It should be clarified then, that a merge will happen anytime there is a rebasing conflict. It does not mean the conflict had to be resolved manually. In that case these merges will show up as sort of false-positives of truly bad conflicts, but I believe this is still the best that could be hoped for.
This could be implemented as an option to rebase. If it were to implemented as a separate git command, or for those who would prefer to alias it, I propose the name
git freebase as it is similar to rebase, but it allows the user to be free of the fear of poorly resolved conflicts hidden in history.
Note: this author does not condone (nor condemn) the use of drugs.
My twitter account got hacked. I needed a way to bulk unfollow the 700 accounts I was now following. I installed the command line twitter client
twidge and used a little shell-fu to unfollow 20 accounts at a time
twidge lsfollowing | xargs -L 1 twidge unfollow
I then looped it automatically with the
watch command, resulting in
watch -n 10 "twidge lsfollowing | xargs -L 1 twidge unfollow"
This unfollowed the newest accounts first, so I was able to catch it before it unfollowed the accounts I really care about.
- Learn from our mistakes by following the instructions below
- Install Drupal 7 via easiest method available, i.e. Softaculous
- Mind Drupal’s helpful warnings to stop from leaving open security holes
- Install CiviCRM module in Drupal
- Install Sunlight integration (Drupal module)
- Enable lookup of CiviCRM contacts by Congressional District
- Enable CiviCRM Mapping and Geocoding
- Import your Contacts
- Famaliarize yourself with the immense capabilities of CiviCRM
The easiest way to save money is to trick yourself into thinking you have less than you do, and saving the difference. Any time you think you have money, you’re liable to think you can spend it.
This trick is based on the quirkiness of the calendar. If you get paid every other week, then it’s easy to assume that you get two paychecks per month, and you can base your budgets on that. The truth is that there are 52 weeks in a year and you’re only assuming there’s 48. So in fact twice a year you’ll have a month with 3 paychecks. If you can save these two entire checks, that puts you at a 7.7% savings rate, or even higher if you have your retirement contributions or other savings automatically deducted.
Most of these ideas could be combined into a unit that would basically resemble ceiling-mounted track lighting. Each “light” would be able to aim itself and would contain some of the following modules.
- Kinect-like cameras analyze volume of vessels and their contents
- This camera could track your actions to a degree
- Projectors project lines on inside of vessels to show you how much of an ingredient to add
- Voice controlled “assistant” (read Siri) walks you through recipes, responds to:
- “How much flour do I add?”
- “What do I do next?”
- “The chicken is in the oven. Set the timer”
- Assists in timing multiple recipes to be completed at the same time.
- UV light reveals unclean surfaces
- UV light used to sanitize surfaces (maybe just when no one’s in the kitchen)
- IR thermometer measures temperatures, which are then projected onto the cooking surface
- Sensors smell for burning (I now realize this is basically a smoke detector but I think we could do better if we designed a new gadget around this use case.)
- Camera to upload photos of food to social media for bragging rights.
- Cameras to record video of cooking process for tutorials or to capture entertaining mistakes.
The nice thing about this track lighting unit is that it’s relatively easily retrofittable into an existing kitchen and doesn’t require you to toss existing gadgets. A major flaw I’ve noticed in futurology is the temptation to assume that you can start from scratch. But the way things really work is that technology creeps forward by maintaining a degree of backwards compatibility. Products that require large investments don’t succeed in the market. Also the modularity of this design is nice because some technologies will reach marketability before others.
Besides this device, every surface would be a scale, especially stove-top burners and including oven racks.
Cooking appliances could be programmed by temperature vs. time graphs which would be downloadable from the internet and allow different temperatures over the course of cooking, and adapt to the temperature of the food (like microwaves already do) and also the weight of the food.
I think the sort of assistance this provides allows the cook to feel like they still have ownership of the cooking process, as opposed to more automation based technologies that can rob one of that satisfaction. I’m reminded of the story of the boxed cake mix that failed when it only required the baker to add water, but was successful when it required the addition of an egg (although for that I think you must also factor in the distrust of the artificialness of a product that used to require perishable ingredients and is now made to be shelf-stable).
While it is a notoriously hard problem to do image analysis to figure out what the ingredients are that you are working with, I think it would be fairly easy to tell the system “I’m measuring the flour” and then it would just have to track the location of the measuring cup. If it can do this, it can track your progress through a recipe and warn you if you do things out of order or forget a step. This would be one of the hardest things to get right because people hate being condescended to by technology.