Quantcast
Channel: the evolving ultrasaurus » general
Viewing all 45 articles
Browse latest View live

why crowdsourced transcription?

$
0
0

I signed up to try out FromThePage as “ultrasaurus” a couple of weeks ago. It’s creator Ben Brumfield (@benwbrum) recognized me from RailsBridge and the NPR story and reached out via Twitter. Ben’s blog, Collaborative Manuscript Transcription is a wealth of information about crowd-sourced transcription.

Jason Shen and I were able to connect on the phone while Ben was in Austin TX at Social Digital Scholarly Editing conference last week. Ben kindly gave us an overview of the landscape of crowd-source transcription projects and the open source software this is behind a few of them. We also got a glimpse of how he got started in this fascinating corner of next generation web tech and why he quit his day job to work on crowd-sourced transcription solutions full-time.

FromThePage started as a family history hobby. As a software developer, he was able to create a web site, originally based on MediaWiki, later moved to Ruby on Rails, to allow other people to help with transcription. Working with his great-great-grandmother’s diaries, he saw how a bunch of people could really do research on a topic together. He was inspired by wikipedia, by the idea of getting a community together — not just to comment, but actually edit, beyond the abilities of a single person. With a wiki format, someone who was a good typist could type it all up, another with special knowledge could make corrections, etc.

Wikipedia used to feature more prominently “what links here” — this is an index. He wanted to use this to figure out a way to link portions of text with other places those subjects are mentioned. He very quickly found mediawiki is not the tool — the difference between text and articles about the text were not clear.

One of the challenges is deciding how to handle the material, what are the guidelines for transcription: encoding abbreviations and incorrect spellings, etc.? There very detailed, technical solutions like TEI, an XML format, and less formal text markup. He started reviewing other systems, posting on his blog, speaking on the topic for the last two years. A number of organizations were interested in using FromThePage. Some people pay, some can’t — it’s open source. After 15 months of doing this full-time, he has worked on enhancements on FromThePage, a new transcription tool for structured data, and other sites built with different tech, based on the needs of the content and the community.

Ben’s personal mission is to transform the landscape of what amateurs do with their own material. Right now, if you are someone who has a lot of old historic papers or diaries. what you do is sit down and write a book about it — and you probably write a crappy book. Ben would like these folks to provide their materials in a way that other people can use it.


crowdsourced transcription landscape

$
0
0

The following is based on an interview with Ben Brumfield, after which I did a bit of research myself, adding links and some additional references.

There are 6 general areas from which people are doing transcription.

  1. Investigative Journalism: crowdsourcing information for citizen investigation. The idea is to get a whole lot of people to flag and inspect information. People type up the information on scanned documents (e.g. receipts, tax returns), transcribing what they see. Then write a total of receipt on a separate page. Basic transcription + high level purpose-built extraction. Gather the data to use it for something. Volunteers are politically motivated.
  2. Bio informatics The archetypical artifact is a plant specimen with a bunch of labels on them — structured data. They are presenting users with a full image, asking people to extract information. No free form text entry. They tend to be more sophisticated in how they represent documents. “Even if you see an error, type what you see.” or select from a menu. Their volunteers are smaller group more informed group, who want to help science and/or love the subject themselves. Participate even if not active physically. Motivated by the immersive nature of transcription — living in that document, you are really “there.”
  3. Library and Archive world – scanned letters, papers and diaries. Much more immersive with a narrative flow, which keeps people coming back. Two goals: 1) improve databases (i.e. finding aids) Plain text transcript can be put into Solr DB. 2) improves findability, will be crawled by Google, & people who don’t know about the material or institution. They are also looking at the outreach perspective. Connect with potential patrons/users. Not just labor, but a service – let your users engage more deeply with collections. Tighter connection = advocates.
    • National Archives launched a transcription pilot project. All of their materials currently online are completed, but they point people to WikiSource where they have a list of images from the National Archives queued up to work on.
    • University of Nebraska Lincoln – launched campaign to transcribe alumni yearbooks.
    • DIYHistory
  4. Literature ScholarsTextGrid, system that was built where all transcription is done off-line in Eclipse, then full transcripts are contributed — this is also a way of giving what scholars already have. Sounds good, but tapping into the scholarly workflow has challenges. For scholars, transcripts are a middle work. They don’t get an incentive for contributing this effort. They typically want everything that has their name on it to be properly cited and looking good. Where that DOES work to some degree is Genealogy (see below). They’ve been doing it for longer and are ok with sharing with a somewhat broader audience. Worry about plagiarism, non commercial use, etc. Not trying to write a book like other scholars.

  5. Geneology – Generally volunteers will first focus on transcribing material about their own ancestors, then stuff about where their ancestors are from, next they move on to generally useful material like the 1940s census, which leads them to communities of like-minded folks. If you offered them the opportunity to transcribe stuff from their own families, they would leap on it. They are working with tabular records: ship records, shareholder lists.
  6. Literary and Historical – A lot of people at the conference seemed to be talking about how to add rich set of markup to indicate things like strikeouts, changes in handwritings, personal names, place names. Taking this approach generally yields small, but quite dedicated, communities of users — their data model is XML, usually TEI XML. They are embedding the information in the document. The majority of the tools that exist are all for that community. FromThePage is in this camp — you can use a lighter wiki markup for proper names, creating an automatic index and cross-linking between pages.

why drupal for georgia.gov

$
0
0

Nikhil Deshpande (@nikofthehill) is the Director of GeorgiaGov Interactive a group within the Georgia state government that provides services to agencies and other government organizations. Today at CapitalCamp he talked about why they chose Drupal for georgia.gov and how they approached the transition.

Georgia.gov, as the website for the Georgia state government, used to be simply a landing page with links. They wanted it to be a front door to wherever you wanted to go in the state government, but people were coming there and falling off. They had a fragmented experience, a fragmented brand. They were running many different CMS’s. They had both platform issues and a design challenge.

Their users don’t look like typical personas. They are trying to be a website for everyone, to serve the whole population. How do they do this? Here are my rough notes on this intriguing talk.

Platform Choice

Since they were running a lot of CMS’s, they knew exactly what they needed:

  1. to have an enterprise element, they were hosting 60-70 websites
  2. cost effective (not saying cheap) — worthwhile, but doesn’t cost as much as others
  3. simple and usable
  4. strong presence in the public sector

Nikhil Deshpande stated that Drupal is the second largest CMS worldwide, 2.1% of the web. [note: w3techs reports Drupal as #3 at 2%, which is still pretty huge, but perhaps Joomla has grown in the past few years.]

Open Source!

Nikhail saw this as opportunity to answer valid questions about open source solutions, since they were moving from mostly proprietary systems.

  • security? high threshold of security since it has so many eyes on it
  • free? how good can it be if it is free? It’s not free. It’s free as in free speech, not free beer.
  • total cost of ownership? you need to implement it and host it

Who uses it?  Huge number of government sites, including go.usa.gov, USDA, NASA, Dept of Justice, USAID, and many more.

You can either implement it yourself or get someone to implement it for you. They sent out a bid and chose Phase 2 as a partner. Then Phase 2 brought in Acquia (started by the founder of Drupal) and mediacurrent. They decided to use OpenPublic platform, which is built very specifically for the government. It’s a distribution of Drupal that you can customize or use out-of-the-box.

  • tailored to the needs of govt
  • security
  • accessibility
  • workflow

Moving from Vignette to Drupal

Content: Oracle to MySQL
Look and feel — not just a migration, decided to do a re-design.
Single code-base, multiple databases
Cloud hosting — all public info, no sensitive data
Search
Mobile ready – 20% of traffic overall (and climbing), some websites up to 45%

Design

Internal team designed the main site, then Phase 2 did the rest of the websites
did heat maps — search 31% clicks, child support 13%, headlines 3.6%

Made it very search centric. They got a Google Search Applicance and indexed all of the Georgia government websites.

55 redesigns?

Nope…

  • template based
  • styletiles as a design methodology
  • demo websites for agencies based on the styletiles

4 main themes — agencies could choose: patriotic, friendly, official, classic

No one really likes change, but if you communicate well it can go smoothly.

56 sites, 8 batches, 150 content managers
Oct 2011 – Sept 2012
on time & budget
Best of Web — 2012 Innovation Award
99.98% Uptime
Savings 4.7MM in 5 years

Takeaways

  • define success
  • communicate & involve (120 people who were trained at content managers, decision-makers, who signed off on the look of the website)
  • carefully select implementation partner, but also build a strong internal team

No one wants to be on the receiving end of a change. It is important to communicate “things are going to be hard for you, but this is what we are doing to make it work.”

responsive design prototyping

$
0
0

A Response-Able Process to Responsive Design talk by Mal Jones (@skeletonjones), Brian Verhoeven (@beverhoeven) and Corey Lafferty (@coreylafferty) introduced their agile process and a new open source prototyping tool that they built.

In 2011, they made responsive default for advocacy sites and content sites. We’re no longer building cars, we’re building transformers. How did they change their process?

Start with mobile story boards, then page description diagram. Pick three things on each page that are important, then three more, then the rest. Involve client in that prioritization — force them to choose.

Agile process. Prototype the unknowns — in the browser. They needed to be able to experiment. They need to be able to see how it looked and felt like on a phone. They looked at a lot of tools, but nothing really met their needs:

  • fast sketching of ideas
  • how elements respond in an actual environment (the web)
  • A/B testing
  • supports iteration

They ended up creating Proty, which can be used by coders and non-coders. If you are a coder, you can edit the HTML, but that isn’t required. Mobile first, breakpoints second (from sass). Each of the responsive sized gets its own file, but they aren’t mutually exclusive.

  • Small gets loaded first
  • Medium only what you need for the medium size that is not in the small (just the diffs)
  • Large, same thing, just what you need in the desktop, that is not in medium + small.

How do we use Proty? we use it first for creating wireframes that are live and responsive to different sizes. You can add notes to the page, for clients or other team members.

We also use Proty for:

  • technical tests / proof of concepts.
  • style guides

This process helped us transition designers to learning HTML and CSS.  Also helps with the agile process where there is overlap between dev and design roles.

Note: prototyping is not a magic way to create a web site once the design is complete.  You still have to build a web site.  If parts can be reused, great!  but that’s not expected.

Responsive design cannot be an afterthought.  It not a feature — it is how you build every feature.  Identify what works on mobile and what doesn’t.  Be able to recognize challenges early with embedded content, such as large document files, large tables of numbers, video, etc.

Brad Frost has a great list of responsive design patterns for navigation.  They like the ”hamburger” menu (love that name for the icon with three little lines that typically triggers the main screen to reveal a side menu — see Path, Facebook, and many others now).

Don’t do the “hide & cry” — just because someone is on a mobile phone, they still deserve to see all of your content!

Notes from the audience:

  • checkout style_guide module.
  • Canvas will be hosting a devicelab in DC in the next few months.

For more info follow: @forumone and @protytype

learning photoshop

$
0
0

I’m back in San Francisco where I can walk my dog in the morning and drive my kid to school. I actually went shopping to buy some of that fresh California produce I missed so much when I was in DC — perhaps I was just shopping at the wrong places. beet-sketch

This particular beet tempted me from the organic vegetables section of the supermarket.

I’m learning PhotoShop (again). I want to be competent with a wide range of tools — not just code. I indulged in the purchase of a pressure-sensitive tablet and experimented with the so-called pencils.

I’m collecting tutorials and tools through my learning path. I was inspired by the Lindsay Norman collection: Web Design for Beginners.

collective intelligence

$
0
0

Most software today cannot be defined purely by the software itself. This new class of software requires data and a community people that create and interact with that data. This is substantially different from first generation software tools, where a person starts with a blank canvas or template and uses the software to create a document, such as PhotoShop, Word or Emacs. Also quite different from software services, where a person uses an online service to perform a transaction, like online banking or e-commerce, or communications software, like email or Skype.

We are more than the sum of our efforts. Software can now enable a collective intelligence. It can be applied without direction for entertainment or social engagement in a social network, like Facebook and Twitter, or to serve an individual purpose, as with crowdfunding platforms, Indiegogo and Kickstarter.

There is also an emerging category of services where humans collectively accomplish something that leads to discovery or allowing our machines to interpret the real world more effectively on our behalf. At Blazing Cloud last year, we called this UGC Science, more generally it’s called crowdsourcing. Thousands of people are participating in dozens of projects that are helping to interpret real world artifacts through crowdsourced transcription, including my current work with the Smithsonian Collections.

This is a trend where data science meets user experience — we’re designing the way humans interact with the software with the goal of creating an outcome larger than an individual could do alone.

public speaking: fear therapy

$
0
0

I joined the Smithsonian chapters of Toastmasters, partly as a way to connect with a new community and partly as the next step in my ongoing effort to conquer my fear of public speaking. People who know me through my online presence or have heard me speak, may be surprised that I have any fear at all. From just a few meetings I’ve already learned much from this incredible Toastmasters group.

Introduction: Sarah Allen. She’s new to our club. She’s a new member, and without hardly any hesitation at all, she signed up to give her first speech, her “icebreaker,” which we’re very excited to hear about. Sarah told me that although she’s had a lot of experience with public speaking, she still has a tremendous fear of public speaking, and the reason she joined the club is so she can pick up some great tips to manage that fear, and actually harness it maybe to be a positive thing. She tells us she would, also, like to learn to not say “um” so much. So, let’s get her up here for her first test. Sarah, is going to speak to us about fear therapy.

Thank you Mistress Toastmaster for that fabulous introduction, and I am going to speak about a different kind of fear, unlike mountain biking, which Don just spoke about.
I’m afraid right now. Maybe some of you have experienced this kind of fear. I am very aware of every inch of my skin. I have this knot in my shoulders, and my neck feels like there’s this nylon string pulling up that just might snap, and my head would then float away. This is absurd. This is an irrational fear, right?

When I was a little girl, I was impossibly shy. I was afraid to talk to people that I didn’t know. I wasn’t even sure I wanted to speak to people that I didn’t know. So, today I will tell you a little bit about my life, and the techniques that I’ve learned, applying what I call “fear therapy,” forcing myself to do things that scare me.

I wasn’t timid in general. I was actually pretty adventurous. For example, I loved to swim. When I was two years old we moved to St. Lucia, and I’m told I went swimming in the ocean every day. When I was five, we moved to Boston, I went swimming in the Mystic Lakes, at the boat club, at the pool, and I loved to go to Cape Cod, especially when the waves were wild before a storm, and I could duck my head underneath and they quiet to this dull roar.

We moved around a lot. I realize I was particularly good at speaking languages, new foreign languages, perhaps because I listened more than most people. In fourth grade, we moved to the Philippines, and my mom tells me that I learned to speak Tagalog in just a few months. The following year we moved to El Salvador, and she would find people who were Filipino and spoke Tagalog and bring them home for dinner, and I would not say more than a few words. Suddenly years later I realized that the Spanish that I learned in El Salvador completely replaced Tagalog. Because I had refused to speak, I completely lost this language. So, I resolved to stop letting my fears prevent me from living the life that I wanted to lead, and being the person that I wanted to be.

The first technique that I share I call “jumping off the cliff.” Just like I would enjoy jumping off a cliff into a pool of water, and I thought that was fun, I would let the experience that I wanted to have pull me through my fear. So, after high school when I studied German, I pushed myself off a cliff, and I moved to Switzerland, where I knew no one, and I became fluent in German, and I practiced turning strangers into friends by actually talking to them.

The second technique I’ll share with you, I call the scripted response. I came back to the states for college, and I became a software developer. I loved the way that symbols and numbers in my mind could turn into sparks of color on the screen, and I made software that made these picture dance. When people asked me what I did for a living, I told them I was computer programmer, and that generated this awkward silence. My boyfriend told me that I should tell people that I made special effects for films, which was sort of true because I made software that helped other people make special effects for films, and it did work much better in conversation. I felt a little dorky by getting by boyfriend help script my conversation, but I learned to speak with words that other people could really understand and connect to. And over time, I’ve developed a lot of these scripts in my head, and they become stories that help me stitch my memories together, and help me connect to new people.

I have many techniques that I can apply in my fear therapy sessions. Since I jumped off a cliff, and decided to go on this six month fellowship at the Smithsonian, I face my fears every day. I’ve always had trouble articulating what exactly I’m afraid of. I felt it must be fear that something terrible would happen, that people would make fun of me, or think badly of me, but it strikes me now, reflecting on this, that it’s a different kind of fear altogether.

Nelson Mandela made famous a quote by Maryanne Williamson that our deepest fear is not that we are inadequate. Our deepest fear is that we are powerful beyond measure. I think I was always afraid that these sparkles that was in my mind would come out as meaningless trivia or bland words that created distance, instead of bringing me closer to people.

Thank you all for creating this group, and this safe space, and I hope that my talk sparks a connection with a few of you today.

Note: Special thanks to Jason Shen for recording my talk

your audience is part of your UX

$
0
0

UX design is a lot like filmmaking. We design an experience.

When you are making a film it is easy to forget that the audience is working too, drawing conculsions and projecting expectations
I was struck by how Jon Boorstin described the design practice in “Making Movies Work: Thinking Like a Filmmaker.” Our audience, their preconceptions, hopes and fears, are the essential part of the experience. They bring context with them. It’s tempting to oversimplify, especially when we attempt to reach a large audience, but our creative works, especially software, sit within a larger world and come to life in the minds of the people who interact with them.


lessons learned and future thoughts

$
0
0

When I was in high school, I thought we were supposed to see clearly into the future, where decisions would be made at regular intervals…

So I began my talk to Louisville High School, an all girls school in Woodland Hills California, where I spoke this past week about my life, my career and some thoughts about the future. When I was in high school, also at an all girls school, I expected to be able to see choices clearly ahead of time. This is not my life.

In my life, those choices that made a difference have only been clear in hindsight.

The visual pun, which I didn’t expect anyone in the audience to understand was that my first slide is a photo of a hall in EEOB, the old Executive Office Building, right next to the white house. It is no longer completely strange for me to walk down those halls as a Presidential Innovation Fellow. This is not my life. It’s a place I’m visiting, while I work to help our government apply technology to solve critical challenges. The straight, official looking hallway is the perfect metaphor for how many adults present the prospect of a bright future to a college prep school student. Life is murkier in reality.

Introduction

I did not plan to have an exciting life as a high tech entrepreneur.

I will talk for just a few minutes about my early life, and how I got started in computer programming, and then the winding path that led me through entrepreneurship, to doing a lot of creative software development.

First, I have some questions for you:

  • Has anyone in the room developed software before? one hand goes up
  • Who has written any code at all? a few more hands are raised, and I ask them to keep their hands up
  • Javascript? …Scratch? …Logo? …?Visual Basic? more hands go up as I mention each language
  • HTML? …CSS? at least half the audience has their hands raised now
  • What about anyone who has written an Excel formula? now we’ve got most of the audience raising their hands
  • Email filters? I guess kids don’t use email much anymore

There’s a spectrum of computer programming. What we’re seeing today is that the advanced features of many software applications require programming skills, even if they don’t call it programming.

I ask if anyone can define software… to tell me and tell their peers, what software is? One kid does a very good job of it. Now they are ready, I think, to hear about some fancy software I’ve created and feel some kind of connection to the process, I hope.

There’s a good chance that every person in this room has used software that I developed and you’ve most certainly seen its effect on the world.

You should know that software is a team sport. I’ve played on some great teams.

What I’m probably most proud of is my work on After Effects. You’ve probably seen the result of After Effects in the movies. This was the first breakout success software that I built.

I also worked on both Shockwave and Flash. I was on the original Shockwave team, and then worked on Flash later.

I will tell you a little bit about how it all happened and how I didn’t see it coming.

Early Life

I was born in New York City. I lived there for two years. My family lived in different places all over the world. When I was in fourth grade, we lived in the Philippines, and I learned Tagalog. I went to a Catholic school, with 2,000 girls, and only two Americans in the whole school.

At that time, the Filipino people generally credited America with giving them their freedom after WWII, and I was treated like a celebrity, which was mostly fun and occasionally mortifying.

I later learned that America actually contributed to the oppressive regime under President Marcos. At that time, Martial Law was in effect. I didn’t really understand what that meant as a kid. There was a curfew, but I had to be home by dark, anyhow.

The next year, we moved to El Salvador, where I became fluent in Spanish, which then completely replaced Tagalog for me. El Salvador, at the time, was in the midst of a civil war. The very, very rich in El Salvador were oppressing the very, very poor — taking away their farms, often killing them, and the United States was providing arms to a corrupt government.

I was horrified by the actions of my country. When I came back to the US, I read in the newspapers that the US was fighting Russian communism in El Salvador. That’s was not what I learned was going on when I was living there. I was dismayed by the incomplete truths and misinformation I read in the newspaper.

As a teenager, I protested on Washington. I got very involved in activism against US foreign policy. I thought that I would have a career in International Relations. I wanted to change the world for the better. I felt that my parents’ generation had created a mess. It was my generation’s responsibility to fix that.

Meanwhile, my mom was laid off from teaching and decided that she was going go into the next big thing and sell computers. She brought home an Apple II, which at that time, came with a BASIC manual. I read the book, followed the steps, and learned how to do high-resolution computer graphics, which looked like this at the time.

I would program the computer to draw lines and I thought this was really neat. A lot of the people that I knew, assumed that I would go into computing as a profession, but I felt that a career in computing would be like having a career in Rubik’s cube. It’s really fun, but is this what you really want do with your life?

I didn’t think at that time that computers could solve any really significant problems in our world. Of course, I was wrong, along with a lot of other people who couldn’t see what was going to happen. Though there were some people that definitely did.

Career Path

Next, I will take you through a very brief tour of my career path. I will specifically highlight four decisions I made that made a really big difference.

From those four decisions, I’ll introduce the four life lessons that I want to impart to you today. I made a thousand, a million, decisions – you never know which decision is going to make a difference, but these are the four that did for me.

Four decisions, four life lessons

My big first decision was picking a college. I decided to go to Brown University. Most people who go to college have no idea what they really want to do. I picked Brown because Brown taught 13 foreign languages. I wanted to learn all of them.

I was really interested in how, when you speak a different language, you think to say different things and it influences your choice of words. It affects the connotation of what you say, and that that is responsible for a lot of misunderstandings in the world.

I audited some languages classes. The modern language classes taught literature, which was interesting but not really my passion, so I didn’t take those classes.

I thought “maybe what I want to study is linguistics.” but the linguistic classes, at the time, at Brown taught dead languages. They taught Latin, Sanskrit, Ancient Greek, which is again, somewhat interesting, but not really my passion. So, I thought “well, maybe I’m not that interested in language”, which absolutely the wrong assessment.

I did hear some great advice: take classes in college based on the teacher, not the subject.

Lesson #1: Learn from Great Teachers

I studied studio art, inspired by my teacher, Marlene Malik, who taught me that to create, we must also see, and that our work does not stop at the edge of the canvas, it is affected by its placement in a room, on a wall — the world provides context.

I also studied computer science which I took as a backup ’cause I figured if I’m getting an art degree, I better do something practical.

I still enjoyed programming, but could not imagine it being my career.

I had taken a year and a half off between high school and college, which caused me to graduate in December. The summer before my last semester, I joined some college friends to start a company called The Company of Science and Art (CoSA).

Lesson #2: Work with Great People

The team that I worked with were really great people. In some ways, these colleagues saw things in me that I didn’t even see in myself.

It had a huge effect on my expectations for the rest of my career, that my first adult work experience was with people who had mutual respect for each other, where we learned things from each other, where we created together. That was a really valuable experience and we ended up creating After Effects together.

I left CoSA right before After Effects was released because I was in love. My then boyfriend and I had decided that we would move across the country when I graduated. I delayed that for a year and a half, but then finally, I said, “Alright, this company, I love it, I’m having fun, but I don’t know if it’s ever really going to pay the rent.” Again, I was wrong about that.

We bought a telephone van and we packed up all our stuff and moved to California. I had gotten a job at Apple Computer, which I thought was pretty hot.

It was for product that they wouldn’t even tell me about when I applied for the job. In networking, which I thought was really interesting. I hadn’t studied that in school, the way that the computers talk to each other. It ended up being the worst job I’ve ever had in my life. It was terribly boring and the product was a dismal failure.

I did meet a great person there, Harry Chesley. I learned from him about Internet protocols. He was at SRI when TCP/IP was invented, which is the fundamental layer of the internet that everything runs on.

He told me stories about how they invented all this stuff and what it was like back when there were four computers on the Internet. I loved working with Harry, but I just really didn’t believe in what we were building. I ended up going back to CoSA, just three weeks before CoSA was acquired by Aldus, and then nine months later, Aldus was acquired by Adobe.

I found myself, once again, at what felt like an enormous company. It was probably 1,200 people at the time. I just felt like another cog in the machine, and I didn’t want to be there.

At that time, Harry had gone to this company called Macromedia to work on a product called Director and figure out how to make it work for interactive television.

By this time it was 1995 which was two years after the web was standardized, right around the time that Netscape had broken off from NCSA, a research institution where it had started. The Web was this very technical, academic endeavor. Most industry people thought that cable TVs, were going to evolve into interactive television – they called it ITV, where people would be using their remote controls with interactive film and that that would be the next big thing.

Everybody I had known who worked on an ITV project had been laid off two years later. So I said, “Well Harry, I’m really excited to work on your project, but I really like this idea you have of prototyping it on the Internet, and if I can work on the Internet side of it, then I’ll take the job.” And so he convinced his boss to have two people work on the internet and two people work on ITV. I signed up to Macromedia in June 1995 before they had a website. Three months later, we were all working on the Internet, and we released Shockwave, three months after that. It turned out to be a good thing to learn about the Internet in 1995.

Lesson #3: follow your heart

The direction that your heart is pointing may not be the right direction, but the key thing about following your heart is when you get to the right place, you will know it. And that’s what your heart tells you. The path may be winding. Pay attention to what you do outside of your work because that’s going last much longer than any particular job and the people that you connect to outside of your work are as valuable, more valuable, than the people you’ll know in your career.

I had followed my heart and married my college sweetheart, and I kept switching jobs every couple of years till I found myself in a good place. In 1995, I had the opportunity to work with Netscape’s APIs and release one of the very first plugins that made it so that you could do audio, and motion graphics, and interactivity without a full page reload. And that was really exciting. I was part of the rise of the Web.

One of the things that I had learned from Harry is that the internet was actually created… Does anybody know when the internet was created?

The Internet was invented in the United States during the late 1950s to the 1970s by a group of researchers and scientists at the Advanced Research Projects Agency (ARPA). On the October 29, 1969, computers at Stanford and UCLA connected for the first time using the network then called ARPANET.

The Internet came out the information technology from World War II. The government wanted to create a communications medium that would survive a world war. One of the reasons the Internet is tremendously resilient is because it was designed to survive war. Any node can go down and as long as some parts of the Internet are alive, then people can communicate.

I was struck by the fact that what came to consumer excitement was mostly publication, what we used to call “brochure-ware.” Most of the commercial Web was these pages that would be little more than product brochures – the glossy printed promotional material that you might pick up at a retail store or receive in the mail.

I got excited about actually creating software that would allow web applications to communicate with each other in real time. My first attempt was an ill-fated project called the Shockwave Multiuser Server, which was used for chat applications and multiplayer games. Later I joined Johnathan Gay on the Flash team to create Flash video. We created two-way audio and video. People built a lot of applications that looked like this and of course, what was enormously successful was the broadcast video that enabled sites like YouTube.

I saw the internet go from 16 million users in 1995, which sounds like a lot, but most people you knew didn’t really know what the internet was — most people weren’t using the internet. Then in the 2000s, it became a household term. Everybody had an email address. Everyone could access the web.

I reflected on my career and I thought to myself, I’ve built software that’s used by hundreds of millions of people but I’ve never set out to build a piece of software that I didn’t know was possible. I’ve never really taken a risk in my career. I’ve taken risks like moving across the country, taking a job that I didn’t know whether it was going to pan out. But that’s not a real risk, because then I can just get another job. I had skills and I knew that I was working in an industry where there were plenty of interesting jobs available.

By this point, I was then working at a private company as a Director of Engineering, leading a team of about 15 or 20 people. I decided that I wanted to start a new company. Maybe I didn’t know the people that I wanted to start a company with. Maybe I didn’t know what the product was going be. And maybe I didn’t know what technology I wanted to learn next. I decided to take a year off to do independent consulting while I found or created my next startup.

I wanted to attempt things where I had no idea whether I have the capability of doing this thing, but I will think through what will happen if I fail and I’m not going to do anything if I can’t live with the consequences.

Lesson #4: Take Risks

I set out on this path and I found that often, what I would have thought about as a failure and been afraid to take a step because of that potential failure, actually wasn’t that bad. Sometimes there was no bad outcome at all.

Sometimes I would be worried about what would happen at a meeting with someone important and influential in the industry. I would think to myself: the best outcome would be if we ended up with a good contract with this company. The worst outcome is that they don’t need our services and I have had a conversation with an interesting and influential person.

My willingness to take risks enabled me to accomplish things that were much bigger and bolder than I’d ever tried to do before. I created a mobile software development company, called Blazing Cloud. I learned how to be a CEO, though I always made time to write code and stay in touch with technology.

This Year

Early this year I found myself faced with an unexpected decision. I learned about a program that paired industry experts with innovators inside government. The CTO of the United States, Todd Park, asked me to apply. How many of you knew we had a CTO of the United States of America? (zero hands raised) He’s pretty amazing. He convinced me that I could have a big impact. I also felt that the changes that are being made in government today in terms of technology policy are unlikely to happen under any other administration.

There’s a sense of urgency. Our government, our world, has some big problems — technology isn’t the solution, but it can help if applied effectively. I applied to be a Presidential Innovation Fellow.

On June 15th, I went to Washington to work for six months at the Smithsonian Institution, also working with the Office of Science and Technology Policy on the Open Data Initiative. On May 9th, President Obama declared that all government data would be open by default. Unless there is a good reason for privacy, data produced by our government with our tax dollars will be free to citizens to use for any purpose. There’s great precedence that open data fuels industry and stimulates the economy — from satellite data that powers maps on our phones to weather, geological and census data. The Innovation Fellows are working across dozens of agencies to create effective systems to implement this open data policy.

At the Smithsonian, we have a unique challenge. The Smithsonian Institution has 19 museums, 15 archives, 23 libraries, 9 research centers, and a zoo. We have over 137 million physical objects — from artworks to natural history specimens — and over 136 feet of archival material. Those are papers stacked in file folders.

I am working on a team that is creating a way to turn images of manuscripts or journals or specimen labels, often written in cursive, into machine-readable text that can be searched and made available to the vision-impaired or future generations that aren’t learning cursive in school.

We have the opportunity to look at history through primary sources. Digital volunteers can identify connections that tell new stories. Physical specimens, collected over hundreds of years, can be made available for modern data analysis.

Industry Trends

I’m excited about this new kind of software like I’m working on at the Smithsonian. You know this software, since you all use Facebook — social networks are in this same category. The code is only part of a system that doesn’t function without people and the data that those people create and sometimes data from other sources as well. Things are different now. You have grown up with assumptions that will let you see opportunities that people my age will miss, since this is all new to us.

I see opportunities in this new technology that are very exciting. Software is collaborative. After hundreds of years of specialization, there is huge opportunity in interdisciplinary approaches. We’re seeing innovation between the tradition disciplines. Also, open source is exciting. You can look at source code for thousands of projects. You can learn from it and contribute to it.

Software is distributed. Our world has software everywhere and it’s beginning to cooperate and work together. We need to be careful of the implications, and be aware of this new kind of power we can harness. Computing has become very small with tiny devices from a FitBit to tiny robots smaller than a fly. Software also has vast storage capabilities. Our ability to collect data far outpaces our ability to process it and know what to do with it.

Closing Thoughts

On this anniversary of Martin Luther King’s “I have a Dream” speech at the March on Washington in 1963. I would like to share my favorite quote of his that speaks to how we need to consider the impact of what we create with technology.

“Through our scientific genius we have made of the world a neighborhood;” and he was talking about jet planes. This is so much more true today. “…now through our moral and spiritual genius we must make of it a brotherhood… We must all learn to live together as brothers or we will all perish together as fools.”

And finally, I want to leave you with some words from Alan Kay who said “the best way to predict the future is to invent it.”

coding is the new literacy

$
0
0

Code literacy is not just the ability to read and write code. It is a problem-solving ability.

I love to code. I love to teach people how to code, because people inevitably learn a new way to solve problems, to think about how parts of our new world work.

I found this note while cleaning up in my office. I think it was the beginning of a Strange Loop 2011 talk, I called it Easy as Pie: Teaching Code Literacy (video). It’s not actually easy to teach coding, but it is something that anyone who is passionate about it can share 1-1 with a little practice. The key is to keep trying till you find that spark, and if you never do, that’s cool too, since it’s an important 21st century skill.

  • It’s not about learning a trade.
  • We should teach coding for the same reasons we teach about the laws of gravity or photosynthesis.
  • It’s a fundamental part of our world.
  • We need to prepare our kids (and adults) to use technology to solve the very real and urgent problems that we face today.
  • We need to teach our kids how to think in every possible way.  We need to stretch their brains to prepare them to lead their lives with all of options available to them.

hand written notes of the bulleted list above

exploring glass, rough start

$
0
0

Judy tries out Google Glass So I got a chance to explore Google Glass tonight. Setup took two tries, apparently it doesn’t work on 5G wifi (Kalvin found via Google search) and then we all delighted in flailing around with swipe and tap gestures to figure out how to use the thing. I took a photo of Judy trying to get it to play a video… not quite the streamlined experience we’ve been led to expect, but that’s ok. We’re explorers. It’s fun.

She made this first person chinese ribbons video and I recorded this video of the same chinese ribbons from a 3rd person perspective. Then I shared them to Google+, sadly I can embed them in my blog.

Then I accidentally started a hangout with EVERYONE in all of my google circles. Luckily I don’t really use Google+ that much, so I *only* invited 82 people to my hangout! Most of my friends and acquaintances were fairly entertained.

I have all sorts of ideas for apps, mostly silly and fun, some serious. Looking forward to exploring more…

pioneering women in computing

$
0
0

When I graduated from college people would ask me, “How does it feel to be a pioneer in your field?” There are so few women in this profession that just by entering it you’re doing groundbreaking work. For a moment I was proud of myself and then I thought, “Should I be proud of this? That some accident of my birth made me female and I’m interested in the power of these new machines?”

I went on to develop software and I loved the work. Every once in a while I would hear a story of a woman who came before me who had really done groundbreaking work. Though sometimes stories of everyday women who loved the work were even more inspiring. I will share stories from three eras of computing. I’ll start before the modern digital computer was invented.

Did you know the first computers were human? Indeed. One colleague told me about his mother-in-law who had studied math in college. She was hired directly out of school without even an interview to be a computer. This was actually a common practice in the early mid-20th century. Scientific labs would recruit women math majors to operate first slide rules and then later mechanical calculators to compute. They called it “pink collar” work.

The next age of computing starts with some of these women. During the second world war it was a time of great technical advancement. We were constantly seeking to improve the new machines of war that we invented and sent overseas. In the Ballistics Research Lab right near here in Maryland they recruited women math majors to help them with the war effort. Every time they developed new artillery they would need to calculate these ballistic tables to figure out how you have to angle the gun in order to hit a specific target. Before every new type of artillery would need to be deployed they would have these women with their slide rules calculate immense ballistic tables so that for every distance they would record a different angle that would be written up in these great big books for the soldiers at war. This was quite time consuming.

There were these two fellows who had this idea for a machine that could do this much quicker. They called their machine the ENIAC, the Electronic Numerical Integrator and Calculator. It was actually much more than a calculator. It was the first electronic general purpose computer and they needed someone to program this general purpose computer to generate these ballistic tables. They picked six women who were the best “computers” of the group for this important assignment.
The project was very top secret. These women weren’t allowed to even see the machine. They were giving wiring diagrams and then they were asked to figure out how they would connect the wires in order to have this machine do the calculations. Using this initially purely paper-thought experiment they were successful in programming the computer. They eventually had access to the machine and they lay the groundwork for this entirely new industry.

Around that same time perhaps the most famous woman in computing, Admiral Grace Hopper, was just starting her career in the military. Long before she was an admiral she developed the first compiler. “Nobody believe that,” she said. “They told me computers could only do arithmetic.” I first knew of her as the engineer who had coined the term “debugging” when she isolated a computer glitch to an actual bug hidden amongst the vacuum tubes that was creating a problem in the software.

Now, I’m going to fast-forward to the modern era even though there were many remarkable women in between. A few years ago I learned about Barbara Liskov. In 1968, the year I was born, she was one of the first women to get a PhD in computer science. Even though women had really created this field it as a long time before they were getting degrees in the university for this, it was a long time before anyone could even get a degree for this. She pioneered one of the core principles of object-oriented programming. It was only a few years ago that I learned the name of this principle, the Liskov Substitution Principle and it was quite a long time after that, I learned that Liskov was a woman.

I want to ask you today, as you reflect on your daily work, do you know the names and stories of the people who created the techniques that you apply everyday? If all of those names are of one gender or one heritage you are likely missing more than half the picture. I don’t expect you to remember the names of these women. I do hope that if anyone ever remarks to you how few women there are in tech, you might mention to them that there was a time when 100% of software developers were women.

There was a time when software development was actually considered women’s work. In every field there are people with incredible talent who make significant contributions and are then forgotten from history through an accident of their birth. Sometimes we can find these stories and retell them.

Transcript of my second talk at Smithsonian Toastmasters.

little rules for working life

$
0
0

Working in a new situation, closely with a new colleague this summer, I found myself often saying “I have a policy…” and I realized that over time I’ve create quite a few silly and some serious rules that help me navigate the day-to-day work of software development or simply working with people.  These echo in my head or I say them aloud when I find myself in a specific situation.  I do break these rules, but they make me think through those exceptions very carefully.

  • I never take a job where I don’t know at least one team member very well. The most important indicator of success for any group is the quality of the people. VCs invest in the team, rather than the idea, since it is easier for a great team to change their idea, but impossible for a great idea to find a new team. Where you choose to work is an investment.
  • Do a quick web search before you meet with or hire someone. It takes ten minutes.  You should know if they are in the news or what they just blogged about.  You spend your time more effectively, often develop a closer relationship more quickly, or learn that they are crazy so you can make yourself scarce.
  • Sometimes, fun trumps other priorities. I try to spend some time every week doing a task which is prioritized based purely on the joy of doing it.  It keeps me happy, and sometimes, there’s a part of me that understands what’s important better than my prefrontal cortex.
  • Never do anything just because a VP told you to. I learned this at Macromedia where there was a new VP every year or so.  I had to live with the consequences of my decisions and explain them to the new guy.  It’s pretty lame to have to say, “because someone told me to.”  Of course, you can’t just say “no” either.  You need to understand why you are being asked to do something and make sure the right thing happens, which may be just a little different from what you are being asked to do.
  • Working code is 9/10s of the law.  I first heard this from my friend Eric Bloch. Sometimes it is faster to demonstrate than discuss.  Sometimes spending a little time on one practical solution is better than spending the extra time to discuss options and then implement something marginally better.
  • People are more important than software.

Communication

  • Write stuff down. I take meeting notes and send them out afterwards. I don’t work without a contract. It’s not an issue of trust. There are a thousand small decisions about the work that go unsaid in a meeting. This applies to any collaborative work. Anytime I need to say to you “I will do this” or “I expect you to do that,” a follow-up email will solidify alignment or catch misunderstandings — saving time and forging stronger relationships.
  • Think through the desired outcome, before hitting send. Sometimes just a little more information or one additional “cc” will be the difference between action and yet another email in the thread.  Sometimes, this causes me to delete, rather than send.
  • “Why” is more important than “what.” Know why you are building software or writing an email or having a meeting.  Remember why a decision was made, not just what the decision was.
  • Before giving a speech, stand at the back of the room. Just for a minute, feel what it is like in the worst seat in the house.  Once I did this and overheard someone tell me what a stupid waste of time this class was going to be.  I had the opportunity to find out why and then address his concerns in the class.  Even if the room is empty when I do this, I feel more connected to the audience.
  • Never blog more than once a day, save it for tomorrow.  I’d make up a different rule if I blogged more often.  Sometimes I’ll go for weeks, or even months without blogging.  Then I’ll get back in the swing of it and have so much to say.  I just keep drafts and release them later.  I write for myself, but it’s good to think about audience also.

Celebration

  • Iterate. Celebrate. Iterate. Celebrate. I wish I knew where I read this. Celebrate the little things.  You can’t really control the big win.  It’s the small series of little wins that we can make happen.  We need to celebrate these.
  • For parties, always buy a good lager, not Michelob or Bud, and something non-alcoholic too. Even though I prefer Pale Ale, there are some folk who like a lighter beer.  I try remember that there are divergent tastes. Someone can still like good beer, even if they don’t like ale. And sometimes there’s that guy who really loves Michelob lite. Know your team and cater to their whims, when you can, but keep the Jack Daniels off the list for the holiday party.

Know the org chart

  • Tell someone’s boss, in writing, when they do a great job, especially if they are far away in an organization.
  • Always take the meeting with the big boss. Having relationships at all levels of an organization is helpful.  It’s important to see the bigger picture, understand how your work fits into broader goals.

Expectations

  • Don’t apologize. If I know I screwed up in a way that I know affects someone else, I should, of course, apologize.  However, I used to apologize when I would send an email a week late.  Then I noticed that I would get an email apologizing about lateness and I hadn’t even realized that it was overdue.
  • Don’t make promises we don’t need to make. It’s sometimes important to set expectations.  If I avoid habitually making promises that I don’t actually need to make, then it easier to remember the important ones.
  • Never say that solving a software problem will be fast, say it is “straightforward.” Even if I think it’ll take ten seconds, it might take longer to deploy it.  It might need to be scheduled later.

Time

  • Plan to be early, arrive on time. A good friend once told me “to be early is to be on time, to be on time is to be late, to be late is to be fucked.”  So true, though sometimes, you can make people feel awkward if you are waiting for them so don’t make it too early. You can always have a coffee nearby or take short walk around the neighborhood.  Remember, there might be security or sign-in procedures.  Just because you know where the building is, doesn’t mean you know where the meeting is.
  • Date commitments as time ranges when possible.  If I think it’ll happen on Monday, I say “early next week.”  Instead of July 10th, consider “this summer.”
  • Nothing happens between Thanksgiving and Jan 2. When scheduling I have date ranges that I skip over and pretend they don’t exist, unless I have specific commitments from every individual who is needed to deliver or review whatever.  Every group, every culture has dates where less work gets done for good reason.  We all need these down-times.  Know them and simply work around them like water in a stream flows around a rock.  In San Francisco, I usually black out the week of Burning Man and a few days after Pride.  In the northeast at my first company, it was Rosh Hashanah.
  • Never ship on a Friday. Monday is usually soon enough. Think about whether the release really merits having the team on deck over the weekend. If it does, plan for it ahead of time.

As a Manager

  • The #1 job of a good manager is hiring and retaining great people. When I’m in a management role and things get crazy, as they often do, I tell this to myself every morning and twice during the day.  It takes discipline to spend time writing an excellent job description or having individual meetings with staff when there are urgent, pressing, seemingly more important issues to deal with.
  • Never hire until you’ve interviewed at least three great candidates. Hiring should be a tough decision.  We should have to ask ourselves what is really important so we can decide between these amazing people.  We should have cause to wonder if we should stretch our budget to hire more than one.
  • Move fast on a great candidate. This can conflict with the previous rule, but only when I’ve failed in prioritizing recruiting.  When I have a job opening, I spread the word far and wide as quickly as possible, then if I have a great candidate, I’ll already be talking to other candidates and have context for a quick decision.
  • If all of your candidates look the same, you have a recruiting problem. Know the demographics of your industry and of the region where your office is.  If you are only interviewing white guys or Stanford grads, you are missing some of the talent pool.  Since I work in a male dominated field, I’ll sometimes tell a new recruiter, don’t send me any resumes until you have at least one women among them.  With 20% women in our industry, 20% of my candidates should be women.  There’s should be a few qualified, talented people of color in the mix. I can then hire the best person for the job.
  • Always be recruiting. Imagine your dream team.  Your people should be on their way to becoming your dream team, if they aren’t there already.  Just getting to know people who you will want to work with, will make you more able to create that team.  Sometimes you can’t hire them, but maybe they’ll come give a talk to your team or serve as a mentor or informal advisor.  Maybe you want to work for them in your next job.

information is oxygen

$
0
0

During the Industrial Age, information was property — held by few, information required money and brought power. With the rise of the Information Age, information became water. We all need it, sometimes it falls from the sky, but there are complex rights. Like water, there were information sources and streams. Information was produced and consumed.

A new era is emerging, where information is oxygen. We can’t survive for 3 minutes without it. In fact, if we need to wait for more than 200ms for information, we get restless. We have cloud computing.  Linked Data defies boundaries and does not conform the the bounds of its container.  Increasingly our data is unstructured, expanding or contracting to fit the shape of its emerging purpose. Open Data is creating an increased transparency, where we can see our government at work or observe trends taking place in the real world through weather, agricultural or census data, to name just a few open data sets.

I found the Scholarly Kitchen questioning the metaphor of information as property in 2009, and then suggesting information as streams in 2011.  Our language adapts to the changing world around us.

Like ripples in the water as an unseen fish comes up for air, we can see change in our culture through metaphors that move through our written and spoken language.

the evolution of the letter C

$
0
0

Language evolves. Spoken language evolves faster than written language, but the written language is easier to track as it leaves behind physical artifacts.

The third letter of our alphabet is the problematic C, which could be soft as in ‘nice’ or hard like ‘cat’ or I don’t know what you call the sound at the beginning of ‘chat.’ This ambiguity has frustrated spellers of English across generations. Many years ago I looked into the history of the letter C in order to satisfy one kid’s curiosity that mirrored my own. I learned about the Phonecian alphabet which pre-dated our own roman script, where the pre-cursor to our letter C sounded like a hard-G.

From the illustration above, you can see that evolution took place differently for Greek and Cyrillic. Today in the same letter from the Cyrillic alphabet looks like this: Г and wikipedia tells me that it sounds like “Ge.” If only we had kept this letter as is, and adopted K and S more aggressively as spoken language drifted, we would have an easier time spelling words in modern English. Although we would still have the challenging relationship between “public” and “publicity” where the written form illustrates the relationship between noun and verb. The solution, of course, is that we should modify the spelling to “publik,” then we’ll need to all start saying “publikity” and everything would be easier to spell.

Notes
I was delighted to find the visualization above (via @larsyencken) which illustrates the evolution of various alphabets that includes Greek and Cyrillic, and as the Roman script we use for English. Bill Rankin at Radical Cartography describes this striking visualization which includes a geographic map as a “relatively simply exercise” — simple for him! I’m so glad he took a moment from his busy life to put it together.


stories of shitty behavior don’t make me want to leave…

$
0
0

It sucks to read about more shitty behavior at a tech conference. The sad truth of our society is that shitty conduct is common in every industry, especially those dominated by old power structures of white, straight men. I don’t like to hear those stories, but they don’t make me want to leave. They make me want to stand up and be counted. They make me proud to be part of a community where brave people speak up.

There are times when I’ve stood in awkward silence or simply left an uncomfortable situation.  I’m human and flawed and sometimes weak or just plain tired. Other times, I hope more frequently, I speak up. I rarely call people out publicly. I think it is important to focus on the inappropriate behavior, rather than vilify the person.  We need to focus on how we can all notice it a little sooner before it gets out of hand, and how we can each act to eliminate or mitigate the behavior, especially when we are not the target.

I can understand someone who has been abused not forgiving the abuser.  I can understand wanting to exile that person from our society.  However, they are going to hang out somewhere and there are other people like them whose stories have not been told in blog posts and broadcast via twitter.   We need to do the hard work of staying alert to make our conferences and workplaces safe for everyone.

I’m so proud of all friends who are allies, especially the straight, white guys.  I try to be an ally for the folks who don’t have my privilege and power as well.  More of us need to speak out in the moment, to be on the lookout.  These stories need to be told until we grow up as a community and learn how to eliminate this behavior.

civic hacking at the smithsonian

$
0
0

A few weeks ago, the Smithsonian American Art Musuem held the first Smithsonian hackathon as a way to include volunteers in the process of re-imagining what a kiosk of the future might be for the Luce Foundation Center for American Art.

Twenty-three people from the DC community spent the weekend in the museum, writing code and creating innovative designs for a next generation virtual museum experience that let’s people connect both during a museum visit and from home.

Most of the time, it was like every hackathon I’ve ever attended. Folks sat in teams, furiously typing or drawing, collaborating in small groups.
Untitled
But something else magical happened… at one point, someone stood up and suggested a “brain stretch” — one team was struggling to come up with ideas for particular use cases. People from various teams got together and brainstormed:

Luce Foundation Center Hackathon
After drawing dozens of ideas, we asked Georgina and Bridget, who were the organizers from the Luce Center, which ideas they liked best. There were so many great ideas! The team that organized the brain stretch integrated some of them, and another team mocked up and implemented other ideas.

People were less fixated on winning, than they were to create great solutions to solve real challenges, to make more of our nation’s treasures accessible to a wider audience.

It was inspiring — and well worth all of the extra advance work to make it happen. It was so hard to judge the winners that we ended up making new prizes. Here are some of my favorites:

Once Upon a Time: stop motion live action envisions the museum of the future

GeoSafe: this Windows 8 app is shippable!

I really want an ArtPass on my next museum visit, and just part of the submission from the winning team, LuceMatch is like hot-or-not for art.

Check out the rest of the Luce Center hackathon submissions!

work in government, save the world?

$
0
0

Working as a Presidential Innovation Fellow has changed my perspective on the US government. I still believe there’s a bureaucracy that threatens to crush us all under its weight, but I no longer see that as immovable or inevitable. There are people working in our government, relentlessly in pursuit of excellence. They are passionate about the need to solve problems and provide opportunities for the American people. Where I work, at the Smithsonian, and at many agencies, the mission is much bigger than that, we are challenged to solve some of key problems facing our world. If we don’t, who will?

The following positions are not for just anyone. You need to have amazing experience as an entrepreneur and some real experience working through and around huge organizations with byzantine rules.  You need to be a leader, and maybe you never considered working in government before this moment.

I’ve taken a stab at providing a feel for what each position will need. Why don’t we have better job descriptions posted on the gov website? Because our Federal hiring process sucks. I say these words as a citizen, not as a government employee.  Come help these good people make it better.

  • Director, Presidential Innovation Fellows: Work with dozens of people like me, position us where we can make the biggest difference, then stand back and watch shit happen. Some of that you may need to untangle, when we ask forgiveness, not permission.  Some things will be magical and powerful that you never believed possible.  Articulate the strategy.  Compromise on the method, not the outcome.
  • Director, GovX: You know how hard it is to create great software that solves real problems and gains widespread adoption.  You’ve created web and mobile products, as an engineer, product manager, designer, or that role you can’t pin a name on where you just made it happen.  Maybe you have run a consulting company or maybe you have an amazing talent for matching the right people with the right problems and won’t be satisfied till you see the best they can come up with. You believe in starting small, creating pilot or prototypes that are validated with real users. You know how to create software that starts with ten users and then scales to 310 million happy customers.
  • Communication Specialist You are not just a story teller — you discover amazing untold stories just by talking to people.  You know how just a few words can resonate with people, such that they become a phrase that is reused and gain power with the retelling.  You have a sense of how to build a brand.  You understand that a solution doesn’t really exist until people know it is there.

We need you.  Or someone you know.  Tweet this, post it on Facebook.  There are three people who we need to find, who don’t yet know what they are doing next year.

Unfortunately, the timing is very tight. I encourage you to apply ASAP if you are interested. The Communication job will stop accepting new candidates at 11:59pm Eastern on Wednesday December 4th, 2013.

The PIF and GovX director roles end not much later, Tuesday, December 10th and Wednesday the 11th (also 11:59pm Eastern)

Jason Shen also writes about “3 federal jobs that just might change everything.” You should read his post, the job descriptions and FAQ.

learn to code: no math required

$
0
0

When I learned to code, I was not very good at math and didn’t like it much. I had just started pre-algebra and struggled to make sense of abstract equations and abitrary rules that seemed to serve no purpose and were disconnected from my real world. I didn’t care to discover answers that were already known to imaginary word problems that some textbook writer made up.

If someone had told me that I needed to be good at math to be good at programming, maybe I would have avoided learning to code. Instead, when I was 12 years old, I sat down with a BASIC manual and an Apple II and taught myself to code for fun.

Earlier this week, President Obama called on every American to learn to code. His message is spot on, mostly. Unfortunately, he said “No one’s born a computer scientist, but with a little hard work and some math and science, just about anyone can become one.”

Perhaps some colleges require advanced math for a Computer Science degree, that wasn’t true in 1990 at Brown University. I did end up learning a lot of math and science. After I learned to code and struggled through algebra at school, it all started to click with geometry. Maybe it was the shapes and a connection to art and the real world, maybe computer programming actually helped me understand mathematics. I went on to study Calculus in high school and Linear Algebra in college. At the university level, I studied computer graphics, which does require math. In my first startup, where we invented the software program After Effects, we used math to let artists create video special effects. In both cases, it was mostly geometry and matrix math, which is technically part of linear algebra, but the equations I needed for graphics were no more complex than what I was doing in high school geometry. For most software development, especially these days as a web developer, you would be fine with elementary school math.

Of course everyone should learn math and science — those are just not directly related to most computer programming. Yesterday I recorded a short video message, a public service announcement, to help clarify this for parents and educators.

origins of the smithsonian

$
0
0

In 1826, James Smithson wrote in his will that, if his heir were to die without children, his entire estate would go “to the United States of America, to found at Washington, under the name the Smithsonian Institution, an Establishment for the increase and diffusion of knowledge among men.” This unusual bequest was even more strange in that James Smithson has never been to the United States of America in his lifetime.

At the time, President Andrew Jackson didn’t feel that accepting this bequest was within the powers of the executive branch, so it was up to Congress to decided what to do. There were great debates on how to interpret this strange bequest. Should it be dedicated to our scientific knowledge? to understanding our world through the arts? should this institution be the keeper of history? or even create an observatory to look out at the stars and understand our universe? Finally in an Act of Congress on July 1, 1836, the Smithsonian Institution was founded to do all of those things.

In my first few of working at the Smithsonian, I toured the Smithsonian Institution Archives where I saw this hand-written will:

I learned more about about Smithsonian history on a tour of the “Castle” with curator Rick Stamm, author of an illustrated history of the Smithsonian Institution Building.

We don’t know exactly why James Smithson made this strange bequest, but it was in an age when our understanding of the world was changing. Smithson had been born in Paris, as the illegitimate son of first Duke of Northumberland. In The Lost World of James Smithson, Heather Ewing notes, that due to the circumstances of his birth, Brittish law declared that he

shall not be hereby Enabled to be of the Privy council or a Member of either the house of Parliament or to take any Office or place of Trust either Civil or Military or to have any Grant of Lands, Tenements or Hereditaments any inheritable property from the Crown to him or to any Person or Persons In trust for him.”
p. 46

However, he still was able to attend Oxford and became a citizen scientist of his day, distinguishing himself as a chemist. He joined several phillosopher’s clubs — gatherings of young men who would discuss theories of the new science. Reading about this history makes me wonder if tech meetups are the modern day equivalent, where men and women gather to exchange ideas and evaluate the latest inventions and discoveries. It strikes me that James Smithson must have seen America as a place where a new institution could thrive, dedicated to the increase and diffusion of knowledge, rather than simply promoting the progeny of the privileged.

James Smithson, of course, was quite privileged, but perhaps his own struggles for recognition provided some perspective that caused him to strive for a higher ideal. Or perhaps he just wanted to make sure that the Brittish crown was never able to seize his assets, even after death. In any case, he left his fortune to our country almost 200 years ago, and the folks at the Smithsonian take its mission quite seriously.

To this day, the Smithsonian museums have no admission cost and are free to the public. Its archives, libraries, research institutes and observatory offer scientists and researchers, facilities and unparalleled historic collections that enable new discoveries every day.

The post origins of the smithsonian appeared first on the evolving ultrasaurus.

Viewing all 45 articles
Browse latest View live




Latest Images