A nice, concise table from the @codeorg State of CS Ed report this year showing the adoption of the 9 key CS policies at the individual state level.

How does your state rank there? Are you surprised by any of it? Image
Here are the 9 policies referenced in the table. The Code.org advocacy coalition recommends these things be in place at a state level to make computer science a fundamental part of the state's education system. Image
Basically, there's a lot more to getting CS in schools than the state govt telling districts to do it or making a requirement. There needs to be curriculum and goals, teachers need to be trained and certified (pre and in-service), and all that has to be paid for and coordinated.
No, the idea is not that every kid should have to take a lot of CS classes. Rather, it's that all kids get some exposure to the field so that they have the opportunity to be curious. Then, they have options to pursue these classes further.
And as a periodic reminder, here's how CS is defined for this purpose:

"Computer science is the study of computers and algorithms, including their principles, their hardware and software designs, their implementation, and their impact on society."
CS in this sense is not what you think of when you think about university majors. It's ultimately simple about using computers to solve problems. That includes coding, but also security, architecture, systems, networks, and even things like robotics.
Here's the policy breakdown from my home state. Still work to be done, particularly in preservice training and having all HS's offer CS courses. Image
I see lots of correlation between these state level stats and our @RuralTechFund work. States with more of these policies in place typically generate more requests to us for support than others. That's a good thing -- they're pushing tech ed forward in their districts.
Not only that, these states also request more advanced technology at younger ages. A 9 policy state might see more schools start a robotics team at the elementary level, whereas states further behind see schools less likely to do that until HS or at all.
All told, I generally support these policies and their state-level adoption. They can take different forms and some are better than others, but they push CS ed access forward. More access to more people.
Even better as that these policies generally have bipartisan support and are less likely to be reversed when elected offices flip.
That means these policy areas are one of the (less and less frequent) places where you can speak to your elected reps and they'll probably be somewhat supportive regardless of broader wedge positions the national parties go nuts about.
You can read the State of CS Ed 2021 report here and look up information about your state and where y'all stand in relation to access and policies: advocacy.code.org/stateofcs.

No registration is required.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Chris Sanders 🍯

Chris Sanders 🍯 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @chrissanders88

6 Nov
Some of the work I'm most proud of from my time at Mandiant was pioneering the building of investigative actions *into detection signatures* as they were written. This had profound impact across the detection and product teams, and made the tool so much more accessible.
We included two main components: a plain English version of the question that the analyst needed to answer, and the search syntax that would provide data to answer the question. It manifested in the UI as something I named "Guided Investigations".
This helped detection engineers write much better signatures because they had to think more deliberately about the consumer of the alerts (the analyst). It led to higher quality detection logic and clearer metadata, including rule descriptions.
Read 26 tweets
3 Nov
There are a lot of ways that folks distinguish between blue team roles. My focus is on investigative work and cognitive skills, so I divide those roles into the mental model shown in this diagram. 1/
The primary characteristic that distinguish these investigative roles is their common place in the incident identification and response process. You might be familiar with that process acronym of PICERL, but it appears in many forms: csrc.nist.gov/publications/d…. 2/
In the diagram, the functional portion of the PICERL process is at the top. Each role is listed below that with where it typically fits in relative to those phases. Preparation and Lessons Learned phases are excluded since those are pre and post-investigation steps. 3/
Read 28 tweets
1 Nov
Y'all remember my Golden Ticket charity fundraiser from last year where you could win free access to ALL my training? Well, good news. It's coming back in December!

I'm planning it now and want to make it even bigger. So...
Last year we raised 46K for charity, which I matched for a total impact of 92K.

This year, I'm looking for individuals or companies to partner with me by matching a portion of the money raised or kicking in funds at specific community donation goals.
One way to help is to offer to match up to $amount of donations.

Another is to offer $amount that you will contribute once the community reaches $goal.

My team will handle the logistics of it all so that it's headache-free. We'll also share with folks that you're helping out.
Read 5 tweets
22 Oct
At it early this morning. It’s going to be a great day. #BBQ
Today, the only thing going on is this beautiful prime brisket. It has my full attention. Just over 12 pounds before trimming, probably closer to 10 now.
I’m often a salt and pepper only guy for brisket, but I’ve been digging the Meat Church rubs lately so I’m trying their Holy Cow on this one. Trimmed and rubbed down last night. On the counter now while the pit warms up.
Read 76 tweets
20 Oct
Since I spend so much time talking to and researching SOCs and SOC analysts, I often get asked, "What the biggest difference is between high and low growth SOCs?"

The answer? Expectations.
1/
First, what do I mean by growth? I'm talking about places where analysts can grow their abilities. These are the places that take complete novices and help them achieve competence or take experienced analysts and help them specialize. Growing human ability.
2/
The organizations that support growth well are those where leadership has high (but realistic) expectations for analysts. These most often center around expecting the analyst to be able to make reliable, evidence-driven decisions confidently.
3/
Read 10 tweets
19 Oct
Like lots of folks, I'm pretty miffed by the lack of robust virtualization support on Apple M1 hardware. I hope that gets fixed soon. But, it also got me to thinking about decision making at big vendors like Apple and others.
1/
For example, the security community (myself included) is often critical of Microsoft for some of their decision-making when it comes to usability/flexibility vs. security. Two things immediately come to mind...
2/
1. Macros. The idea that they exist, are default usable, and the UI pushes users more toward enabling them than disabling them.

2. Default logging configs. Fairly minimal with lots of sec relevant stuff left out (integrate sysmon already!).
3/
Read 16 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(