Re: [NNagain] public service website slowness

Re: [NNagain] public service website slowness

[Hal Murray]

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.

Re: [NNagain] public service website slowness

[Dave Crocker]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

On 8/19/2024 7:48 AM, Steve Crocker via Nnagain wrote:
>
> Why not address this problem head on?  Do not present plans to 
> Congress for upgrades, new capabilities, etc. unless the plan includes 
> appropriate funding for maintenance and upgrades.


When I entered grad school, 45 years ago, we had a new building under 
construction for us.  An observation was made that getting a donation 
for a building used to create exactly this problem for the University 
and that now the donation also needed to cover ongoing expenses for 
operating it.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net
mast:@dcrocker@mastodon.social

[-- Attachment #2: Type: text/html, Size: 1399 bytes --]

Re: [NNagain] public service website slowness

[David Bray, PhD]

[-- Attachment #1: Type: text/plain, Size: 5389 bytes --]

Oh, that's done and is usually standard practice - the challenge is our
Congress separates the authorization to do something from the appropriation
to do something.

So Congress can legitimately say they authorized a plan to have all these
things in place.

And then separately when the appropriations process happens - well that's a
different Committee. And separate from the authorization process.

... There also are unfunded mandates. Congress passes a law requiring a
Department or Agency to do something.

But the passed law is then not funded or only poorly funded. However the
Department or Agency still has to do the work. Yes, the head of the
Department or Agency can go raise their concerns for yet another unfunded
(or inadequately funded) effort - however remember Congress approves the
political heads and so raise too many concerns and you mind find yourself
out of a job...

I'm not saying we should be a Parliamentary-like system, however it is
worth noting that in our country, both at state and federal levels, those
who pass the law are intentionally distinct from those who have to carry
through on what is done...

Good video on how Congress likes the situation where they tell the
President/Executive Branch broadly what to do (and not do) by law, yet also
absolve themselves from having to pass a correspondingly logical budget for
those prescribed activities: https://www.youtube.com/watch?v=KIbkoop4AYE



On Mon, Aug 19, 2024 at 10:48 AM Steve Crocker <steve@shinkuro.com> wrote:

> Time: Many years ago
> Place: Living room
> Actors: My grandfather, my father, me
>
> My grandfather, observing that I was about to turn 16, generously offered
> to provide funds to buy me a used car.
> My father quickly interceded.  "Not so fast."  "What about gas,
> maintenance, etc?"
> The discussion continued, reaching a decision that I should take a
> part time job.
>
> ======================================
>
> Why not address this problem head on?  Do not present plans to Congress
> for upgrades, new capabilities, etc. unless the plan includes
> appropriate funding for maintenance and upgrades.
>
> Steve
>
> SceneLiving room discussion
>
> On Mon, Aug 19, 2024 at 10:41 AM David Bray, PhD via Nnagain <
> nnagain@lists.bufferbloat.net> wrote:
>
>> Part of the challenge is that several government websites usually only
>> have a budget allocated to launch them - and then they collect dust (the
>> O&M long-tail). So the lament is that a website that was made 18-25 years
>> ago is slow to load nowadays (keeping in mind that client-side javascript
>> wasn't really an option back then either).
>>
>> A much bigger problem is making sure legislators when they appropriate
>> funds for a project that is intended to continue for multiple decades -
>> those appropriators need to also include in that budget continuous
>> refreshes to both the web UI/UX as well as the security posture. That's the
>> other side of the issue, when legacy technology isn't funded IT security
>> postures get progressively worse as sites get more and more out of date.
>>
>> Meanwhile we also need to encourage ways for continuous updates to both
>> the UI/UX and the security to be done that aren't captured by incumbents
>> who use this knowledge of the ins and outs of both the technology systems
>> and associated human systems to charge inflated prices to keep things
>> updated too?
>>
>> ... and this isn't only for government organizations.
>>
>> Ask Delta about their IT infrastructure and how when
>> Crowdstrike/Microsoft Cloud hiccupped, how that created a ripple effect for
>> them and their UI/UX too. O&M tied to legacy IT does have substantial
>> impacts.
>>
>>
>>
>> On Mon, Aug 19, 2024 at 12:03 AM Dick Roy via Nnagain <
>> nnagain@lists.bufferbloat.net> wrote:
>>
>>> Speed is not the problem … it’s how information to be transmitted is
>>> encoded and more importantly, how much redundant info is being sent.  It’s
>>> the MS mindset … give me a faster processor and more memory and I’ll give
>>> you more bloated code to fill it up! When you put kindergarteners in
>>> charge, you get a kindergarten solution! JJJ
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> *From:* Nnagain [mailto:nnagain-bounces@lists.bufferbloat.net] *On
>>> Behalf Of *Dave Taht via Nnagain
>>> *Sent:* Sunday, August 18, 2024 7:03 PM
>>> *To:* Network Neutrality is back! Let´s make the technical aspects
>>> heard this time!; bloat
>>> *Cc:* Dave Taht
>>> *Subject:* [NNagain] public service website slowness
>>>
>>>
>>>
>>> This was a damning analysis of many government websites' speed.
>>>
>>>
>>>
>>> https://infrequently.org/2024/08/object-lesson/#the-golden-wait
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> Dave Täht CSO, LibreQos
>>> _______________________________________________
>>> Nnagain mailing list
>>> Nnagain@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/nnagain
>>>
>> _______________________________________________
>> Nnagain mailing list
>> Nnagain@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/nnagain
>>
>
>
> --
> Sent by a Verified
> [image: Sent by a Verified sender]
> <https://wallet.unumid.co/authenticate?referralCode=tcp16fM4W47y>
> sender
>

[-- Attachment #2: Type: text/html, Size: 11696 bytes --]

Re: [NNagain] public service website slowness

[Steve Crocker]

[-- Attachment #1: Type: text/plain, Size: 3709 bytes --]

Time: Many years ago
Place: Living room
Actors: My grandfather, my father, me

My grandfather, observing that I was about to turn 16, generously offered
to provide funds to buy me a used car.
My father quickly interceded.  "Not so fast."  "What about gas,
maintenance, etc?"
The discussion continued, reaching a decision that I should take a
part time job.

======================================

Why not address this problem head on?  Do not present plans to Congress for
upgrades, new capabilities, etc. unless the plan includes
appropriate funding for maintenance and upgrades.

Steve

SceneLiving room discussion

On Mon, Aug 19, 2024 at 10:41 AM David Bray, PhD via Nnagain <
nnagain@lists.bufferbloat.net> wrote:

> Part of the challenge is that several government websites usually only
> have a budget allocated to launch them - and then they collect dust (the
> O&M long-tail). So the lament is that a website that was made 18-25 years
> ago is slow to load nowadays (keeping in mind that client-side javascript
> wasn't really an option back then either).
>
> A much bigger problem is making sure legislators when they appropriate
> funds for a project that is intended to continue for multiple decades -
> those appropriators need to also include in that budget continuous
> refreshes to both the web UI/UX as well as the security posture. That's the
> other side of the issue, when legacy technology isn't funded IT security
> postures get progressively worse as sites get more and more out of date.
>
> Meanwhile we also need to encourage ways for continuous updates to both
> the UI/UX and the security to be done that aren't captured by incumbents
> who use this knowledge of the ins and outs of both the technology systems
> and associated human systems to charge inflated prices to keep things
> updated too?
>
> ... and this isn't only for government organizations.
>
> Ask Delta about their IT infrastructure and how when Crowdstrike/Microsoft
> Cloud hiccupped, how that created a ripple effect for them and their UI/UX
> too. O&M tied to legacy IT does have substantial impacts.
>
>
>
> On Mon, Aug 19, 2024 at 12:03 AM Dick Roy via Nnagain <
> nnagain@lists.bufferbloat.net> wrote:
>
>> Speed is not the problem … it’s how information to be transmitted is
>> encoded and more importantly, how much redundant info is being sent.  It’s
>> the MS mindset … give me a faster processor and more memory and I’ll give
>> you more bloated code to fill it up! When you put kindergarteners in
>> charge, you get a kindergarten solution! JJJ
>>
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> *From:* Nnagain [mailto:nnagain-bounces@lists.bufferbloat.net] *On
>> Behalf Of *Dave Taht via Nnagain
>> *Sent:* Sunday, August 18, 2024 7:03 PM
>> *To:* Network Neutrality is back! Let´s make the technical aspects heard
>> this time!; bloat
>> *Cc:* Dave Taht
>> *Subject:* [NNagain] public service website slowness
>>
>>
>>
>> This was a damning analysis of many government websites' speed.
>>
>>
>>
>> https://infrequently.org/2024/08/object-lesson/#the-golden-wait
>>
>>
>>
>>
>> --
>>
>>
>>
>> Dave Täht CSO, LibreQos
>> _______________________________________________
>> Nnagain mailing list
>> Nnagain@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/nnagain
>>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>


-- 
Sent by a Verified
[image: Sent by a Verified sender]
<https://wallet.unumid.co/authenticate?referralCode=tcp16fM4W47y>
sender

[-- Attachment #2: Type: text/html, Size: 9639 bytes --]

Re: [NNagain] public service website slowness

[David Bray, PhD]

[-- Attachment #1: Type: text/plain, Size: 2567 bytes --]

Part of the challenge is that several government websites usually only have
a budget allocated to launch them - and then they collect dust (the O&M
long-tail). So the lament is that a website that was made 18-25 years ago
is slow to load nowadays (keeping in mind that client-side javascript
wasn't really an option back then either).

A much bigger problem is making sure legislators when they appropriate
funds for a project that is intended to continue for multiple decades -
those appropriators need to also include in that budget continuous
refreshes to both the web UI/UX as well as the security posture. That's the
other side of the issue, when legacy technology isn't funded IT security
postures get progressively worse as sites get more and more out of date.

Meanwhile we also need to encourage ways for continuous updates to both the
UI/UX and the security to be done that aren't captured by incumbents who
use this knowledge of the ins and outs of both the technology systems and
associated human systems to charge inflated prices to keep things updated
too?

... and this isn't only for government organizations.

Ask Delta about their IT infrastructure and how when Crowdstrike/Microsoft
Cloud hiccupped, how that created a ripple effect for them and their UI/UX
too. O&M tied to legacy IT does have substantial impacts.



On Mon, Aug 19, 2024 at 12:03 AM Dick Roy via Nnagain <
nnagain@lists.bufferbloat.net> wrote:

> Speed is not the problem … it’s how information to be transmitted is
> encoded and more importantly, how much redundant info is being sent.  It’s
> the MS mindset … give me a faster processor and more memory and I’ll give
> you more bloated code to fill it up! When you put kindergarteners in
> charge, you get a kindergarten solution! JJJ
>
>
>
>
>
>
> ------------------------------
>
> *From:* Nnagain [mailto:nnagain-bounces@lists.bufferbloat.net] *On Behalf
> Of *Dave Taht via Nnagain
> *Sent:* Sunday, August 18, 2024 7:03 PM
> *To:* Network Neutrality is back! Let´s make the technical aspects heard
> this time!; bloat
> *Cc:* Dave Taht
> *Subject:* [NNagain] public service website slowness
>
>
>
> This was a damning analysis of many government websites' speed.
>
>
>
> https://infrequently.org/2024/08/object-lesson/#the-golden-wait
>
>
>
>
> --
>
>
>
> Dave Täht CSO, LibreQos
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>

[-- Attachment #2: Type: text/html, Size: 6211 bytes --]

Re: [NNagain] public service website slowness

[Dick Roy]

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]

Speed is not the problem … it’s how information to be transmitted is encoded
and more importantly, how much redundant info is being sent.  It’s the MS
mindset … give me a faster processor and more memory and I’ll give you more
bloated code to fill it up! When you put kindergarteners in charge, you get
a kindergarten solution! :-):-):-)

 

 

 

  _____  

From: Nnagain [mailto:nnagain-bounces@lists.bufferbloat.net] On Behalf Of
Dave Taht via Nnagain
Sent: Sunday, August 18, 2024 7:03 PM
To: Network Neutrality is back! Let´s make the technical aspects heard this
time!; bloat
Cc: Dave Taht
Subject: [NNagain] public service website slowness

 

This was a damning analysis of many government websites' speed.

 

https://infrequently.org/2024/08/object-lesson/#the-golden-wait




 

-- 

 

Dave Täht CSO, LibreQos


[-- Attachment #2: Type: text/html, Size: 5177 bytes --]

[NNagain] public service website slowness

[Dave Taht]

[-- Attachment #1: Type: text/plain, Size: 169 bytes --]

This was a damning analysis of many government websites' speed.

https://infrequently.org/2024/08/object-lesson/#the-golden-wait


-- 

Dave Täht CSO, LibreQos

[-- Attachment #2: Type: text/html, Size: 514 bytes --]