The CSForAll Consortium Summit in St. Louis starts Monday. CodeBrooklyn, co-founded by Brooklyn Borough President Eric L. Adams and myself in 2015, is a consortium member. The mission of CodeBrooklyn is to raise awareness of computer science education among Brooklyn parents and schools and in turn connect school communities, especially those that are majority students of color or Title I, with funding for CS programs. Due to various client commitments I am unable to get to St. Louis. So here’s a few questions and thoughts I have regarding the CSForAll movement in the United States, with a heavy dose of NYC in particular, going into what looks to be a tremendous coming together of incredible educators, donors, advocates, and organizations. These topics and questions are organized as follows:
- Working with the Trump Administration and the Implications for the CS education Community
- Rigor and Two Tier Computer Science
- Prioritizing Rural America
- Our Languages and Paradigms Need Review
- We Need to Spread Funding Around Better
- Corporations are Going to Need CS Education Strategies
- What About the Boys?
Should the “CS Ed Movement” Work with the Trump (and DeVos) Administration? And Will Different Choices Divide It?
It’s evident to many who work in CS education in the U.S. that some of the leadership of the national computer science education movement has divided into two camps. This division is largely, though not entirely, based on willingness to work with the current president, his education secretary, Betsy DeVos, and the administration overall.
The first “camp” is led by Code.org, which has made the calculation that despite concerns they might have about other Trump administration policies (including and notably the “Muslim Ban”; Code.org’s founders, twins Hadi and Ali Partovi, are immigrants from Iran) there is more to be gained by moving forward and working with the current administration.
The result of this collaboration was the September 25 White House announcement of the Trump administration’s intent to “establish a goal of devoting at least $200 million per year in grant funds towards … high-quality STEM and Computer Science education”). This was followed a day later in Detroit by First Daughter and Advisor to the President Ivanka Trump’s announced commitment of $300 million in new private sector funding for computer science education by Internet Association members that have also chosen to be partners with the Trump administration on computer science education. These White House partners include Amazon, Google, Microsoft, General Motors, and Salesforce.com. (How much of both the public and private funding is actually “net new” vs. money previously pledged and/or being shifted from other important federal purposes is a separate, though crucial, question to be asked and is as of now unanswered).
The other camp is essentially the CSForAll Consortium — or, more correctly, several of its most visible and well-known leaders and supporters. Several of these people were previously members of Obama White House Office of Science and Technology that led that administration’s development of CS policy. In particular, they were behind President’s Obama’s January 2016 CSforAll proposal, the center piece of which was to be $4 billion in federal funding (Disclaimer: In December 2015 I attended one of a series of White House CS For All meetings; I was also consulted by the Hillary Clinton campaign regarding the development of her CS education platform). The position of many in this group is perhaps best represented in Reshma Saujani’s powerful op-ed in the NY Times last month about her decision that she and the organization she started, Girls Who Code, would not participate in the new Trump White House CS Education announcement.
Personally, I’ve been conflicted on the topic of working with the Trump administration, and my views have shifted in the last 11 months.
As context, I supported Hillary Clinton in the primaries and voted for her in the general election. I am a registered Democrat; for a couple years I have represented the blocks, the 64th Electoral District, around my house in Park Slope, Brooklyn on the Kings County Committee.
But I also grew up in Maine – Kennebunkport specifically. Maine is a notoriously independent state and being from Kennebunkport I couldn’t avoid meeting a Republican or two. I have a friend who worked on the transition team and now has a senior role in the Trump administration with the Department of Homeland Security.
My first inclination immediately after the election was to give the President-Elect and his team time to develop and announce their CS education policies (unlike Hillary Clinton, President Trump’s campaign did not have a CS education policy plank) – but to also retain the option to change my mind if circumstances warranted.
In November I argued for this view – “let’s give them a chance” – on a Facebook forum for those involved in the CS movement. Many argued against me, taking a position similar to Reshma’s view expressed last month in the Times. They viewed any work with the Trump administration as inherently amoral. Undaunted, I created a Change.org petition asking the incoming administration to support the CSForAll program. I shared my petition by email on December 1, 2016 to a number of the people I know who are active in the CS education movement, a number of whom will be in St. Louis.
Circumstances warranting introspection and a revisit of my view happened quicker than I had anticipated they might. The impetuous to change for me was the “Muslim Ban” weekend of January 28th. My children’s elementary school in Brooklyn is approximately 10-15% Muslim, including many whose family come from Yemen, one of the countries include in the original version of the ban. On January 30, 2017 I wrote to the same group I had on December 1, 2016 a one line email: “I renounce my email, dated 12/1/2016, in its entirety.”
Ten months later, after all that’s transpired, working with the Trump administration seems more fraught with moral hazard risk than ever. And yet organizations I respect and admire like Code.org and Microsoft have made the decision that partnering with the president, his daughter, and Secretary DeVos in order to further fund and expand computer science education is worth that risk.
My larger concern now is what this means for the CS education movement, both now and down the road. The dominant role Code.org plays in the CS education movement was already a point of contention and consternation before President Trump’s ascendency. While much of this is political inside baseball probably irrelevant and invisible to the teacher in her/his CS classroom (and, at the end of the day, that’s really all that matters), I worry that the movement further fractures based on decisions to work – or not – with Donald Trump.
“Rigor for All”: We Must Avoid Watering Down (and Creating Two Tiers of) Curriculum and Lessons, Especially Based on Socio-Economics
Last month I attended the first joint CSNYC/CSTA-NYC Meetup – the previous CSNYC Meetups have been reconstituted as the NYC chapter of CSTA. Through my employer, TTM Advisors, I’ve done work with both CSNYC and CSTA and admire both organizations. The Meetup was also a celebration of Cornell Tech’s new Roosevelt Island campus. Diane Levitt, Director of K-12 Education at Cornell Tech and Michael Preston, Executive Director of CSNYC, were co-hosts; these two people have worked tirelessly to expand computer science in New York City for many years.
While the event was good, and the company even better, I was disappointed by an exemplar video the NYC Department of Education CS4All team chose to highlight as an example of the computer science lessons both NYS/NYC taxpayers and the funders of CSNYC are paying to have developed. Mike Zamansky, one of the most esteemed computer science teachers in the city, and who until last year led the CS department at Stuyvesant, was similarly disappointed in the video and its showcased lesson.
The most celebrated attribute of the lesson featured in the video appears to be that it was “culturally responsive.” But I am not really sure just how “culturally responsive” what’s shown in that video really is. I am not really a big fan of the whole cultural appropriation critique popular now, especially on college campuses, but if I could ever sympathize with that view a bit, it’s in this video.
Throughout the world drumming has a tremendous spiritual tradition. Drumming is also an important way of communicating stories and traditions across generations. I am not sure students rote memorizing and reciting HTML does that tradition the respect it deserves. Moreover the children in the video looked, like many NYC schools(though, sadly, hardly all – more on that in a bit), pretty diverse. To which children’s culture in that video was the lesson seeking to respond? I couldn’t help wonder what the reaction might be to a video of Korean- and Chinese-American students in Flushing reciting the periodic table to Japanese Taiko drums in order to construct a “culturally responsive” chemistry class.
My larger concern is the contents of the lesson itself. Simply put, memorization and recitation of an HTML page, even if done to the beat of a drummer, is just not computer science education from what I’ve seen. Is there any proof, anywhere, that having students rote learn HTML contents of a web page has any pedagogical value?
I am guessing someone decided to take this approach because 1) they wanted to do something “culturally responsive”, 2) they wanted to introduce kinesthetic learning (not uncontroversial; sometimes connected to efforts to be “culturally responsive” which is one source of the controversy), and/or 3) drum class was the only class during which the principal could find a way to do computer science.
But in the video the drum teacher is clear in his own admission that he doesn’t understand the semantic meaning of the words (the HTML code) he’s teaching the kids to say. This is remarkably different from the traditional cultural role of drumming and chanting in the first place — the words matter tremendously, whether it’s invoking a God or transmitting a traditional story from generation to generation. The person leading and drumming would definitely know the meaning of the words and likely have a hand in their interpretation.
And is there even an opportunity for the kids to learn the semantic meaning of, for example, “a href”? We never find out. It feels like going to Latin Mass and reciting the Gospel but not having any idea what you are saying because you don’t read Latin.
Moreover this video is now online as a featured exemplar for other school communities around the city. Do we want other schools, principals, parents, teachers still getting their head around what “CS4All” even means to see this video and think “Oh, so that’s what computer science education is?” I’d argue “No.” I cringe thinking that school communities I work with in Brooklyn and around the city might see that lesson and conclude that’s what computer science education is.
Another concern I had at the Meetup was that the DOE CS4All team member made the statement that “We wanted to make sure teachers were not grading students based on their code and whether it was correct or not… based on wanting them to grade students on their process and how they got there.”
First of all, this is a terrible message to send to kids. It’s the epitome of “everyone gets a trophy”. It puts effort above results. The world is a brutal place and just doesn’t work that way.
Perhaps in the affluent, largely white, ostensibly “progressive” neighborhoods like the Upper West Side and (sadly) my own, Park Slope, many children, through the trust funds and inherited wealth of their parents, can be safely insulated from the real world of accountability, testing, and objectively right and wrong answers. But outside of these neighborhoods and a particular cohort of parents (the same general group of parents who in New York City are fond of attending public forms to clamor for integrated schools but whose own, quite different, personal choices to self-segregate their own kids contributes to making NYS and NYC home to the most segregated schools in the country; I have seen this issue first hand when I was an elected member of CEC 13 and had to vote on the contentious PS 8/307 rezoning) the rest of us study, work, and live in a world where we are measured not by effort but results. And I’m guessing that more than a few of the children in the exemplar drumming video are not the beneficiaries of the socio-economic privilege to “opt-out” of accountability, testing, or jobs with performance reviews based on objective criteria (results).
Moreover, it must be noted that correctness is a very real thing in computer science. The correctness of code is a critical concept within computer science theory. Programs can be proved correct using formal verification techniques. Code can be evaluated by things like its readability by other developers, its extensibility, and whether it makes appropriate use of abstraction.
Software can be be further evaluated on its ability to fully and wholly solve the problems it was designed to solve while additionally creating no secondary effects, including and especially negatives ones — i.e., adherence to business requirements and (successful) acceptance testing.
Code can also be evaluated – objectively – on the time complexity of its component algorithms (Big O notation).
And while it’s true that a program might be written in, say, 100 different ways, so long as the requirements are met, functions produce expected return values in unit tests, etc., the DOE team member’s assertion didn’t even reach that bare minimum. Getting the right answer apparently matters not at all.
More broadly this pedagogical approach, advocated by some in the education community – the one of process over answers; the “we just need to teach kids how to think” approach that devalues the role of objective fact in schooling, I believe has contributed to the rise of our corrosive “fakenews” political climate and portions of our citizenry seemingly challenged by the need to differentiate fact from fable.
The assertion that “We wanted to make sure teachers were not grading students based on their code and whether it was correct or not” is a perversion of the originally and legitimately valid concern about the time spent on testing and rote learning. That twisting has taken us to a new place where people stand up to assert we do not want to evaluate students work for objectively right or wrong answers. Right answers do exist in computer science and it is a misrepresentation to set the expectation with students that computer science – or the real world – is just “Free to Be You and Me“. It’s not.
Beyond the concerns I had at last month’s Meetup, I have another concern: paper based computing activities and their use in economically disadvantaged school communities.
As context, many key concepts of computer science can be taught off line – i.e., on paper. For example, the summer professional development for TEALS volunteer teachers shows how one can demonstrate algorithms like insertion sort and merge sort using student participants and pen and paper. Moreover, nearly every teacher I know has a backup plan or two for any online lesson in the event of network or laptop problems (which happens a lot).
But increasingly, especially in NYC, I’m seeing what is a “hands in the air” approach to infrastructure issues that schools may encounter with laptops and networks, and which are major obstacles to online computer science instruction. The effective message is this – if your kids’ school (and the parents at that school) are not affluent enough to buy a bunch of laptops that actually work and/or politically connected enough to lobby your city council person for “Reso A” funding to get infrastructure upgrades, these school communities are expected to get by with paper based off line lessons for computer science. This is two tier education and in conflict with “For All.”
I think it’s unfortunate that the interdependence between the success of the ten year DOE CS4All roll out in NYC and ongoing upgrades to school LANs and the DOE WAN does not formally exist, though is obvious to everyone involved nonetheless. I know the CS4All NYC DOE team – who work their butts off for our city (let me clear: my constructive criticism comes from a place of love, not disdain), has no control over the NYC DITT schedule of projects. But that doesn’t make disconnecting these work efforts within the DOE the right approach.
I know fairly well the laptop and network situation on the ground in NYC schools. Last year I contributed, through my work on Code Brooklyn, to the Technology Survey Report developed by the Brooklyn Borough Presidents Office which was released during last year’s CS Ed week. Right now, through my work with TTM Advisors, I’m doing a project for the Heckscher Foundation for Children where I’m visiting economically disadvantaged school communities (i.e., Title I) around the city, especially in the Bronx and Brooklyn, to assess the root causes of network, both LAN and WAN, poor performance.
The headline is that public schools of privilege, which are generally schools with majority white populations in Manhattan, “Brownstone Brooklyn” and pockets of Queens – the school communities that can raise a million dollar PTA fund and pull political strings as needed to get still more funding, have the best hardware and networks in the city. The rich, as is all too common in our nation, especially in areas that self identify as “liberal” and “progressive”, get richer.
So while affluent white children learn to code on shiny new laptops in Tribeca on fast Meraki networks, children of color in Brownsville are expected to get by learning computer science on paper, if they have any computer science at all. That isn’t right. The answer to crappy laptops and slow networks can’t be continue the “let them eat cake” approach of telling them to do computer science offline on paper. The answer must be to get those schools new laptops and fast, reliable networks. To be clear, I know first hand that the DIIT is working really hard to address this; New York State’s slowness in dispersing Smart Schools Bond Act money hasn’t helped matters either. But, again, effort is not the same as results and we must make sure ALL of our schools have the laptops and networks they need in order to teach computer science.
One final note on the topic of have and have not school communities: if you’re involved in the computer science movement, regardless of your role or where you live, and you’re not getting to a school that is either Title I and/or majority students of color, once a month and at least once a quarter, you risk falling of touch with the school communities that deserve the most attention and focus. These are the school communities most critical to our nation realizing the “for all” vision for computer science. It’s essential to spend time in schools, talking to students, parents, teachers, and administrators (though, if you do visit a school, please do not do as one global social media company did and spend the majority of your time at a school located in in the Howard Houses public housing in Brooklyn, and at which many students’ families have daily concerns about basic food security, talking about how great the free corporate cafeterias are in Palo Alto. If you’re that well-off, you might consider donating a couple dollars to that school so it can buy a few new computers instead of bragging about your burrito and sushi bars).
With the exception of my work from 2015 to 2016 as the founding Executive Director of TeachCS, which was national in scope, most of my work within the CS movement has been limited to New York State, New York City, and the great borough of Brooklyn. But love Brooklyn though I do, my heart will always be in my home state of Maine. And so I when I was back home in July I was happy to read an op-ed in the state’s largest paper, the Maine Sunday Telegram/Portland Press Herald, that the state legislature had passed L.D 398, an act “to enact measures designed to ensure that schools are authorized and encouraged to consider courses taken by a student in computer science as demonstrating proficiency in science or mathematics.” The centerpiece of this legislation is the establishment of a K-12 Computer Science Task Force, chaired by Jason Judd, Project Director of Project>Login at Educate Maine, and on which Code.org is also a member.
I think we all know now all to well what can happen when affluent college educated professionals in coastal cities lose site of the real economic pain being experienced in much of rural America, especially among those whose jobs in manufacturing and other heavy industries have been lost. But given the nature of the CS movement – many, though not all, of its leaders, philanthropists, donors, and organizations are based in large urban centers on the east and west coast, it can be easy to forget and neglect the needs of rural America. We can’t let that happen.
Of course, it must be noted, a relatively rural state not entirely dissimilar to Maine in size, poverty level, and economic head winds – Arkansas, is arguably the national leader in statewide computer science education programs. This is in large part due to the tremendous work of Anthony Owens, Arkansas’s State Director of Computer Science. Arkansas has shown us that rural states in the middle of the country can’t just keep up, they can and will lead.
Some will argue that the answer is online learning. Some of the TEALS program delivery to rural states is done in that just model using remote TEALS volunteers and telepresence. And while as the former CTO of Relay Graduate School of Education I have certainly seen the potential and power of flipped classrooms, hybrid models, and online learning more generally, what’s needed most, whether it’s the south side of Chicago or Aroostook County in Maine is qualified, in person teachers in all schools, urban and rural.
It’s great that the CSForAll Consortium chose St. Louis, the gateway to the west and the geographic center of the country, for its host city. A critical part of “For All” is our more rural states and territories (let’s remember Puerto Rico and USV now more than ever!) and this choice of location sends an important message about the CSForAll Consortium’s commitment to those areas. (And if you’re interested in this topic, check out Garth Flint’s blog).
Imperative and object oriented (OO) programming, and languages in these paradigms like Java and Python still make up the lion’s share of computer science curricula. What gets short changed in these choices is functional programming and that’s unfortunate for a few reasons. First, the cross walks between math and computer science are arguably their strongest and most clear in functional programming. Second, by not seeing functional programming until years into their CS education students end up so used to both imperative and/or OO that FP seems like a huge leap, and it really shouldn’t (it’s worth noting that universities like Harvard teach functional programming in the second semester of their computer science program). Third, while FP has been around a long time (Alonzo Church, who developed the Lambda Calculus on which functional programming is based, was a professor to Alan Turing) it’s now seeing a huge resurgence in interest and usage, both academically and commercially.
We also need to talk about the appropriateness of block based coding in high school.
Our mission at TeachCS was to fund, via philanthropy from Tata, Microsoft, Google, and Quotidian Ventures, professional development for teachers to be trained in one of five National Science Foundation (NSF) funded courses, three of which were aligned to the new (and so far quite successful) AP Computer Science Principles framework. A key feature of AP Computer Science Principles is that, unlike AP Computer Science A, which is based on Java, AP Computer Science Principles is language independent.
As part of the Microsoft TEALS program, I taught what was essentially a beta version of AP Principles during the 2013-2014 school year using Beauty and Joy and SNAP at Uncommon High School in Brooklyn. Though BJC is thoughtful, rigorous, well designed course, my students were relentless in asking “when are we going to learn real coding”, by which they meant text based coding. Last week, when I was visiting Brooklyn Technical High School, one of the most selective high schools in New York City, the student tour guide described, unprompted, her AP Computer Science Principles class as “not real coding” because they “just used blocks.”
Platforms like Codesters (Disclaimer: Codesters, a computer science education company, is a client of TTM Advisors LLC, my employer) attempt to bridge that gap by allowing students to develop in a block based environment and then, when they’re ready, switch over to text-based (in Codesters’ case that’s Python). I think models like that, as well as curricula that simply are text based from the get go, need to get more consideration for both middle schools and, especially high schools. We can’t be afraid of text based coding. Students are telling me at least that they think block-based programming is “for little kids” and we must take that feedback into account.
Code.org and its founder, Hadi Partovi, have done a tremendous service to the CS community and this recent wave of enthusiasm for CS education nationwide. It’s signature event, the “Hour of Code” has like no campaign ever made a huge impact in areas of inclusion and participation not just in the United States, but around the world. CS Ed Week is still almost two months away and already overall 9,000 schools and communities around the world have committed to doing the “Hour of Code” this year.
As recognition of this great work, just last week Amazon announced a $10 million donation to Code.org. To put that in perspective, the total budget for the Computer Science Teachers Association is under $1 million a year. Amazon’s donation could have funded CSTA’s current operations for ten years.
I have not done the numbers, but my rough finger in the wind from having done fundraising myself is that over half of the philanthropy for CS education is going to Code.org and I’m guessing that’s more like 2/3 of the funding coming from the big tech companies like Facebook, Amazon, Microsoft, and Google.
This is a difficult topic to discuss but discuss it we must — Code.org’s incredible ability to raise philanthropy is making it difficult for other nonprofits in computer science (with a couple exceptions, like Girls Who Code, who also do a great job of marketing and fundraising) to make ends meet. Corporate Social Responsibility (CSR) departments are not known for being either well-resourced themselves or as risk takers — this makes a follow the herd model of simply giving money earmarked for computer science education to Code.org by default an easy choice for a haggard, over burdened CSR middle manager. And Code.org does do great work. But this present state of affairs doesn’t always make more for a vibrant, robust community of thriving non profits.
I also think it’s important to make room in CSForAll for curriculum developers, coding platforms, and professional development companies that are for profit (for purposes of this discussion I’m leaving out for profit K-12 schools; I personally can not yet support for profit K-12 schools). McGraw Hill is for profit. Pearson is for profit. Nearly every ed tech startup you can think of is probably a venture backed for profit – companies like Knewton and Code Academy. Organizations that sell products and services to schools and districts are usually for profits.
And yet, this current wave of computer science education momentum has largely been built on the assumption that the predominant business model for organizations involved in CS curriculum and professional development will be the 501(c)(3). Anyone who has run a non profit knows how difficult it is to raise money and keep going year after year raising ever more, at least until earned revenue can become a significant source of funding, which can take many years. And because of the afore mentioned dominance of Code.org in attracting CS philanthropy, this leaves the remainder of the CS nonprofits essentially in a constant state of fierce competition amongst themselves for what amounts to philanthropic table scraps. It also makes young nonprofits vulnerable — when the cornerstone donor of TeachCS for over 80% of our first year scholarships and programs operations decided mid year to instead shift its funding to a similar Donors Choose program, it effectively killed TeachCS and left me personally out tens of thousands of dollars in back salary I could no longer pay myself (thankfully the afore mentioned other four donors honored their commitment and we were able to still do a scaled back program).
Meanwhile there is a ton of cash out there in the form of venture capital, both institutional and individual. There are business opportunities in CS education and we have to stop being queasy about that as, again, organizations that sell to schools are usually profit generating businesses anyways. And so I’m happy to see for profits like CodeHS and VidCode as partners at the CSForAll Summit.
I’d also add that technology community – especially Google, Amazon, Facebook, IBM, Twitter, Microsoft, etc. – can do much more more in terms of philanthropy. I’d challenge the tech sector to increase their giving – both in the form of philanthropy and VC, to CS education organizations by 10x over the next 3 years, and that each company commit to supporting at least two other CS organizations other than code.org (again, this isn’t a knock on Code.org — but the CS education community will benefit from more diversification in philanthropy by well-heeled companies with valuations in the hundreds of billions of dollars).
And while I understand the impetus (and touch of arrogance) that pushes companies like Google (CS First), Apple (Swift Playgrounds), and Microsoft (MakeCode) to build their own CS programs, curricula, and platforms, the CS community, school communities, teachers, and students, would be better served by less fragmentation. While it’s wishful thinking, these companies could serve the community better to instead focus on financially supporting the curricula and platforms already out there, many with principal investigators and a decade or two head start on academic peer review and in-class evaluation.
In 2000, while I was still living Silicon Valley, I joined KPMG Consulting LLC, then still part of KPMG LLP. Over the next six years, as the Enron scandal rocked the accounting and consulting community, I’d watch on as KPMG spun out KPMG Consulting, which would be rebranded BearingPoint. In 2006 I left BearingPoint and joined Deloitte Consulting LLP, which was (and is) still part of the overall Deloitte family of partnerships, the last of the group of Deloitte, KPMG, E&Y, PwC, etc to retain its original structure which includes both audit and its original consulting unit.
Since 2000 there has been tremendous change in the “Big 4” (then the “Big 5”). In 2000 the control and power within these firms lied with the audit and accounting partners. By the time I left Deloitte in January 2013 it was evident that consulting was on the ascent both in terms of consulting revenue as as a percentage of aggregate overall revenues from the US member firms (Audit, Tax, Consulting, and Financial Advisory) and internal influence. A year prior to my departure, in January 2012, Deloitte bought Ubermind, in turn creating Deloitte Digital, and moving fully into the market once traditionally dominated by the digital agencies. Deloitte, like most of these professional service firms, is not your grandfather’s white shoe accounting firm.
What does this all have to computer science education? Computer science is becoming a critical skill in a lot more careers than ever. 30 years ago it’s hard to imagine that firms like Deloitte or PwC would care much if a candidate knew how to program a computer. Now it’s an essential skill for many positions, both client facing and back office, in those companies. And as I argued last year in a guest post for Code.org, I think the traditional division between functional analysis work and software engineering is going to go away.
And so increasingly I think we’re going to see large organizations, and not just those in technology, developing explicit talent and philanthropic strategies for computer science. This will likely take the form of…
- Increasing the share of philanthropic and other corporate giving to computer science (the afore mentioned overworked CSR manager is going to need help determining which organizations to support). In particular corporations are going to be inclined to want to support organizations that are helping students develop the skills that they are going to need most from prospective employees, whether that’s A/I, big data, cybersecurity, hardware design, or some other area of computer science.
- Firms like Deloitte start formal recruiting in the junior year of students’ undergraduate program but they look even earlier to begin attracting and identifying top talent. Corporations are going to be looking for top computer science students and solid computer science programs in high schools as sources for prospective employees.
- Computer science will be an ever more important part of talent development strategies and so leading companies are going to want to better engage with the computer science education community about best practices in teaching computer science.
This is perhaps my most controversial point. I don’t just think that – I know that – as I’ve shared the following view point with several prominent people in the CS Education movement and the reaction has been quite negative. But persist I will as I think this is important.
My son goes to a progressive, politically left-leaning, public middle school in the East Village of Manhattan. It does not yet offer computer science as part of the curriculum taught during the day – i.e., it’s a school that has yet to benefit from the NYC DOE CS4All program’s 10 year rollout.
However the school does offer a Girls Who Code after school club, which is open to only girls at the school.
Before I go any further, let me be clear: I think the world of Girls Who Code and its founder, Reshma Saujani and nothing here is meant as a critique of that program or her. There are also academically researched cases to be made for creating places for girls and young women to explore computer science on their own.
But I’d like to think that the intention of our inclusion efforts around computer science was not to end up with school communities where the de facto condition is that a student may not study computer science at school, though offered, just because he is a boy.
In the case of my son’s school, fault lies not with GwC but with the school administration and DOE overall as well as an overall funding mechanism for schools in NYC – one that over relies on the affluence of parents to pay for core programs as if these public schools were in fact private – that can neither yet provide CS during the class day for my son nor fund an additional after school program for CS that would be open to girls and boys alike. This is not inclusion. This is not equity. This is not “For All”.
How did we get here? I think the CS movement has made a mistake by assuming autodidact models from our past when we ourselves were children. These are outdated, errant, and even racially and privileged based assumptions about how boys get exposed to computer science. These models include Gen X boys like me in the 1980s who huddled around Commodore 64s or Apple IIs programming Basic between bouts of Castle Wolfenstein, or more recently, archetypes like the young Mark Zuckerberg in the 1990s teaching himself to code basic web sites. These models are also premised largely on the life experiences of privileged, suburban, mostly white boys and are not representational of boys in their own full diversity.
Complicating this still more is that we – adults who can often remember command prompts and even DOS, do not always appreciate the degree to which programming has been abstracted away from the casual tech user. For many young people programming a computer today is no less foreign than the idea would have been in the 1970s to open up the television set to fiddle with its internal circuits. So even young autodidacts may not have the inclination to just start coding on their own. In other words, they need computer science to be explicitly offered and introduced to them, ideally by experienced teachers trained in peer reviewed, academically pressure tested, curricula, whether those children are boys or girls. We must stop assuming boys will just go off to learn to how to code on their own.
Having a strategy for boys need not, and should not, come at the the expense of the many crucial programs, like Girls Who Code and Black Girls Code, that exist to promote inclusion and equity with young women (and, I’d note that I’m also the father of a daughter). I’d argue that for boys the strategy is one based on using computer science to address the widening academic gap between boys and girls, which is now starting to manifest itself in the work place as well. Computer science could be a powerful way to help our boys from falling even further behind girls in the classroom.
To give an (hypothetical) example: if 10,000 students take AP-CSP year one and 7,000 are boys and 3,000 are girls, and then in year two that number is 5,000 boys and 5,000 girls, is that success? I say no, but I think there are some in our community who would say yes, that’s (some) progress. Again, these numbers are illustrative but I think the goal should not be just a shift in relative terms, but increases in absolute numbers, with the additional goal that we want girls’ participation to increase at a (much) faster rate than boys.
So in this example, success in my mind would be if in year two we grew male participation by 2,000 more to 9,000 (a 22% increase) and female participation by 6,000 to 9,000 as well (a 200% increase), thus increasingly the absolute number to 18,000 (an 80% overall increase) while also improving the ratio in the numerator and achieving gender parity. Isn’t THAT what we want? And yet I get the distrinct impression that for some the numerator ratio in relative terms is in fact the priority – that the first illustration where 2,000 less boys participate would, yes, be a form of success. I just can’t get behind that. And while this example is illustrative, the practical policy of my own son’s school seems to be just this in real life terms. CS is available to only one gender – girls. That changes the ratio, sure, but leaves my son behind in the process to achieve that goal.
Finally I’d observe that US civic society is not going to be a better place in 20 years if we have even more men wandering around with few to any skills relevant in the modern job market.
I have been but a bit, part-time contributor to several efforts to expand computer science. As mentioned above the bulk of my work has been limited to New York City and Brooklyn in particular. And while I taught CS in high school for a year as part of the TEALS program (and three years of English in Japan on JET) I am not a professional educator and do not posses a graduate degree in either education or computer science. It’s classroom teachers, especially in Title I schools, along with parents, whose view points are perhaps the most critical. And incredible national leaders like Jan Cuny and seasoned CS educators like Mike Zamansky know far more than I could ever about the best strategies to roll out CS nationwide and within individual schools. So take all that in consideration and as a disclaimer re my thoughts above.
I wish I could be in St. Louis. The line up looks incredible and there are a lot of smart people that will be in attendance. Have fun and do great stuff.