#quality

scriptkiddie@anonsys.net

Microsoft documentation is bullshit because they want it so đŸ˜±đŸ‘Ž

#microsoft #documentation #fail #ai #software #bullshit #omg #wtf #problem #quality #development #help #user


â™Č anonymiss - 2024-12-17 12:51:59 GMT

#Microsoft: Our #documentation is big #bullshit and we have no desire to change it. Users can ask #AI if they need help. Nobody reads the documentation anyway.

source: github.com/MicrosoftDocs/WSL/p


Thanks for the contribution here and appreciate your attention to detail. We have decided to keep as-is.. part of that decision is that more and more folks are using AI chat to access guidance and tables don't always translate well in that context.

...

That is hands-down the worst response to a documentation #patch that I've ever seen.

Nobody wonders anymore why Microsoft software is so bad with this mind setting.

#developer #software #fail #problem #response #decision #documentation #guide #tutorial

danie10@squeet.me

South Africa’s Home Affairs needs a visible Dashboard for Uptime Monitoring of Service and Network Uptimes

Front of a bland caramel coloured government building, with numerous people standing outside in front and waiting for service
There’s an old adage that says ‘What you cannot measure, you cannot manage’ which is actually not fully true, because many things have to be managed that do not have any hard metrics to go by. But the principle of having some signals and metrics does indeed greatly assist with determining whether a service is improving or declining. For the Department of Home Affairs, this would include a metric to indicate the mainframe service is fully operational, and then a metric for each and every remote DHA office’s connectivity status. From a technology perspective, if those lights were all green, it should be 100% operational. If the mainframe system is not green, then everything is unavailable countrywide. If some site offices show red lights, it means they have no connectivity at those DHA offices.

This should not be very complicated, as there are many free and open source tools that do this type of job very well. For such example is Uptime Kuma which I use to monitor and alert me of issues with my own hosted services (pictured below). Home Assistant and Grafana can also be used to provide additional analytics and alerting if necessary to e-mail addresses, mobile phones, Telegram Groups, etc. There are probably other uptime monitors that can do an even better job.

A dashboard showing a few site names such as GadgeterZA Website, GadgeteerZA Photos site, GadegteerZA Limesurvey Site, and OpenWebRx SDR receiver. Each has a green bar to the right of it indicating it has been up for 100% of the time. At the top, it states All Systems Operational.Uptime Kuma Dashboard – Services can be grouped and tagged also

The SA Cabinet actually has (used to have) a policy around using primarily free and open source software where they can. So no tender is required to procure free and open source software. From the skills side, something like this generally requires no coding, and just some configuration. I’m very sure SITA still has the internal skills to be able to do this themselves. It is easier than designing a Drupal website. The biggest challenge is to just decide what are the best metrics to actually measure, e.g. ping time to every remote site. But even a start would be something better than what we don’t see right now.

It is vitally important that the accountable Minister is able to have this dashboard and alerting available in order to see the improvement from any actions taken. Likewise, the Department also could/should be using this to measure the service levels from SITA and the 3rd party service providers. I know from experience that much of those metrics only get reported on after month end, and usually by the service providers themselves, not by any live dashboard that the Department has.

But it is also significant for citizens, who consume this service daily, and often have to stand in long queues for hours on end, only to hear later “the system is down” or “the network is down”, to also be able to at least see this dashboard in its live state. There is no reason to keep such a live status secret from the public. Citizens should be aware before they visit the DHA offices, or whilst standing in the queue, that the system is down, so that they can decide whether to come back another day, or postpone their visit. It is scary to think how much economic productivity time is wasted by so many citizens around the country, standing in these queues, when the system or lines are down.

A good 10+ years ago the SA government had an approved eGOV Framework which promised an e-Services portal, built on open source software, and which would have APIs (application programming interfaces) available for 3rd parties to use. The Open Data philosophy was intended to improve transparency and accountability by government, and also to provide a source of data that private entrepreneurs could use to build businesses or sell value-added services on top of government’s open data (see image below). Some services today, such as Municipal Money, are built of top of data scraped from National Treasury and audit reports. These 3rd party services provide not only an important watchdog role, but also help citizens and businesses to make data-driven decisions themselves.

An old screenshot of a webpage showing copyright 2017 at the bottom. Site shows a SA gov logo as well as a SITA logo to the top left. Page title is e-Services Open Data. It goes on to explain what open data is and how it can revolutionise the way that the public and private sectors engage with government. It provides links to API, Data Sets, and Mzansi ID.South African Governmnet’s e-Services Open Data policy

Taking the above into account, there is no reason why citizens should not be able to see such a real-time dashboard of availability of DHA services. Coming back to the old adage about ‘What you cannot measure, you cannot manage’, I’d certainly hope at least that the new Minister for DHA has access already to such a dashboard. If not, maybe the above ideas can help to ensure one is put in place pretty quickly. The more visibility and transparency around these services, will probably be better for all, and maybe even focus efforts on where the real issues are.

SITA’s DBA’s, network engineers, and mainframe operators/programmers should be able to advise which of the following monitor types (depicted below) can be effectively used to monitor the services. I know there is monitoring of each one of these services, but they are usually reported on retroactively, and they do not appear as a unified view of a single government service (Network engineers monitor their services separately from DBAs, who monitor separately from mainframe operators, etc). The whole aspect of monitoring needs to be adapted to show a client/citizen centric view, preferably with a single index score that can be measured for improvement and availability.

A screenshot titled Add New Monitor with monitor type options such as HTTP(s), Ping, DNS, Docker Container, MQTT, and many more.Uptime Kuma’s monitor types
#Blog, #opensource, #quality, #southafrica, #technology

anonymiss@despora.de
bliter@diaspora-fr.org

#Amiga #demo #soundtrack: Desert Dream - Reynolds' #drum #cover - #Reynolds

top

1993 was an #amazing period of time. The Amiga's #popularity was on it's top, such #productions have been released what we hardly believed to be possible. On of these miracles was this demo too. It is #unbelievable, how low #resources are enough for this #quality by an Amiga

https://www.youtube.com/watch?v=5IUV0p9Itzw
#musique #music

danie10@squeet.me

Bluetooth vs. Wi-Fi Music: Which Has Better Audio Quality? Choose Wi-Fi if you can

Bild/Foto
Wi-Fi is better for music since these connections have much higher bandwidth than Bluetooth, meaning your music isn’t additionally compressed, making for higher-quality audio. Bluetooth can still sound good and is very useful (and is probably good enough), but for lossless or hi-res audio, Wi-Fi is your only option.

Bluetooth may not offer the highest-quality audio, but the good news is in many cases, this doesn’t matter much. If you’re doing most of your listening via Spotify, a higher bandwidth connection isn’t going to offer any sort of upgrade anyway (since Spotify doesn’t have the best audio quality).

Some streaming services like Tidal, Deezer, Apple Music, and Amazon Music Unlimited offer either lossless audio, hi-res audio, or both. With these, you may notice a slight upgrade in sound quality over Wi-Fi, but even that is debatable.

See https://www.howtogeek.com/878574/bluetooth-vs-wi-fi-music-which-has-better-audio-quality/
#Blog, #music, #quality, #streaming, #technology

adolar@pod.dapor.net

Buy a brand name, they said.
It costs more, but it's totally worth it in the long run, they said...
enter image description here
That box was kept closed, not open. This is btw a pretty common problem in the humid tropics. A lot of steel that may be labeled as "stainless" develops stains pretty quickly, once it gets here. Real Swiss army knives are holding up pretty well, everything else though...
#quality #tropics #humidity #rust

jirikiha@diasp.org

This is an excellent description of Systems Thinking.
Definitely worth the 15 minutes, and Dr. Ackoff is funny, too!
If Russ Ackoff had given a TED Talk...

This presentation is from a 1994 event hosted by Clare Crawford-Mason and Lloyd Dobyns to capture the Learning and Legacy of Dr. W. Edwards Deming. Russ knew Dr. Deming and speaks here about the difference between "continuous improvement" and "discontinuous improvement" as seen through the lens of systems thinking.

#Systems #Quality #Deming #Ackoff

H/T @benedikt Bauer

canoodle@nerdpol.ch

Rant: Open Source and the concept of: Release early, release often or publish early & publish often -> continuous development/continuous integration (CD/CI) -> tight loops ok but still - linking to nirvana without redirection & badly written software that everyone uses - another case of - nothing works "ok" - klarer fall von "nichts funktioniert ok"

https://administrator.de/forum/wol-geht-nicht-mit-broadcast-adresse-101944.html

-> it’s catastrophic, when webpages change their url setup


https://www.heise.de/netze/Wake-on-WAN–/artikel/89304/0

because it will result in

“nothing works” “ok”

this does not have nothing to do with luck, but with:

  1. bad url management:
    • wordpress does an pretty good job there, as whenever the user changes the url (more keywords?) it will also redirect from the older past urls to the new url
      • that is how it is SUPPOSED to be for EVERY website of the (not so) “ethernal” part of the internet called www
  2. elastic search seems to be a very very badly written software that does not do any sort of software quality checks?
    • or maybe it’s wrongful integration? (but maybe it just sucks)
    • why is every developer-user using it?
  • PS: as mankind still ponders and evolves (by making mistakes) how to best deal with computers
    • yes someone said “publish early” & “publish often” (doing this with the blog
 also
 often too often and too early X-D)
      • or: “Release early, release often” (wiki)
        • “tight feedback loop between developers and testers or users” (wiki) - yeah sure as a developer that might be a good thing, as a user
 really doubt it
 - there are highly intelligent respected developers that pioneered this concept
 it might work for small teams
 (of one)
        • “This philosophy was popularized by Eric S. Raymond in his 1997 essay The Cathedral and the Bazaar, where Raymond stated “Release early. Release often. And listen to your customers”.[4]”“This philosophy was originally applied to the development of the Linux kernel and other open-source software, but has also been applied to closed source, commercial software development.””The alternative to the release early, release often philosophy is aiming to provide only polished, bug-free releases.[5] Advocates of RERO question that this would in fact result in higher-quality releases.[4]“
      • has this lead to every developer going in the: continuous development/continuous integration direction? (definately sounds like it)
        • it really should be called CD/CI not CI/CD because first comes the development, then the integration (but well hewego: CI/CD@RedHat)
        • still pondering if it’s really a good idea - well if software quality sticks to UNIX principles of K.I.S.S (most do not and have NO IDEA what non-K.I.S.S means for their software-project or company: - it is the difference between: - lost in chaos of complexity = dysfunctionality - vs a lean stream of running smooth software-company - src: https://homepage.cs.uri.edu/~thenry/resources/unix_art/ch01s07.html - plus test-driven development: 100.000 use case checks tested afterwards automatic & semi-automatic & manual - than that probably works (but then that is what needs to be done anyway to ensure good software quality) - plus: maybe a feedback channel that does not de-motivate - always say something positive first - then the critique
        • signal.org is a very cool mobile & desktop messenger (that usually works pretty well) but: - what is already annoying: if updates per program are 100MBytes and more
 (always downloads the full thing (signal.org desktop client) no differential updates?)
  • word of advice: never blindly follow “the trends”
    • always think for yourself, “does it make sense”?
      • test it if it works for you, if not, drop it, what’s the point?

imho gotta to do both


#linux #gnu #gnulinux #opensource #administration #sysops #rant #software #quality #mess #archive #heise #url #urls #redirects #ci-cd #cd-ci #CICD #CDCI #dev #systems #system #company #developers #developer #buckminster #buckminister

Originally posted at: https://dwaves.de/2022/02/03/rant-open-source-and-the-concept-of-release-early-release-often-or-publish-early-publish-often-continuous-development-continuous-integration-cd-ci-tight-loops-ok-but-still-linking-to-n/

canoodle@nerdpol.ch

Rant: Open Source and the concept of: Release early, release often or publish early & publish often -> continuous development/continuous integration (CD/CI) -> tight loops ok but still - linking to nirvana without redirection & badly written software that everyone uses - another case of - nothing works "ok" - klarer fall von "nichts funktioniert ok"

https://administrator.de/forum/wol-geht-nicht-mit-broadcast-adresse-101944.html

-> it’s catastrophic, when webpages change their url setup


https://www.heise.de/netze/Wake-on-WAN–/artikel/89304/0

because it will result in

“nothing works” “ok”

this does not have nothing to do with luck, but with:

  1. bad url management:
    • wordpress does an pretty good job there, as whenever the user changes the url (more keywords?) it will also redirect from the older past urls to the new url
      • that is how it is SUPPOSED to be for EVERY website of the (not so) “ethernal” part of the internet called www
  2. elastic search seems to be a very very badly written software that does not do any sort of software quality checks?
    • or maybe it’s wrongful integration? (but maybe it just sucks)
    • why is every developer-user using it?
  • PS: as mankind still ponders and evolves (by making mistakes) how to best deal with computers
    • yes someone said “publish early” & “publish often” (doing this with the blog
 also
 often too often and too early X-D)
      • or: “Release early, release often” (wiki)
        • “tight feedback loop between developers and testers or users” (wiki) - yeah sure as a developer that might be a good thing, as a user
 really doubt it
 - there are highly intelligent respected developers that pioneered this concept
 it might work for small teams
 (of one)
        • “This philosophy was popularized by Eric S. Raymond in his 1997 essay The Cathedral and the Bazaar, where Raymond stated “Release early. Release often. And listen to your customers”.[4]”“This philosophy was originally applied to the development of the Linux kernel and other open-source software, but has also been applied to closed source, commercial software development.” “The alternative to the release early, release often philosophy is aiming to provide only polished, bug-free releases.[5] Advocates of RERO question that this would in fact result in higher-quality releases.[4]“
      • has this lead to every developer going in the: continuous development/continuous integration direction? (definately sounds like it)
        • it really should be called CD/CI not CI/CD because first comes the development, then the integration (but well hewego: CI/CD@RedHat)
        • still pondering if it’s really a good idea - well if software quality sticks to UNIX principles of K.I.S.S (most do not and have NO IDEA what non-K.I.S.S means for their software-project or company: - it is the difference between: - lost in chaos of complexity = dysfunctionality - vs a lean stream of running smooth software-company - src: https://homepage.cs.uri.edu/~thenry/resources/unix_art/ch01s07.html - plus test-driven development: 100.000 use case checks tested afterwards automatic & semi-automatic & manual - than that probably works (but then that is what needs to be done anyway to ensure good software quality) - plus: maybe a feedback channel that does not de-motivate - always say something positive first - then the critique
        • signal.org is a very cool mobile & desktop messenger (that usually works pretty well) but: - what is already annoying: if updates per program are 100MBytes and more
 (always downloads the full thing (signal.org desktop client) no differential updates?)
  • word of advice: never blindly follow “the trends”
    • always think for yourself, “does it make sense”?
      • test it if it works for you, if not, drop it, what’s the point?

#linux #gnu #gnulinux #opensource #administration #sysops #rant #software #quality #mess #archive #heise #url #urls #redirects #ci-cd #cd-ci #CICD #CDCI #dev #systems #system #company #developers #developer

Originally posted at: https://dwaves.de/2022/02/03/rant-open-source-and-the-concept-of-release-early-release-often-or-publish-early-publish-often-continuous-development-continuous-integration-cd-ci-tight-loops-ok-but-still-linking-to-n/

canoodle@nerdpol.ch

Rant: Open Source and the concept of: Release early, release often or publish early & publish often -> continuous development/continuous integration (CD/CI) -> tight loops ok but still - linking to nirvana without redirection & badly written software that everyone uses - another case of - nothing works "ok" - klarer fall von "nichts funktioniert ok"

https://administrator.de/forum/wol-geht-nicht-mit-broadcast-adresse-101944.html

-> it’s catastrophic, when webpages change their url setup


https://www.heise.de/netze/Wake-on-WAN–/artikel/89304/0

because it will result in

“nothing works” “ok”

this does not have nothing to do with luck, but with:

  1. bad url management:
    • wordpress does an pretty good job there, as whenever the user changes the url (more keywords?) it will also redirect from the older past urls to the new url
      • that is how it is SUPPOSED to be for EVERY website of the (not so) “ethernal” part of the internet called www
  2. elastic search seems to be a very very badly written software that does not do any sort of software quality checks?
    • why is every developer-user using it?
  • PS: as mankind still ponders and evolves (by making mistakes) how to best deal with computers
    • yes someone said “publish early” & “publish often” (doing this with the blog
 also
 often too often and too early X-D)
      • or: “Release early, release often” (wiki)
        • “tight feedback loop between developers and testers or users” (wiki) - yeah sure as a developer that might be a good thing, as a user
 really doubt it

      • has this lead to every developer going in the: continuous development/continuous integration direction? (definately sounds like it)
        • it really should be called CD/CI not CI/CD because first comes the development, then the integration (but well hewego: CI/CD@RedHat)
        • still pondering if it’s really a good idea - well if software quality sticks to UNIX principles of K.I.S.S (most do not) - plus test-driven development: 100.000 use case checks tested afterwards automatic & semi-automatic & manual - than that probably works (but then that is what needs to be done anyway to ensure good software quality) - plus: maybe a feedback channel that does not de-motivate - always say something positive first - then the critique
        • signal.org is a very cool mobile & desktop messenger (that usually works pretty well) but: - what is already annoying: if updates per program are 100MBytes and more
 (always downloads the full thing (signal.org desktop client) no differential updates?)
  • word of advice: never blindly follow “the trends”
    • always think for yourself, “does it make sense”?
      • test it if it works for you, if not, drop it, what’s the point?

#linux #gnu #gnulinux #opensource #administration #sysops #rant #software #quality #mess #archive #heise #url #urls #redirects #ci-cd #cd-ci #CICD #CDCI #dev

Originally posted at: https://dwaves.de/2022/02/03/rant-open-source-and-the-concept-of-release-early-release-often-or-publish-early-publish-often-continuous-development-continuous-integration-cd-ci-tight-loops-ok-but-still-linking-to-n/

canoodle@nerdpol.ch

linking to nirvana without redirection & badly written software that everyone uses - another case of - nothing works "ok" - klarer fall von "nichts funktioniert ok"

https://administrator.de/forum/wol-geht-nicht-mit-broadcast-adresse-101944.html

-> it’s catastrophic, when webpages change their url setup


https://www.heise.de/netze/Wake-on-WAN–/artikel/89304/0

because it will result in

“nothing works” “ok”

this does not have nothing to do with luck, but with:

  1. bad url management:
    • wordpress does an pretty good job there, as whenever the user changes the url (more keywords?) it will also redirect from the older past urls to the new url
      • that is how it is SUPPOSED to be for EVERY website of the (not so) “ethernal” part of the internet called www
  2. elastic search seems to be a very very badly written software that does not do any sort of software quality checks?
    • why is everyone using it?

#linux #gnu #gnulinux #opensource #administration #sysops #rant #software #quality #mess #archive #heise #url #urls #redirects

Originally posted at: https://dwaves.de/2022/06/03/linking-to-nirvana-without-redirection-badly-written-software-that-everyone-uses-another-case-of-nothing-works-ok-klarer-fall-von-nichts-funktioniert-ok/