Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Hal Murray <halmurray@sonic.net>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Cc: Hal Murray <halmurray@sonic.net>
Subject: Re: [NNagain] public service website slowness
Date: Sun, 18 Aug 2024 19:42:02 -0700	[thread overview]
Message-ID: <20240819024202.7432F62003D@107-137-68-211.lightspeed.sntcca.sbcglobal.net> (raw)

From Computer History Museum

An Evening with the U.S. Digital Service Team
  https://www.youtube.com/watch?v=YBXexQrPx9I
An hour and a half.

"I want us to ask ourselves every day, how are we using technology to make 
a real difference in people's lives."
President Barack Obama


Behind the scenes within the Obama Administration, the U.S. Digital 
Service (USDS) is quietly rethinking--and remaking--the way the federal 
government harnesses digital technology to serve the nation in the 21st 
Century. In this Revolutionaries evening, we will meet the brain trust 
behind this landmark initiative.

USDS was created in 2014 by the White House and is housed within the 
Office of Management and Budget. It began as a small team of digital 
experts who were recruited to repair the HealthCare.gov website. That 
elite digital team now works in collaboration with other government 
agencies to make websites more consumer friendly, to identify and fix 
problems, and to help upgrade the government's technology infrastructure. 
Along the way they are saving taxpayers a lot of money as well.

We have assembled a panel of USDS leaders for a conversation with Museum 
CEO John Hollar about the great work they'e doing to basically redefine 
the experience of government. They will talk about how they were recruited 
and why they continue to serve, and what's so powerful about the idea of 
"giving back." In addition, they have a steep recruitment goal to hit to 
help build an ongoing pipeline of tech talent bound for the nation's 
capitol -- and the response to their pitch has been overwhelming.

-- 
These are my opinions.  I hate spam.




             reply	other threads:[~2024-08-19  2:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  2:42 Hal Murray [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-19  2:02 Dave Taht
2024-08-19  4:02 ` Dick Roy
2024-08-19 14:40   ` David Bray, PhD
2024-08-19 14:48     ` Steve Crocker
2024-08-19 14:57       ` David Bray, PhD
2024-08-19 15:31       ` Dave Crocker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240819024202.7432F62003D@107-137-68-211.lightspeed.sntcca.sbcglobal.net \
    --to=halmurray@sonic.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=nnagain@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox