Showing posts with label no-gender. Show all posts
Showing posts with label no-gender. Show all posts

Sunday, September 7, 2014

#YesAllProfessions

Recently, I've seen an uptick in articles about how people in various non-engineering/science professions should learn to code. From MBA students learning to code to know their business better to law students learning to think like a lawyer by first learning to think like a system designer, the cognitive benefits of learning to code are obvious. Fields such as finance are so heavily tied to data-driven processes that one venture fund actually put an algorithm on its board.  

While simply knowing how to program has myriad benefits even if you never write another line of code in your life, once you know how to code you are more likely to identify ways in which writing code can help you do your (non-tech) job.

You won't find writing software anywhere in my job description, but if I were to list all of the times I've written a computer program to help me better perform my job, I'd be writing all day. Writing code allows me to sift through large amounts of data to help myself and my colleagues make better decisions.   I make maps, graphs, lists, and summaries by writing short programs that we would otherwise either enlist interns to devote time making or would otherwise be unable to do entirely.

These programming tasks are often very small - sometimes taking just minutes to complete, and rarely more than a few hours.  Just to explain the problem to a non-lawyer developer would often take as much time as it takes me to write the program because I have the benefit of having both a complete understanding of the problem and the skills necessary to solve it.

This is, I'm sure, part of why V. David Zvenyach is writing a free online Coding for Lawyers book. While computer science is a complex and challenging field, learning to write simple programs it not hard.  I encourage everyone to take advantage of various free online resources to learn to code, such as the Code Academy or the Hour of Code exercises on code.org.

Wednesday, April 2, 2014

The Intern Hiring Conundrum

When I say "STEM is for Everyone," I mean it.  STEM is not just for people who do STEM - problems that come up in our daily lives can be solved with the techniques we learn by studying STEM.  When you hear "economics," don't think "price of wheat in a drought," think "hiring interns."

Here's why.  A friend came to me with a problem her organization is having hiring interns. There are 7 divisions in her organization, and it used to be that each division handled intern hiring independently.  Too often multiple divisions would end up giving offers to the same candidates, which confused the candidates and made it harder for the divisions to predict yield (that is, the percentage of candidates that will accept offers).

So a couple of years ago they switched to a coordinated hiring process, where each of the divisions would select their preferred candidates and representatives from each of the 7 divisions would sit in a room to resolve any conflicts.  But these meetings could get very heated and led to inter-divisional conflicts.  So they want to take emotions out of the process and develop a fair system allocate candidates between the divisions.

Economists will recognize this as a matching problem.  Matching is a very complex problem - indeed, a matching algorithm was one of the accomplishments that led to the 2012 Nobel Prize in Economic Science for Lloyd Shapley and Alvin Roth.  For various reasons, the organization is not going to use candidate preferences in making division assignments, which helps simplify the system to a more traditional resource allocation problem.  Drafts, lotteries, and auctions are all mechanisms for allocating scarce resources.  Picking the right system will help you get the right interns to the right groups.  To figure out which is the right system, you need to understand your objectives and constraints, and how each system handles your situation.  After the jump, I go through some of the possible intern assignment systems and their pros and cons.

I should point out that I have not studied either economics or game theory extensively - I find these issues fascinating, but true experts would have a lot more to say about this.

Wednesday, March 26, 2014

Tech or Something Else? Why Not Both?

Talking to high school students, one of the most common things I hear is in the form "I really like [STEM field] but I have a passion for [arts/humanities field]."  As in, "I really love science, but I'm really into music" or "I love math, but I really want to study French."  College catalogs and job descriptions conspire to give people the impression that you have to pick just one field, and nothing could be further from the truth.

Technology touches nearly every aspect of society. Everything from advertising to zoo-keeping has benefited from technology.  The innovations that enable game-changing improvements often come from people who have a passion and experience in two or more fields. Combining substantive knowledge in one area with technical know-how creates a very powerful combination.

Wednesday, March 19, 2014

2^11

Sometimes the best way to learn is to not realize you're learning.  The game 2048 is like that.  The goal is very simple - you combine merge blocks of the same number into one with the combined value.  For example, if you combine two '4' blocks (2^2), you make one '8' block (2^3).  Two '8' blocks make a 16 block (2^4) and so on.  The goal is to create a 2048 block (2^11).  After each move, a block appears randomly somewhere on the board - usually a 2, but sometimes a 4.

This is a very fun and natural way to get comfortable with powers of 2, which is an important concept in computing.  I'm sure the creator of this game did not intend it to be an educational game, but it's just one of the little ways that you can pick up important concepts in unconventional ways.

No, I'm not writing a blog post solely to justify the hours I've wasted playing this game.  Why do you ask?

Friday, March 14, 2014

Pi is for Everyone

Source: Wikipedia
The formulas, jargon, and code in this post may not be the best way to prove that STEM is for everyone, but it's Pi Day, and I think it's good to keep in mind that things we take for granted now were once considered extremely difficult.  According to CNN, it's cool to like pi.

So today, in honor of Pi Day, I decided to refresh my memory and sharpen my programming skills by implementing Viète's Forumla. Viète's formula, developed in 1593, expands on the Archimedes method of approximating pi developed around 250 B.C.  This method relies on computing the circumference of regular polygons with many sides. As you increase the sides of the polygon, it gets closer and closer to being a circle, and thus, the ratio of the perimeter to the "diameter" gets closer to the value of pi.