Search
405 results for “overengineer”
-
True Engineering Isn't about using tools.
It's in the questions.
Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.
Do you know what that smart-syntax language is doing under the hood?
Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
Do you know what your "schema-less" database sacrifices when concurrency climbs?
Do you know how many runtime hacks exist to make your "native" build work seamlessly?
Do you know how your framework manages threads… or fails to?Many don't. And that's the problem.
We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.
If you're not asking, "What isn’t being said?"
You're not engineering. You're just believing and praying.
AI is a perfect example of many people which hype it but don't understand it.
You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.#TrueEngineering #ThinkBeforeYouCode #SoftwareCraftsmanship #QuestionEverything #BeyondTheFramework #UnderstandTheTools #CodeWithPurpose #SimplicityFirst #CleanArchitecture #DevMindset #EngineeringNotAssembling #TechWithoutMyth #UnderTheHood #CI_CDReality #AutomationTruths #NoMoreMagic #AskTheRightQuestions #AIWithoutUnderstanding #OverengineeringKills #LegacyByDesign #BuildForSimplicity #MinimalistTech
-
True Engineering Isn't about using tools.
It's in the questions.
Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.
Do you know what that smart-syntax language is doing under the hood?
Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
Do you know what your "schema-less" database sacrifices when concurrency climbs?
Do you know how many runtime hacks exist to make your "native" build work seamlessly?
Do you know how your framework manages threads… or fails to?Many don't. And that's the problem.
We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.
If you're not asking, "What isn’t being said?"
You're not engineering. You're just believing and praying.
AI is a perfect example of many people which hype it but don't understand it.
You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.#TrueEngineering #ThinkBeforeYouCode #SoftwareCraftsmanship #QuestionEverything #BeyondTheFramework #UnderstandTheTools #CodeWithPurpose #SimplicityFirst #CleanArchitecture #DevMindset #EngineeringNotAssembling #TechWithoutMyth #UnderTheHood #CI_CDReality #AutomationTruths #NoMoreMagic #AskTheRightQuestions #AIWithoutUnderstanding #OverengineeringKills #LegacyByDesign #BuildForSimplicity #MinimalistTech
-
True Engineering Isn't about using tools.
It's in the questions.
Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.
Do you know what that smart-syntax language is doing under the hood?
Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
Do you know what your "schema-less" database sacrifices when concurrency climbs?
Do you know how many runtime hacks exist to make your "native" build work seamlessly?
Do you know how your framework manages threads… or fails to?Many don't. And that's the problem.
We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.
If you're not asking, "What isn’t being said?"
You're not engineering. You're just believing and praying.
AI is a perfect example of many people which hype it but don't understand it.
You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.#TrueEngineering #ThinkBeforeYouCode #SoftwareCraftsmanship #QuestionEverything #BeyondTheFramework #UnderstandTheTools #CodeWithPurpose #SimplicityFirst #CleanArchitecture #DevMindset #EngineeringNotAssembling #TechWithoutMyth #UnderTheHood #CI_CDReality #AutomationTruths #NoMoreMagic #AskTheRightQuestions #AIWithoutUnderstanding #OverengineeringKills #LegacyByDesign #BuildForSimplicity #MinimalistTech
-
True Engineering Isn't about using tools.
It's in the questions.
Too often, I see "engineering" reduced to assembling frameworks like IKEA furniture, follow the docs, trust the tool, ship it. But real engineering begins where the documentation ends.
Do you know what that smart-syntax language is doing under the hood?
Do you know how your beloved build tool behaves when it comes to automations and generic CI/CD pipelines?
Do you know what your "schema-less" database sacrifices when concurrency climbs?
Do you know how many runtime hacks exist to make your "native" build work seamlessly?
Do you know how your framework manages threads… or fails to?Many don't. And that's the problem.
We've built castles on sand because the sand came with good tutorials. Engineering isn't about how much you can plug in. It's about how much you understand, especially the parts no one talks about.
If you're not asking, "What isn’t being said?"
You're not engineering. You're just believing and praying.
AI is a perfect example of many people which hype it but don't understand it.
You have incidents, bugs, complexity, legacy and need time for maintenance or migrations? Then you build your system wrong. Technology should help and not hinder us. We need to focus on simplicity, not on overengineering.#TrueEngineering #ThinkBeforeYouCode #SoftwareCraftsmanship #QuestionEverything #BeyondTheFramework #UnderstandTheTools #CodeWithPurpose #SimplicityFirst #CleanArchitecture #DevMindset #EngineeringNotAssembling #TechWithoutMyth #UnderTheHood #CI_CDReality #AutomationTruths #NoMoreMagic #AskTheRightQuestions #AIWithoutUnderstanding #OverengineeringKills #LegacyByDesign #BuildForSimplicity #MinimalistTech
-
Struggling in product development is trendy now, so why bother improving? Let’s embrace the mediocrity. It’s mainstream. A circus of borrowed frameworks, questionable dependencies, and collective delusion. If we can’t get our own code right, what makes us trust everyone else’s? Same with business processes. Are we keeping ourselves randomly busy? A small hint: Using fewer thing means also fewer headaches 😇 Get back to basics.
#KISS #YAGNI #DRY #ProductDevelopment #Overengineering #KeepItSimple #FrameworkMadness #TechSatire #SoftwareChaos #BackToBasics #LessIsMore #BusinessProcesses #EfficiencyMatters #SimplifyComplexity
-
After a couple of listens, I can confidently say that Dan Lancaster fucked up so hard on Swallow The Sun's new album, Shining:
https://centurymedia.bandcamp.com/album/shining-24-bit-hd-audio
Almost every instrument, even the vocals have unnecessary effects on them. The drums, the vocals and the guitars sound artificial and overengineered. I didn't like the new sound profile at all.
-
After a couple of listens, I can confidently say that Dan Lancaster fucked up so hard on Swallow The Sun's new album, Shining:
https://centurymedia.bandcamp.com/album/shining-24-bit-hd-audio
Almost every instrument, even the vocals have unnecessary effects on them. The drums, the vocals and the guitars sound artificial and overengineered. I didn't like the new sound profile at all.
-
Dear #CircleCI, I'd like to inform you that I don't need another "#AI" shit. What I'd really appreciate, though, is being able to actually see the text rather than some colorful noise on your overengineered site.
(Yes, I know I can download the logs to see them. Also, not my package, not my choice of provider.)
Also, if anyone know how to fix this in #Firefox, since it's not the first site where I'm seeing this…
-
My trusty #yamakawa DVD player finally failed (dried caps) with glibberish video output and I got a 15€ USB DVD drive for my #OSMC #kodi #raspberrypi driven fill-house-with-music-and-light rack instead. While at it, I did some cable-management to reduce the mess.
The #HarmanKardon hk6100/hk6200 are great, cheap, and easy to fix (got them in broken for cheap). The #szone 4 zone mixer was cheap/broken as well and requied some mechanical fix and mainly contact cleaning. Its great to route 4.0 surround sound and a bluetooth receiver and a CD player to 4 different amplifiers (3x harman kardon for different rooms and 1 subwoofer) and adjust volue and tone indivisually. The subwoofer (with built-in amp) was picked up from a pile of electronic junk - it had a radio receiver to be used with a soundbar. I just removed that and connected an analog audio input to the amplifier board.
As usual, the whole setup is a bit overengineered...
-
My trusty #yamakawa DVD player finally failed (dried caps) with glibberish video output and I got a 15€ USB DVD drive for my #OSMC #kodi #raspberrypi driven fill-house-with-music-and-light rack instead. While at it, I did some cable-management to reduce the mess.
The #HarmanKardon hk6100/hk6200 are great, cheap, and easy to fix (got them in broken for cheap). The #szone 4 zone mixer was cheap/broken as well and requied some mechanical fix and mainly contact cleaning. Its great to route 4.0 surround sound and a bluetooth receiver and a CD player to 4 different amplifiers (3x harman kardon for different rooms and 1 subwoofer) and adjust volue and tone indivisually. The subwoofer (with built-in amp) was picked up from a pile of electronic junk - it had a radio receiver to be used with a soundbar. I just removed that and connected an analog audio input to the amplifier board.
As usual, the whole setup is a bit overengineered...
-
My trusty #yamakawa DVD player finally failed (dried caps) with glibberish video output and I got a 15€ USB DVD drive for my #OSMC #kodi #raspberrypi driven fill-house-with-music-and-light rack instead. While at it, I did some cable-management to reduce the mess.
The #HarmanKardon hk6100/hk6200 are great, cheap, and easy to fix (got them in broken for cheap). The #szone 4 zone mixer was cheap/broken as well and requied some mechanical fix and mainly contact cleaning. Its great to route 4.0 surround sound and a bluetooth receiver and a CD player to 4 different amplifiers (3x harman kardon for different rooms and 1 subwoofer) and adjust volue and tone indivisually. The subwoofer (with built-in amp) was picked up from a pile of electronic junk - it had a radio receiver to be used with a soundbar. I just removed that and connected an analog audio input to the amplifier board.
As usual, the whole setup is a bit overengineered...
-
My trusty #yamakawa DVD player finally failed (dried caps) with glibberish video output and I got a 15€ USB DVD drive for my #OSMC #kodi #raspberrypi driven fill-house-with-music-and-light rack instead. While at it, I did some cable-management to reduce the mess.
The #HarmanKardon hk6100/hk6200 are great, cheap, and easy to fix (got them in broken for cheap). The #szone 4 zone mixer was cheap/broken as well and requied some mechanical fix and mainly contact cleaning. Its great to route 4.0 surround sound and a bluetooth receiver and a CD player to 4 different amplifiers (3x harman kardon for different rooms and 1 subwoofer) and adjust volue and tone indivisually. The subwoofer (with built-in amp) was picked up from a pile of electronic junk - it had a radio receiver to be used with a soundbar. I just removed that and connected an analog audio input to the amplifier board.
As usual, the whole setup is a bit overengineered...
-
My trusty #yamakawa DVD player finally failed (dried caps) with glibberish video output and I got a 15€ USB DVD drive for my #OSMC #kodi #raspberrypi driven fill-house-with-music-and-light rack instead. While at it, I did some cable-management to reduce the mess.
The #HarmanKardon hk6100/hk6200 are great, cheap, and easy to fix (got them in broken for cheap). The #szone 4 zone mixer was cheap/broken as well and requied some mechanical fix and mainly contact cleaning. Its great to route 4.0 surround sound and a bluetooth receiver and a CD player to 4 different amplifiers (3x harman kardon for different rooms and 1 subwoofer) and adjust volue and tone indivisually. The subwoofer (with built-in amp) was picked up from a pile of electronic junk - it had a radio receiver to be used with a soundbar. I just removed that and connected an analog audio input to the amplifier board.
As usual, the whole setup is a bit overengineered...
-
I completed the first draft of my first blog post ever for my personal gooseandquill.blog! It's a tutorial that covers setting up rootless #podman on #GuixSystem then writing and building your first #guile package to produce a container image runnable on Podman and #kubernetes. I'm looking for beta readers!
Because I run #OpenShift at home, I plan to launch my blog with a little overengineered fun courtesy of #shipwright! It uses #buildah and #tekton under the hood.
-
Vedin juuri meidän @dude:n porukalle 19 kalvon luennon saavutettavuudesta.
Olen tehnyt saavutettavaa webiä kohta 20 vuotta. Kun puoliso on kuurosokea, saavutettavuus ei ole vain ammatillinen asia, vaan kirjaimellisesti lähellä sydäntä. On hienoa nähdä, että saavutettavuus on vihdoin ja viimein kirjattu Suomen lakiin: 28.6.2025 eteenpäin digipalvelulain uudet vaatimukset koskevat myös yksityisiä yrityksiä, ei enää vain julkishallintoa.
Miksi tämä on tärkeää?
- Internet kuuluu kaikille, ei vain harvoille
- Saavutettavuus parantaa käyttökokemusta aivan kaikille, myös vammattomille
- Yksinkertainen, selkeä ja hyvin suunniteltu ratkaisu on yleensä saavutettavin
- Saavutettavuus on tärkeä osa arvomaailmaa, laatua ja vastuullisuutta
- Saavutettavuus ei ole "lisäominaisuus", vaan saavuttamaton = rikkiKäytännössä uuden lain voimaan astumisen myötä säädökset koskevat esimerkiksi verkkokauppoja, pankkipalveluita, suoratoistopalveluita, lippukauppoja, viestintäsovelluksia, yli 10 henkilön yrityksen verkkosivuja. Digipalvelulain taustalla olevat WCAG-standardi ja POUR-periaatteet määrittelevät mm. kontrastin, käytössä olevat värit, näppäimistökäytön, lomakkeet, selkeät otsikot ja vaihtoehdot pelkälle värille. Miniminä voidaan pitää mm. saavutettavuusselostetta, palautekanavaa ja WCAG 2.2 A/AA-tason vaatimukset.
Suunnittelussa saavutettavuus tarkoittaa mm.
- Riittävää kontrastia ja selkeää typografiaa
- Johdonmukaisuutta
- Tekniikan ja käytettävyyden riittävää miettimistä taustalla
- Että sisältö kulkee loogisesti kaikille apuvälineilleTeknisessä toteutuksessa saavutettavuus ei vaadi mitään taikatemppuja. Validi ja semanttinen HTML, toimiva näppäimistönavigaatio, testaus ja suorituskyky kun ovat hyppysissä, pääsee jo pitkälle. Saavutettavuutta ei kannata overengineerata, sillä silloin tulee synnyttäneeksi enemmän ongelmia kuin ratkaisuja.
Meillä Dudella saavutettavuus on ollut yksi tärkeimmistä arvoista alusta asti. Nyt laki asettaa vähimmäistason, mutta näkisin sen enemmän mahdollisuutena kuin pakkona: saavutettavuus on hyvää palvelua, joka hyödyttää käyttäjiä ja yrityksiä yhtä aikaa.
👉 Lisätietoa: https://www.saavutettavuusvaatimukset.fi/fi/digipalvelulain-vaatimukset (mahdollisesti myös pian dude.fi blogin puolella)
PS. Ennen kaikkea tykkäsin jälleen tehdä tyylikkäät (ja kaikille saavutettavat kalvot!). Saavutettavuuden ei tarvitse olla tylsää!
-
Vedin juuri meidän @dude:n porukalle 19 kalvon luennon saavutettavuudesta.
Olen tehnyt saavutettavaa webiä kohta 20 vuotta. Kun puoliso on kuurosokea, saavutettavuus ei ole vain ammatillinen asia, vaan kirjaimellisesti lähellä sydäntä. On hienoa nähdä, että saavutettavuus on vihdoin ja viimein kirjattu Suomen lakiin: 28.6.2025 eteenpäin digipalvelulain uudet vaatimukset koskevat myös yksityisiä yrityksiä, ei enää vain julkishallintoa.
Miksi tämä on tärkeää?
- Internet kuuluu kaikille, ei vain harvoille
- Saavutettavuus parantaa käyttökokemusta aivan kaikille, myös vammattomille
- Yksinkertainen, selkeä ja hyvin suunniteltu ratkaisu on yleensä saavutettavin
- Saavutettavuus on tärkeä osa arvomaailmaa, laatua ja vastuullisuutta
- Saavutettavuus ei ole "lisäominaisuus", vaan saavuttamaton = rikkiKäytännössä uuden lain voimaan astumisen myötä säädökset koskevat esimerkiksi verkkokauppoja, pankkipalveluita, suoratoistopalveluita, lippukauppoja, viestintäsovelluksia, yli 10 henkilön yrityksen verkkosivuja. Digipalvelulain taustalla olevat WCAG-standardi ja POUR-periaatteet määrittelevät mm. kontrastin, käytössä olevat värit, näppäimistökäytön, lomakkeet, selkeät otsikot ja vaihtoehdot pelkälle värille. Miniminä voidaan pitää mm. saavutettavuusselostetta, palautekanavaa ja WCAG 2.2 A/AA-tason vaatimukset.
Suunnittelussa saavutettavuus tarkoittaa mm.
- Riittävää kontrastia ja selkeää typografiaa
- Johdonmukaisuutta
- Tekniikan ja käytettävyyden riittävää miettimistä taustalla
- Että sisältö kulkee loogisesti kaikille apuvälineilleTeknisessä toteutuksessa saavutettavuus ei vaadi mitään taikatemppuja. Validi ja semanttinen HTML, toimiva näppäimistönavigaatio, testaus ja suorituskyky kun ovat hyppysissä, pääsee jo pitkälle. Saavutettavuutta ei kannata overengineerata, sillä silloin tulee synnyttäneeksi enemmän ongelmia kuin ratkaisuja.
Meillä Dudella saavutettavuus on ollut yksi tärkeimmistä arvoista alusta asti. Nyt laki asettaa vähimmäistason, mutta näkisin sen enemmän mahdollisuutena kuin pakkona: saavutettavuus on hyvää palvelua, joka hyödyttää käyttäjiä ja yrityksiä yhtä aikaa.
👉 Lisätietoa: https://www.saavutettavuusvaatimukset.fi/fi/digipalvelulain-vaatimukset (mahdollisesti myös pian dude.fi blogin puolella)
PS. Ennen kaikkea tykkäsin jälleen tehdä tyylikkäät (ja kaikille saavutettavat kalvot!). Saavutettavuuden ei tarvitse olla tylsää!
-
Vedin juuri meidän @dude:n porukalle 19 kalvon luennon saavutettavuudesta.
Olen tehnyt saavutettavaa webiä kohta 20 vuotta. Kun puoliso on kuurosokea, saavutettavuus ei ole vain ammatillinen asia, vaan kirjaimellisesti lähellä sydäntä. On hienoa nähdä, että saavutettavuus on vihdoin ja viimein kirjattu Suomen lakiin: 28.6.2025 eteenpäin digipalvelulain uudet vaatimukset koskevat myös yksityisiä yrityksiä, ei enää vain julkishallintoa.
Miksi tämä on tärkeää?
- Internet kuuluu kaikille, ei vain harvoille
- Saavutettavuus parantaa käyttökokemusta aivan kaikille, myös vammattomille
- Yksinkertainen, selkeä ja hyvin suunniteltu ratkaisu on yleensä saavutettavin
- Saavutettavuus on tärkeä osa arvomaailmaa, laatua ja vastuullisuutta
- Saavutettavuus ei ole "lisäominaisuus", vaan saavuttamaton = rikkiKäytännössä uuden lain voimaan astumisen myötä säädökset koskevat esimerkiksi verkkokauppoja, pankkipalveluita, suoratoistopalveluita, lippukauppoja, viestintäsovelluksia, yli 10 henkilön yrityksen verkkosivuja. Digipalvelulain taustalla olevat WCAG-standardi ja POUR-periaatteet määrittelevät mm. kontrastin, käytössä olevat värit, näppäimistökäytön, lomakkeet, selkeät otsikot ja vaihtoehdot pelkälle värille. Miniminä voidaan pitää mm. saavutettavuusselostetta, palautekanavaa ja WCAG 2.2 A/AA-tason vaatimukset.
Suunnittelussa saavutettavuus tarkoittaa mm.
- Riittävää kontrastia ja selkeää typografiaa
- Johdonmukaisuutta
- Tekniikan ja käytettävyyden riittävää miettimistä taustalla
- Että sisältö kulkee loogisesti kaikille apuvälineilleTeknisessä toteutuksessa saavutettavuus ei vaadi mitään taikatemppuja. Validi ja semanttinen HTML, toimiva näppäimistönavigaatio, testaus ja suorituskyky kun ovat hyppysissä, pääsee jo pitkälle. Saavutettavuutta ei kannata overengineerata, sillä silloin tulee synnyttäneeksi enemmän ongelmia kuin ratkaisuja.
Meillä Dudella saavutettavuus on ollut yksi tärkeimmistä arvoista alusta asti. Nyt laki asettaa vähimmäistason, mutta näkisin sen enemmän mahdollisuutena kuin pakkona: saavutettavuus on hyvää palvelua, joka hyödyttää käyttäjiä ja yrityksiä yhtä aikaa.
👉 Lisätietoa: https://www.saavutettavuusvaatimukset.fi/fi/digipalvelulain-vaatimukset (mahdollisesti myös pian dude.fi blogin puolella)
PS. Ennen kaikkea tykkäsin jälleen tehdä tyylikkäät (ja kaikille saavutettavat kalvot!). Saavutettavuuden ei tarvitse olla tylsää!
-
Vedin juuri meidän @dude:n porukalle 19 kalvon luennon saavutettavuudesta.
Olen tehnyt saavutettavaa webiä kohta 20 vuotta. Kun puoliso on kuurosokea, saavutettavuus ei ole vain ammatillinen asia, vaan kirjaimellisesti lähellä sydäntä. On hienoa nähdä, että saavutettavuus on vihdoin ja viimein kirjattu Suomen lakiin: 28.6.2025 eteenpäin digipalvelulain uudet vaatimukset koskevat myös yksityisiä yrityksiä, ei enää vain julkishallintoa.
Miksi tämä on tärkeää?
- Internet kuuluu kaikille, ei vain harvoille
- Saavutettavuus parantaa käyttökokemusta aivan kaikille, myös vammattomille
- Yksinkertainen, selkeä ja hyvin suunniteltu ratkaisu on yleensä saavutettavin
- Saavutettavuus on tärkeä osa arvomaailmaa, laatua ja vastuullisuutta
- Saavutettavuus ei ole "lisäominaisuus", vaan saavuttamaton = rikkiKäytännössä uuden lain voimaan astumisen myötä säädökset koskevat esimerkiksi verkkokauppoja, pankkipalveluita, suoratoistopalveluita, lippukauppoja, viestintäsovelluksia, yli 10 henkilön yrityksen verkkosivuja. Digipalvelulain taustalla olevat WCAG-standardi ja POUR-periaatteet määrittelevät mm. kontrastin, käytössä olevat värit, näppäimistökäytön, lomakkeet, selkeät otsikot ja vaihtoehdot pelkälle värille. Miniminä voidaan pitää mm. saavutettavuusselostetta, palautekanavaa ja WCAG 2.2 A/AA-tason vaatimukset.
Suunnittelussa saavutettavuus tarkoittaa mm.
- Riittävää kontrastia ja selkeää typografiaa
- Johdonmukaisuutta
- Tekniikan ja käytettävyyden riittävää miettimistä taustalla
- Että sisältö kulkee loogisesti kaikille apuvälineilleTeknisessä toteutuksessa saavutettavuus ei vaadi mitään taikatemppuja. Validi ja semanttinen HTML, toimiva näppäimistönavigaatio, testaus ja suorituskyky kun ovat hyppysissä, pääsee jo pitkälle. Saavutettavuutta ei kannata overengineerata, sillä silloin tulee synnyttäneeksi enemmän ongelmia kuin ratkaisuja.
Meillä Dudella saavutettavuus on ollut yksi tärkeimmistä arvoista alusta asti. Nyt laki asettaa vähimmäistason, mutta näkisin sen enemmän mahdollisuutena kuin pakkona: saavutettavuus on hyvää palvelua, joka hyödyttää käyttäjiä ja yrityksiä yhtä aikaa.
👉 Lisätietoa: https://www.saavutettavuusvaatimukset.fi/fi/digipalvelulain-vaatimukset (mahdollisesti myös pian dude.fi blogin puolella)
PS. Ennen kaikkea tykkäsin jälleen tehdä tyylikkäät (ja kaikille saavutettavat kalvot!). Saavutettavuuden ei tarvitse olla tylsää!
-
Vedin juuri meidän @dude:n porukalle 19 kalvon luennon saavutettavuudesta.
Olen tehnyt saavutettavaa webiä kohta 20 vuotta. Kun puoliso on kuurosokea, saavutettavuus ei ole vain ammatillinen asia, vaan kirjaimellisesti lähellä sydäntä. On hienoa nähdä, että saavutettavuus on vihdoin ja viimein kirjattu Suomen lakiin: 28.6.2025 eteenpäin digipalvelulain uudet vaatimukset koskevat myös yksityisiä yrityksiä, ei enää vain julkishallintoa.
Miksi tämä on tärkeää?
- Internet kuuluu kaikille, ei vain harvoille
- Saavutettavuus parantaa käyttökokemusta aivan kaikille, myös vammattomille
- Yksinkertainen, selkeä ja hyvin suunniteltu ratkaisu on yleensä saavutettavin
- Saavutettavuus on tärkeä osa arvomaailmaa, laatua ja vastuullisuutta
- Saavutettavuus ei ole "lisäominaisuus", vaan saavuttamaton = rikkiKäytännössä uuden lain voimaan astumisen myötä säädökset koskevat esimerkiksi verkkokauppoja, pankkipalveluita, suoratoistopalveluita, lippukauppoja, viestintäsovelluksia, yli 10 henkilön yrityksen verkkosivuja. Digipalvelulain taustalla olevat WCAG-standardi ja POUR-periaatteet määrittelevät mm. kontrastin, käytössä olevat värit, näppäimistökäytön, lomakkeet, selkeät otsikot ja vaihtoehdot pelkälle värille. Miniminä voidaan pitää mm. saavutettavuusselostetta, palautekanavaa ja WCAG 2.2 A/AA-tason vaatimukset.
Suunnittelussa saavutettavuus tarkoittaa mm.
- Riittävää kontrastia ja selkeää typografiaa
- Johdonmukaisuutta
- Tekniikan ja käytettävyyden riittävää miettimistä taustalla
- Että sisältö kulkee loogisesti kaikille apuvälineilleTeknisessä toteutuksessa saavutettavuus ei vaadi mitään taikatemppuja. Validi ja semanttinen HTML, toimiva näppäimistönavigaatio, testaus ja suorituskyky kun ovat hyppysissä, pääsee jo pitkälle. Saavutettavuutta ei kannata overengineerata, sillä silloin tulee synnyttäneeksi enemmän ongelmia kuin ratkaisuja.
Meillä Dudella saavutettavuus on ollut yksi tärkeimmistä arvoista alusta asti. Nyt laki asettaa vähimmäistason, mutta näkisin sen enemmän mahdollisuutena kuin pakkona: saavutettavuus on hyvää palvelua, joka hyödyttää käyttäjiä ja yrityksiä yhtä aikaa.
👉 Lisätietoa: https://www.saavutettavuusvaatimukset.fi/fi/digipalvelulain-vaatimukset (mahdollisesti myös pian dude.fi blogin puolella)
PS. Ennen kaikkea tykkäsin jälleen tehdä tyylikkäät (ja kaikille saavutettavat kalvot!). Saavutettavuuden ei tarvitse olla tylsää!
-
GardensTale’s Top Ten(ish) Album Art of 2023
By GardensTale
As we drag our bloated stomachs from the dinner table of Listurnalia to the couch of January, it’s easy to forget that dessert has yet been served. Like a Monty Python waiter with a thin mint, the artwork article is here to ensure everyone’s entrails are catapulted across the living room in a shower of vomitus and viscera. Our yearly celebration of metal visuals is a wonderfully diverse one, if I say so myself, with a wide range of color palettes, moods and styles for you to feast your eyes on. This is the latest I’ve ever written this article, but spending a week among the clutches of Transsylvanian vampires held me up in completing it sooner.
The rules, the rules, the rules. Order must be established lest the resultant list means nothing at all.
- If we haven’t reviewed it, included it in a filter piece, or wrote a TYMHM article about it, it won’t be included. I’ve made one exception this year, because I can, but mostly because the review has just been sitting in the queue for ages as of this writing. So it’s been reviewed, just not published. Loophole!
- One entry per artist. This turned out to be easier than any other year. My stricter and quicker selection process had no doubles at all! Perhaps Kantor didn’t have much time this year.
- Original art only. While this does include photography (in vain, I’m afraid), it does not include a painting from 1739 with a logo slapped on. Be better than that, bands!
- And a new rule that is guaranteed to bite me in the ass at some point: no AI art! While there are ethical use cases for AI art, album covers aren’t one of them, and if I can at all help it I will not add fuel to that fire.
THE WORST
#3. Eternity // Mundicide — I didn’t want to just do artwork where the band clearly doesn’t give a fuck. That’s too easy. The joy is when a band has put in the effort to make something uniquely idiotic, and that is where Eternity’s cover comes in. How did no one at any point in the creation of this artwork say “Hey guys? This looks incredibly stupid.” The little arms, man. It’s like the world’s worst rendition of “It’s a small world after all.”
#2. Secret Rule // Uninverse — This is the unpublished exception and I’m sure you can see why I felt the need to make it. The amount of unskilled photoshop here is downright grotesque. Band photo album covers are rarely advisable, but with these outfits and poses, peak awkward is achieved several times over. Add the weird band name with overengineered logo and illogical pun of an album title and the cringe is complete.
#1. Savage Grace // Sign of the Cross — This is How Not To Composition 101. Everything on this cover is in the wrong place at the wrong scale. Not to mention, the typefacing is a disaster. Unexplained additional text, fonts that don’t match, vertical text, you name it, Savage Grace has got it. The lady knight in the foreground looks like she’s taking a very satisfying dump, and do try not to spray your drink across your screen when you zoom in on the meme-worthy face on the floor. An unmitigated disaster.
THE BEST
#(ish). Varathron // The Crimson Temple (artist: Paolo Girardi) — Girardi has been doing this for well over a decade and along with Burke, Kantor and Chioreanu is one of the most recognizable artists in the scene. This one is one of his more horrifying scenes, a grisly and visceral mass sacrifice. The many details and surreal horror recalls Hieronymous Bosch, but the clever composition draws the eye back to the crimson pool and the screaming evil god-face.
#10. Hexvessel // Polar Veil (artist: Benjamin König) — I’ve made it no secret that I love surreal art, and this deeply intriguing illustration by Benjamin König fits that bill completely. Both the misty blue sky and the black of night fit perfectly well over the idyllic snowy town, but the way the split forms a curious celestial figure is inspired. The largely monochrome coloration gives the art a sense of cold stillness, hovering between serenity and grim portent.
#9. Sanguine Glacialis // Maladaptive Daydreaming (artist: Alex O’Dowd) — This is probably the most meta we’re going to get today. I love the contrast of the dark, bleak room and forlorn painter with the glowing, overspilling painting full of warmth and life. The logo and title placement are uncommonly nice as well here. It’s such a lovely work of art I can even overlook the fact that the woman is clearly not dressed for the job at hand.
#8. Raider // Trial by Chaos (artist: Mitchell Nolte) — It’s difficult making art that’s purposefully crowded but still easy to read. Mitchell Nolte, who was featured here with last year’s excellent Dawnwalker art, manages with ingenious color use, creating contrast with the warrior’s fiery aura to spotlight him in the center of a writhing mass of monsters. Wielding a broadsword in one hand and strangling a multi-eyed monster snake with the other solidifies the subject’s status as one of the most badass bastards in metal art this year.
#7. Fire Down Below // Low Desert Surf Club (artist: Christi du Toit) — Comic style illustrations are a rare treat in metal, and those done well are rarer still. Christi du Toit clearly has a knack for wondrous, intriguing layouts. I love the sharp shading and color palette, and the atypical, adventurous feel the illustration exudes. I read a lot of webcomics, and if I saw this on a cover page I’d already be hooked.
#6. Grant the Sun // Voyage (artist: William Hay) — So many metal covers are grim, dark, foreboding or violent. The art for Voyage, on the other hand, is a quirky and colorful affair. The diving panda and the anglerfish make for an interesting dichotomy, a collision of worlds that are never supposed to meet. But the wink and smile belies the beautiful details, such as the streams of air escaping the panda’s mouth or the various level of refraction in the turbulent waters.
#5. Wormhole // Almost Human (artist: Adam Burke) — Adam Burke is usually the go-to guy for sci-fi cosmoscapes, but his strongest artwork this year graces the cover of Wormhole, or as I’m told the correct pronunciation is, WWWWOOOOOOORRRRRMMHHHOOOOOOOOLLLEEEEEE. What I especially like about this art is how much story it suggests. Either something that wasn’t human is in the midst of becoming gradually more so, or someone is shedding their humanity (as well as skin). Either way, it has something to do with the rhino beetle, and I can’t wait to find out what.
#4. Evile // The Unknown (artist: Eliran Kantor) — Few artists could make me include a cover that is like 75% black. Kantor can, though. The slim beam of light cast by a cracked cellar door is the only light for the father and son, surrounded by inky blackness. Kantor is an expert at expressive faces, and this pair ooze fear and despair. It’s an effective and haunting image that uses black as a tool to tell a story. If only the album were as great as the artwork.
#3. Slomatics // Strontium Fields (artist: Ryan Lesser) — I knew this had to be on the list the moment I saw it. I’ll even forgive the lack of album and band titles. The breathless figure reminiscent of the Statue of Liberty, her eyes beaming and her hair waving as if underwater, stands in stark contrast with the glistening embodiment of cosmic horror behind her. A clever trick that enhances that contrast, besides the clash in color, is the difference in shading. The flesh monster has been rendered in angry blotches, the statuesque woman in more marble-like tones. Don’t forget to check out the full-size art in the review!
#2. Harm’s Way // Common Suffering (artist: Corran Brownlee) — This stark, haunting piece makes it abundantly clear that “It’s Raining Men” is a horror scenario. The dreamlike surrealism and the apocalyptic climax clash into a nightmare depiction that took my breath the first time I saw it, and still fills me with an appropriate excess of dread when I look at it now. Rendering it entirely in black & white and cleverly constraining the cloud of people with a frame makes the scene feel both immense and claustrophobic.
#1. Deadly Carnage // Endless Blue (artist: Alexios Ciancio) — Though this list is ever a contentious one, I don’t think much protest will be levied at the winner this year. Graphic designer Alexios Ciancio is the vocalist and guitarist for Deadly Carnage, making this the rare treat of a band member designing their own album’s cover. Inspired by traditional Japanese art, Ciancio has created an absolute feast for the eyes. Though the portrait-oriented illustration leaves a lot of blank space on the sides, the dynamic composition that spills out the frame grants sumptuous life and vitality. The spectral nature of the cresting whale elevates the scene above the earthly and into the ethereal, which the music inside encapsulates. And whereas many artworks suffer from zooming in too much, the crisp lines and myriad beautiful details keep me scrolling endlessly across the canvas, from the swans flying out of the frame to the upended rowboats. A visual masterpiece.
#2023 #DeadlyCarnage #Eternity #Evile #FireDownBelow #GrantTheSun #HarmSWay #Hexvessel #Raider #SanguineGlacialis #SavageGrace #SecretRule #Slomatics #Varathron #Wormhole
-
GardensTale’s Top Ten(ish) Album Art of 2023
By GardensTale
As we drag our bloated stomachs from the dinner table of Listurnalia to the couch of January, it’s easy to forget that dessert has yet been served. Like a Monty Python waiter with a thin mint, the artwork article is here to ensure everyone’s entrails are catapulted across the living room in a shower of vomitus and viscera. Our yearly celebration of metal visuals is a wonderfully diverse one, if I say so myself, with a wide range of color palettes, moods and styles for you to feast your eyes on. This is the latest I’ve ever written this article, but spending a week among the clutches of Transsylvanian vampires held me up in completing it sooner.
The rules, the rules, the rules. Order must be established lest the resultant list means nothing at all.
- If we haven’t reviewed it, included it in a filter piece, or wrote a TYMHM article about it, it won’t be included. I’ve made one exception this year, because I can, but mostly because the review has just been sitting in the queue for ages as of this writing. So it’s been reviewed, just not published. Loophole!
- One entry per artist. This turned out to be easier than any other year. My stricter and quicker selection process had no doubles at all! Perhaps Kantor didn’t have much time this year.
- Original art only. While this does include photography (in vain, I’m afraid), it does not include a painting from 1739 with a logo slapped on. Be better than that, bands!
- And a new rule that is guaranteed to bite me in the ass at some point: no AI art! While there are ethical use cases for AI art, album covers aren’t one of them, and if I can at all help it I will not add fuel to that fire.
THE WORST
#3. Eternity // Mundicide — I didn’t want to just do artwork where the band clearly doesn’t give a fuck. That’s too easy. The joy is when a band has put in the effort to make something uniquely idiotic, and that is where Eternity’s cover comes in. How did no one at any point in the creation of this artwork say “Hey guys? This looks incredibly stupid.” The little arms, man. It’s like the world’s worst rendition of “It’s a small world after all.”
#2. Secret Rule // Uninverse — This is the unpublished exception and I’m sure you can see why I felt the need to make it. The amount of unskilled photoshop here is downright grotesque. Band photo album covers are rarely advisable, but with these outfits and poses, peak awkward is achieved several times over. Add the weird band name with overengineered logo and illogical pun of an album title and the cringe is complete.
#1. Savage Grace // Sign of the Cross — This is How Not To Composition 101. Everything on this cover is in the wrong place at the wrong scale. Not to mention, the typefacing is a disaster. Unexplained additional text, fonts that don’t match, vertical text, you name it, Savage Grace has got it. The lady knight in the foreground looks like she’s taking a very satisfying dump, and do try not to spray your drink across your screen when you zoom in on the meme-worthy face on the floor. An unmitigated disaster.
THE BEST
#(ish). Varathron // The Crimson Temple (artist: Paolo Girardi) — Girardi has been doing this for well over a decade and along with Burke, Kantor and Chioreanu is one of the most recognizable artists in the scene. This one is one of his more horrifying scenes, a grisly and visceral mass sacrifice. The many details and surreal horror recalls Hieronymous Bosch, but the clever composition draws the eye back to the crimson pool and the screaming evil god-face.
#10. Hexvessel // Polar Veil (artist: Benjamin König) — I’ve made it no secret that I love surreal art, and this deeply intriguing illustration by Benjamin König fits that bill completely. Both the misty blue sky and the black of night fit perfectly well over the idyllic snowy town, but the way the split forms a curious celestial figure is inspired. The largely monochrome coloration gives the art a sense of cold stillness, hovering between serenity and grim portent.
#9. Sanguine Glacialis // Maladaptive Daydreaming (artist: Alex O’Dowd) — This is probably the most meta we’re going to get today. I love the contrast of the dark, bleak room and forlorn painter with the glowing, overspilling painting full of warmth and life. The logo and title placement are uncommonly nice as well here. It’s such a lovely work of art I can even overlook the fact that the woman is clearly not dressed for the job at hand.
#8. Raider // Trial by Chaos (artist: Mitchell Nolte) — It’s difficult making art that’s purposefully crowded but still easy to read. Mitchell Nolte, who was featured here with last year’s excellent Dawnwalker art, manages with ingenious color use, creating contrast with the warrior’s fiery aura to spotlight him in the center of a writhing mass of monsters. Wielding a broadsword in one hand and strangling a multi-eyed monster snake with the other solidifies the subject’s status as one of the most badass bastards in metal art this year.
#7. Fire Down Below // Low Desert Surf Club (artist: Christi du Toit) — Comic style illustrations are a rare treat in metal, and those done well are rarer still. Christi du Toit clearly has a knack for wondrous, intriguing layouts. I love the sharp shading and color palette, and the atypical, adventurous feel the illustration exudes. I read a lot of webcomics, and if I saw this on a cover page I’d already be hooked.
#6. Grant the Sun // Voyage (artist: William Hay) — So many metal covers are grim, dark, foreboding or violent. The art for Voyage, on the other hand, is a quirky and colorful affair. The diving panda and the anglerfish make for an interesting dichotomy, a collision of worlds that are never supposed to meet. But the wink and smile belies the beautiful details, such as the streams of air escaping the panda’s mouth or the various level of refraction in the turbulent waters.
#5. Wormhole // Almost Human (artist: Adam Burke) — Adam Burke is usually the go-to guy for sci-fi cosmoscapes, but his strongest artwork this year graces the cover of Wormhole, or as I’m told the correct pronunciation is, WWWWOOOOOOORRRRRMMHHHOOOOOOOOLLLEEEEEE. What I especially like about this art is how much story it suggests. Either something that wasn’t human is in the midst of becoming gradually more so, or someone is shedding their humanity (as well as skin). Either way, it has something to do with the rhino beetle, and I can’t wait to find out what.
#4. Evile // The Unknown (artist: Eliran Kantor) — Few artists could make me include a cover that is like 75% black. Kantor can, though. The slim beam of light cast by a cracked cellar door is the only light for the father and son, surrounded by inky blackness. Kantor is an expert at expressive faces, and this pair ooze fear and despair. It’s an effective and haunting image that uses black as a tool to tell a story. If only the album were as great as the artwork.
#3. Slomatics // Strontium Fields (artist: Ryan Lesser) — I knew this had to be on the list the moment I saw it. I’ll even forgive the lack of album and band titles. The breathless figure reminiscent of the Statue of Liberty, her eyes beaming and her hair waving as if underwater, stands in stark contrast with the glistening embodiment of cosmic horror behind her. A clever trick that enhances that contrast, besides the clash in color, is the difference in shading. The flesh monster has been rendered in angry blotches, the statuesque woman in more marble-like tones. Don’t forget to check out the full-size art in the review!
#2. Harm’s Way // Common Suffering (artist: Corran Brownlee) — This stark, haunting piece makes it abundantly clear that “It’s Raining Men” is a horror scenario. The dreamlike surrealism and the apocalyptic climax clash into a nightmare depiction that took my breath the first time I saw it, and still fills me with an appropriate excess of dread when I look at it now. Rendering it entirely in black & white and cleverly constraining the cloud of people with a frame makes the scene feel both immense and claustrophobic.
#1. Deadly Carnage // Endless Blue (artist: Alexios Ciancio) — Though this list is ever a contentious one, I don’t think much protest will be levied at the winner this year. Graphic designer Alexios Ciancio is the vocalist and guitarist for Deadly Carnage, making this the rare treat of a band member designing their own album’s cover. Inspired by traditional Japanese art, Ciancio has created an absolute feast for the eyes. Though the portrait-oriented illustration leaves a lot of blank space on the sides, the dynamic composition that spills out the frame grants sumptuous life and vitality. The spectral nature of the cresting whale elevates the scene above the earthly and into the ethereal, which the music inside encapsulates. And whereas many artworks suffer from zooming in too much, the crisp lines and myriad beautiful details keep me scrolling endlessly across the canvas, from the swans flying out of the frame to the upended rowboats. A visual masterpiece.
#2023 #DeadlyCarnage #Eternity #Evile #FireDownBelow #GrantTheSun #HarmSWay #Hexvessel #Raider #SanguineGlacialis #SavageGrace #SecretRule #Slomatics #Varathron #Wormhole
-
I still remember my first day on my first job very vividly.
I had just complted a test task where I had to add tag functionality to an anti-anonymous image-board clone the company made (it was called rep dot ly, pretty badass domain name, sad that it folded), whereas the guys, Paul and Danko, implemented a webcam integration, so that people could add cute photos to imageboard-esque threads.
And so, my first day was at a conference where they were presenting the project. I remember being very ashamed that I went to another job interview after I went to theirs, and how interesting was everything in the conference hall. I felt a huge imposter syndrome, heh.
Then, when I started working it was kind of back and forth. Of course, I was slower than the other guys and less well-versed in industrial practices, but ultimately what got me into trouble is my back-then passion for overengineering and not being able to deterime when a design of a feature is good enough. I was with the guys till the very end of that iteration of very.lv though.
Afterwards I made an appearance in banking software, only to make a glorious, but short-lived return to very, where my desire for overengineering, augmented by banking experience, essentially got me fired, because I got too defensive about some program that I made to interact with postgresql, which wasn't doing the thing I was requested to do. But I'm very glad that my second stint with #verypositive gave me production experience with #erlang, that I managed to leverage by writing #foss. It eventually landed me my first well-paid job.
These days, very.lv is more or less a one-person show, but if you need some software, drop them a line, they're really cool.
-
Using older OSes and older programs to avoid slop
This started out as a draft around the start of this month, but when writing an "expanded" version of my Mastodon post I began to reiterate the same points so I said, fuck it, might as well just split my draft into two separate posts.
This is one of them. The other one will be up in a few moments… or hours? I don't know, heh.
Eternal Sloptember
I've been following the Open Slopware document per Drew DeVault's post on rsync. If you aren't aware of this, it keeps track of which FOSS programs have began to accept or even embrace AI-generated code.
I don't like that it's not just Vim, KeePassXC, and rsync, but also ImageMagick, VLC, mpv, Jellyfin, curl, Godot, Calibre, Gitea, GitLab, Bluesky, PeerTube, Mastodon, Lemmy, Lutris, etc.
tmux, plan9port, Heroic Games Launcher, LLVM, VirtualBox, maybe Nix.
The worst for me were whole operating systems accepting AI-generated commits, such as the Linux kernel, FreeBSD, GNU Hurd, ReactOS, and even FreeDOS (even programs for 80s/90s hardware isn't safe).
To explain why this is such a big deal, a lot of people (including me) are skeptical of AI, and want to avoid it however possible, but this makes it harder because it feels like it's being shoved down my throat. Use whatever analogy you want. I've considered low background steel, AI "veganism", even asbestos. But the biggest is that modern AI is a product of capitalism, pushed without ethical consideration by larger companies, and I want to avoid that shit.
Older operating systems
Okay, so my first proposal. I think the core system of every OS should be free of AI. I'm mostly referring to kernel and userspace applications, but I've also seen Lubuntu and Nobara, unfortunately, include AI-generated wallpapers, or projects like KOReader use AI-generated images for releases.
I've been looking into this a bit, and I think older operating systems are a good option, but some may disagree (I'll get into this near the end of this section), and much like internet privacy, it can be a compromise depending on how far back you wanna go. Maybe an OS predating the 2025 winter holidays when Claude Code exploded, November 2022 when ChatGPT was released, October 2021 when GitHub Copilot was first released, or May 2020 when GPT-3 was first published.
Fortunately, older versions of, say, Debian, have a "frozen in time" archive of packages for each older version used. This may also apply to derivatives like Devuan and Ubuntu, as well as Alpine, CentOS, Fedora, Slackware, FreeBSD, OpenBSD, and, with a bit of extra work (for finding the original sources?), NetBSD
But, unfortunately, it's often been claimed that running older software is a security risk waiting to happen.
On one hand, I agree, and one should always exercise caution when running old software (a tool like Lynis could be one in your security arsenal), and the older you go, the more screwed you are by possible RCEs.
On another hand, I also disagree. I personally believe most security issues are a result of PEBKAC and really involve how well the administrator knows their system. Arch Linux has a very lengthy page on security practices that apply to OSes. Others include Slackware and Gentoo. And for me, a big part of security is the attack surface, which is drastically reduced if you don't have 200 services running and stick to minimal software (imo modern web browsers are an overengineered security nightmare).
Older applications
Second of all, I can hoard older versions of software thanks to sites that still host them. Not all source code will compile, but there's a very high chance a Windows binary will be available that can run under WINE (though native performance is only expected on x86 architectures, where you'd have to use an emulator like qemu or box86 otherwise). If I'm unhappy about modern Anki, for instance, I can still run 2.0.52 if I really wanted to. If I'm unhappy about Blender, they too still provide older versions.
I've been able to do this as on as far back as my laptop, Omoikane (2004), running Slackware 13.37 (2011), after compiling WINE 2.14 (2017), though it relies on the program to be compiled without SSE2 due to the older CPU.
This also goes both ways! If I want new software, I can set up a container (Distrobox? uhh… Flatpak? shudders), chroot, virtual machine, or emulator. I've been thinking SSH forwarding could make the programs appear natively on the system.
#ai #slop #linux #debian #retrocomputing #rant #ramble -
Using older OSes and older programs to avoid slop
This started out as a draft around the start of this month, but when writing an "expanded" version of my Mastodon post I began to reiterate the same points so I said, fuck it, might as well just split my draft into two separate posts.
This is one of them. The other one will be up in a few moments… or hours? I don't know, heh.
Eternal Sloptember
I've been following the Open Slopware document per Drew DeVault's post on rsync. If you aren't aware of this, it keeps track of which FOSS programs have began to accept or even embrace AI-generated code.
I don't like that it's not just Vim, KeePassXC, and rsync, but also ImageMagick, VLC, mpv, Jellyfin, curl, Godot, Calibre, Gitea, GitLab, Bluesky, PeerTube, Mastodon, Lemmy, Lutris, etc.
tmux, plan9port, Heroic Games Launcher, LLVM, VirtualBox, maybe Nix.
The worst for me were whole operating systems accepting AI-generated commits, such as the Linux kernel, FreeBSD, GNU Hurd, ReactOS, and even FreeDOS (even programs for 80s/90s hardware isn't safe).
To explain why this is such a big deal, a lot of people (including me) are skeptical of AI, and want to avoid it however possible, but this makes it harder because it feels like it's being shoved down my throat. Use whatever analogy you want. I've considered low background steel, AI "veganism", even asbestos. But the biggest is that modern AI is a product of capitalism, pushed without ethical consideration by larger companies, and I want to avoid that shit.
Older operating systems
Okay, so my first proposal. I think the core system of every OS should be free of AI. I'm mostly referring to kernel and userspace applications, but I've also seen Lubuntu and Nobara, unfortunately, include AI-generated wallpapers, or projects like KOReader use AI-generated images for releases.
I've been looking into this a bit, and I think older operating systems are a good option, but some may disagree (I'll get into this near the end of this section), and much like internet privacy, it can be a compromise depending on how far back you wanna go. Maybe an OS predating the 2025 winter holidays when Claude Code exploded, November 2022 when ChatGPT was released, October 2021 when GitHub Copilot was first released, or May 2020 when GPT-3 was first published.
Fortunately, older versions of, say, Debian, have a "frozen in time" archive of packages for each older version used. This may also apply to derivatives like Devuan and Ubuntu, as well as Alpine, CentOS, Fedora, Slackware, FreeBSD, OpenBSD, and, with a bit of extra work (for finding the original sources?), NetBSD
But, unfortunately, it's often been claimed that running older software is a security risk waiting to happen.
On one hand, I agree, and one should always exercise caution when running old software (a tool like Lynis could be one in your security arsenal), and the older you go, the more screwed you are by possible RCEs.
On another hand, I also disagree. I personally believe most security issues are a result of PEBKAC and really involve how well the administrator knows their system. Arch Linux has a very lengthy page on security practices that apply to OSes. Others include Slackware and Gentoo. And for me, a big part of security is the attack surface, which is drastically reduced if you don't have 200 services running and stick to minimal software (imo modern web browsers are an overengineered security nightmare).
Older applications
Second of all, I can hoard older versions of software thanks to sites that still host them. Not all source code will compile, but there's a very high chance a Windows binary will be available that can run under WINE (though native performance is only expected on x86 architectures, where you'd have to use an emulator like qemu or box86 otherwise). If I'm unhappy about modern Anki, for instance, I can still run 2.0.52 if I really wanted to. If I'm unhappy about Blender, they too still provide older versions.
I've been able to do this as on as far back as my laptop, Omoikane (2004), running Slackware 13.37 (2011), after compiling WINE 2.14 (2017), though it relies on the program to be compiled without SSE2 due to the older CPU.
This also goes both ways! If I want new software, I can set up a container (Distrobox? uhh… Flatpak? shudders), chroot, virtual machine, or emulator. I've been thinking SSH forwarding could make the programs appear natively on the system.
#ai #slop #linux #debian #retrocomputing #rant #ramble -
Application 2025-02-032 Open Governance Body #OGB received
The following submission was recorded by NLnet. Thanks for your application, we look forward to learning more about your proposed project.
Contactname
hamish campbell
phone
email
[email protected]
organisation name
OMN
country
UK
consent
You may keep my data on recordProject
code
2025-02-032
project name
Open Governance Body #OGB
fund
Commons_Fund
requested amount
€ 50000
websitehttps://unite.openworlds.info/Open-Media-Network/openwebgovernancebodysynopsis
A project designed to create a trust-based, decentralized framework for governance within grassroots networks and communities. Rooted in the #4opens principles—open data, open source, open processes, and open standards—the #OGB seeks to mediate human-to-human collaboration by fostering trust, transparency, and simplicity (#KISS).
Its primary focus is addressing the #geekproblem by bridging technical and social flows, creating tools that empower people to organize effectively without falling into hierarchical or centralized traps. The #OGB builds on trust to sift through noise, allowing genuine contributions to rise, moving from complexity to simplicity and back to complexity organically.
The expected outcomes include:
Strengthened grassroots governance: Tools for decision-making and collaboration that are inclusive and scalable.
A thriving #openweb ecosystem: Platforms and networks that prioritize trust and social value over profit.
Mediation of mainstreaming and NGO influence: Keeping progressive activism focused on spiky, meaningful change rather than fluffy distractions.The #OGB aims to create sustainable digital commons that nurture resilience, diversity, and real-world impact.
experience
Yes, I’ve been involved in projects and communities aligned with the ethos and goals of the #OGB. My contributions span technical development, advocacy, and fostering open governance frameworks, all rooted in the principles of trust, transparency, and collaboration.
- Indymedia, I was an active contributor to the global Indymedia movement, which played a pivotal role in grassroots media and decentralized collaboration. My contributions focused on: Open publishing workflows to empower communities to share their stories. Advocating for the “trust at the edges” model to ensure decision-making remained grassroots-driven. Bridging technical and social challenges by helping develop and maintain tools that aligned with the movement’s values.
- OMN (Open Media Network), As one of the key proponents of the #OMN, I’ve worked to reboot grassroots media using trust-based networks and federated tools. My contributions include: Developing the concept of #4opens (open data, open source, open processes, open standards) to serve as a foundational framework. Advocating for federated tools like #ActivityPub and #RSS to enable media flows across decentralized networks. Organizing collaborative spaces to design tools that prioritize human-to-human trust rather than algorithms or centralized control.
- Fediverse Advocacy, Within the Fediverse, I’ve championed the importance of grassroots governance and resisting the co-option of these spaces by corporate or NGO interests. Contributions include: Participating in discussions to shape decentralized protocols like #ActivityPub. Pushing for #KISS (Keep It Simple, Stupid) principles to ensure accessibility and scalability. Highlighting the dangers of #mainstreaming and proposing strategies to mediate its impact on the #openweb.
- Open Governance Experiments, I’ve collaborated on smaller experimental governance projects aimed at exploring new ways of mediating human collaboration. For example: Designing trust-based moderation systems to reduce #geekproblem domination in decision-making processes. Implementing open-process methodologies to ensure transparency in workflows. Mediating conflicts between technical and social contributors, fostering productive collaboration.
Core Contributions Across Projects, across all these initiatives, my primary focus has been on bridging the technical and human aspects of governance. This involves: Developing frameworks that enable decentralized decision-making while maintaining trust. Advocating for simplicity to combat the paralysis caused by unnecessary complexity. Building alliances and mediating the challenges posed by #dotcons, #NGO dominance, and #geekproblem tendencies.
Through these efforts, I’ve gained insights into the challenges of building sustainable governance models in decentralized spaces, and the #OGB embodies the culmination of this work. It’s a step forward in creating robust, trust-based networks that empower communities to take control of their digital and social spaces.
usage
Budget Allocation for #OGB Project
The requested budget will be allocated strategically to ensure the project’s foundational development and long-term sustainability. An outline of key areas:
- Technical Development and Infrastructure (40%) Development of Core Tools: Funding will support developers to build the initial version of the #OGB code, focusing on simplicity, accessibility, and scalability. Server Infrastructure: Setting up and maintaining federated servers for testing, development, and early adoption. Integration with Existing Standards: Work to align with protocols like #ActivityPub, #Nostr and #RSS, ensuring seamless interoperability with the broader #openweb ecosystem.
- Community Building and Outreach (25%) Workshops and Training: Organizing sessions to train communities on the #OGB framework, focusing on trust-based governance and open-process workflows. Content Creation: Developing accessible documentation, tutorials, and guides to demystify the #OGB model for diverse audiences. Engagement Campaigns: Reaching out to grassroots organizations, activists, and communities to onboard early adopters.
- Research and Iterative Design (20%) User Feedback Loops: Conducting trials with early adopters to gather insights and refine the tools and processes. Governance Framework Refinement: Exploring different trust-based models to ensure inclusivity and adaptability to various contexts. Conflict Mediation Strategies: Testing and integrating mechanisms for conflict resolution and power balance within the #OGB framework.
- Administrative and Miscellaneous Costs (15%) Project Coordination: Funding part-time coordinators to manage timelines, resources, and community engagement. Operational Expenses: Covering software donations, events, domain hosting, and other minor but essential operational costs.
Past and Present Funding Sources. The #OGB project is currently unfunded in a formal sense, operating entirely through volunteer contributions. However, it is rooted in a history of collaborative efforts from related initiatives, which have benefited from in-kind support rather than direct funding.
Past Sources: #OMN and #Indymedia Communities: Provided foundational concepts and voluntary contributions of time, skills, and infrastructure. Fediverse and #Activertypub Advocates: Offered insights and testing environments for early experimentation with governance ideas.
challenges
Present Sources: Volunteer Contributions: Core contributors are donating their time and resources to push the project forward. Allied Projects: Informal support from related decentralized tech communities, sharing knowledge, feedback, and occasional resources.
Future Vision, while external funding is vital to accelerate the project’s development, we aim to maintain independence and adhere to the #4opens principles. By minimizing reliance on corporate or NGO funding, we ensure that the #OGB remains a grassroots-driven initiative. Our long-term goal is to establish a self-sustaining model through community contributions and shared ownership, embodying the trust-based governance the project seeks to promote.
Detailed budget breakdown can be attached if required.
comparison
The #OGB (Open Governance Body) project stands on the shoulders of both historical and contemporary efforts, drawing lessons from their successes and failures to craft a novel path to decentralized governance.
A comparative analysis: Historical Projects and Their Influence
Indymedia (Independent Media Centers) Overview: Indymedia was a global network of grassroots media collectives that emerged in the late 1990s to provide a platform for independent journalism. It embodied principles of openness, decentralization, and non-hierarchical governance. Comparison: Like Indymedia, #OGB aims to empower communities through open and decentralized structures. However, Indymedia struggled with governance conflicts and centralization of power in some regions. The #OGB addresses these issues through trust-based networks, conflict mediation mechanisms, and scalable governance tools. Key Takeaway: The #OGB builds on the ethos of Indymedia while implementing technological solutions to mitigate governance bottlenecks.
Occupy Movement’s General Assemblies. Overview: Occupy’s assemblies were experiments in direct democracy, emphasizing inclusivity and consensus-based decision-making. However, the lack of structured governance led to inefficiency and internal conflicts. Comparison: The #OGB shares Occupy’s commitment to participatory governance but incorporates trust-based models to build the decision-making. Instead of full consensus, the #OGB employs trust networks to delegate decisions while retaining accountability and inclusivity. Key Takeaway: The #OGB leverages structured trust-based governance to overcome the decision-making paralysis often seen in consensus-driven movements.
Contemporary Projects and Their Relationship to #OGB. Fediverse and #ActivityPub. Overview: The Fediverse is a decentralized network of federated platforms like Mastodon, powered by the ActivityPub protocol it is pushing user autonomy and grassroots control but has faced challenges around governance and moderation.
Comparison: The #OGB complements the Fediverse by providing governance structures for federated projects, addressing the ongoing issues of moderation and decision-making. The #OGB’s trust networks align with the decentralized ethos of the Fediverse, offering a scalable solution for community self-governance. Key Takeaway: The #OGB enhances the governance layer missing in many Fediverse projects, fostering resilience and collaboration across federated networks.NGO-Led Open Source Initiatives. Overview: Many open-source projects are managed by NGOs, which often prioritize stability and funding over grassroots participation. This has led to criticism of centralized decision-making and “corporate capture.” Comparison: The #OGB resists NGO-style top-down management, instead prioritizing the #4opens principles: open data, open source, open process, and open standards. Unlike NGO-driven projects, the #OGB is inherently community-first, ensuring power remains with the users and contributors. Key Takeaway: The #OGB rejects the NGO-centric model, emphasizing trust-based grassroots governance to avoid co-option by external actors.
Lessons from Historical Failures. CouchSurfing’s Decline. Overview: CouchSurfing transitioned from a grassroots volunteer-driven project to a for-profit company, alienating its core community and undermining trust. Comparison: The #OGB guards against such shifts by embedding trust and open governance at its core, ensuring the project remains community-owned and operated. Key Takeaway: Trust-based governance prevents mission drift and maintains alignment with the community’s original values.
P2P Projects and Overengineering. Overview: Many P2P initiatives have failed due to technical complexity and a lack of user-friendly interfaces, alienating non-technical users. Comparison: The #OGB adheres to the #KISS principle (Keep It Simple, Stupid), ensuring accessibility and ease of adoption without sacrificing functionality. Key Takeaway: Simplicity is essential for widespread adoption and long-term viability.
Key Differentiators of the #OGB Trust-Based Networks. Unlike purely consensus-driven or hierarchical models, the #OGB employs trust-based networks to enable efficient and inclusive decision-making at scale. The #4opens Framework. The #OGB is grounded in the #4opens principles, ensuring transparency, accountability, and openness across all aspects of the project. Focus on Digital Commons. The #OGB is designed to nurture digital commons, creating a space for grassroots innovation, collaboration, and governance that resists corporate capture. Composting the #TechShit, creating fertile ground for genuine social innovation.
Expected Outcomes. The #OGB aims to fill the governance gap left by historical and contemporary efforts, fostering a resilient, open, and trust-based framework for digital collaboration. By learning from the past and building on existing technologies, we seek to empower communities to reclaim the #openweb, bridging the gap between technology and grassroots activism.
The #OGB project faces significant challenges in implementing scalable trust-based governance systems. Key technical hurdles include:
Interoperability: Ensuring seamless integration with existing open protocols like #ActivityPub and the widening #openweb reboot.
Usability: Creating user-friendly interfaces to make complex governance processes accessible to non-technical people.
Resilience: Building systems resistant to malicious actors and spam within decentralized networks.Are a few issues.
ecosystem
The #OGB project is rooted in a diverse ecosystem of grassroots organizations, decentralized communities, and open-source initiatives.
Ecosystem Description
- Grassroots Communities: Activist groups, independent media collectives, and community-driven initiatives seeking alternatives to hierarchical decision-making.
- FOSS Developers: Open-source software developers invested in decentralized tools, such as #ActivityPub, #Mastodon, and related protocols.
- NGOs and Advocacy Groups: Organizations interested in participatory governance and transparency tools for improving their operations.
- Tech Enthusiasts: People exploring ethical and sustainable technology beyond the centralized #dotcons paradigm.
- Academic and Research Institutions: Scholars studying governance, social movements, and decentralized technologies.
Engagement Strategies
- Collaborative Development: Open, participatory development processes underpinned by the #4opens philosophy (open data, source, process, and standards).
- Workshops and Webinars: Educating target audiences about trust-based governance and the project’s tools.
- Partnerships: Building alliances with aligned organizations, including community networks and FOSS projects.
- Documentation and Guides: Creating accessible materials to help communities adopt #OGB principles and tools.
- Pilot Projects: Collaborating with grassroots organizations to implement and refine governance systems, ensuring practical impact.
Promotion of Outcomes
- Demonstration Projects: Showcasing successful case studies of #OGB governance in action.
- Fediverse Integration: Leveraging federated platforms for dissemination and collaboration.
- Open Events: Participating in conferences, hackathons, and public forums to share insights and foster adoption
GOVERNANCE-BODY_REV-March-2022.pdfOGB-dev.pnghttps://hamishcampbell.com/application-2025-02-032-open-governance-body-ogb/
#4opens #activertypub #activitypub #dotcons #geekproblem #indymedia #KISS #mainstreaming #Mastodon #NGO #NOSTR #OGB #OGBfundCommonsFundrequested #OMN #openweb #rss #techshit
-
CW: #overengineering ゆめ is too nervous about #elevator #safety #yume-en
I feel there should be a 'immediate stop' button in elevators which replaces the complex human logic of (1) check the indicator (2) press the floor(s) that is feasible for the elevator to stop at ASAP. (3) press the alarm when appropriate. Mayybe use a slightly more aggressive stopping profile as well?
The current manual logic is really hard to do under duress without wasting extra time and would be really useful in emergencies happening within the car (battery fire, heart attacks, violent crimes, etc where not everybody will be calm enough to take their eye off the situation and focus on stopping the elevator). -
Reinventing Technical Leadership for the AI Era
The evolution of technical leadership reflects the shift from traditional hierarchical models to more systematic, AI-augmented approaches. As productivity improves, leadership now focuses on designing efficient systems for fast decision-making and feedback. Successful leaders must prioritize clarity, autonomy, and leverage to thrive in this new landscape.https://atozofsoftwareengineering.blog/2026/03/31/reinventing-technical-leadership-for-the-ai-era/
-
@xerxesshouldnthavewon A couple of days ago, I was lurking on /r/UltrawideMasterRace (salivating over some of those 32:9 monitors) and I saw a post with a #DigitalBlasphemy wallpaper.
That was some real nostalgia from... about a decade ago? I can’t even keep track anymore, to be honest.
-
@sirber “Hey drama addict, do you ever get tired of living your life through Twitter feuds? Maybe it's time to step away from the screen and start focusing on real-world problems. Just a thought. #GetALife #TwitterObsessed”
There! I asked ChatGPT to write a confrontational tweet directed to you and cause some drama about you missing Twitter drama.
You’re welcome.
-
@laurenthemself OMG, I can relate sooo much. I’m collecting stickers (and never use them) since 2006-ish. I finally pulled the trigger this July and used my stickers on my laptop. Felt so liberating. #UseYourStickers