lyse @lyse.isobeef.org
 (3w ago)

Executing all tests of the online registrations I’m building for the scouts takes now 70 seconds. Initializing a new SQLite database in RAM and creating all the tables for each test case sums up and takes its time. During development cycles I more often resort to the -run flag for go test to specify only one area of tests to be executed. Much more fun this way to quickly go back to writing code.

At least the service layer line coverage is a whopping 99.5%, branch coverage is 93.3% (the latter could still be bumped slightly). However, only 17.6% lines of the web layer are covered (I definitely should increase this by a lot). This still good test base, if I say so myself, came in extremely handy a lot of times when refactoring stuff. Esp. the service layer changed, web not so much. It slows development down quite a lot, that’s for sure. I reckon it’s easily five to ten times more effort to come up with useful tests than writing productive code, probably even more. I’m bad at guessing. But the confidence of not breaking stuff is sooo much more valuable. The tests certainly paid off in the past, zero doubt about that.

It takes a lot of discipline to first write all the tests in the service layer before doing the web stuff and finally see it in action and play around. It’s funny that I always have to force myself to do so, but in the end, I’m always happy to have done it exactly like that. It once again worked out very smoothely that way. But something inside me wants to fast forward. I wonder if that irrational part eventually fades away.

Having a code coverage report does make a night a day difference. It actually turns writing tests into a fun game for me. The older I get, the more I do enjoy writing tests. Rest assured, producing productive code is still cooler. :-)

I’m also sooo happy about vim-go. I can’t believe how much that sped up and boosted my development process.

Whoops, 57 minutes later, this message turned out much more elaborated that I initially envisioned. Oh well. ;-)

#p4xbjgq
lyse @lyse.isobeef.org
 (3w ago)

(#d5n4myq) @movq@www.uninformativ.de I can’t think of a single one. Pretty lucky so far.

@bender@twtxt.net Holy cow, congrats on that title. I do have plugged in the more important equipment in a power strip with surge protection. The weird thing was, that only one of the monitors went black for a second. The other one (both are behind surge protection) remained operational the entire time. Maybe EMP? It was closer to the window than the other one.

#elsakca
lyse @lyse.isobeef.org
 (3w ago)

(#aiqtdda) @movq@www.uninformativ.de Such piece of shit software makes me want to quit. Esp. if it is just for useless compliance garbage that never helped anybody accomplishing any real improvement. Is it from IBM? We once had to build a threat model with some terrible generator and my goodness, you can’t believe what a myriad of hopelessly useless, wrong entries it produced. Thousands of thousands of lines. At least it was markdown. We basically removed like 99% of its output after reading through every single item. Did this once and refused to touch it ever since. All hand-written now and actually helpful.

#uvvodeq
lyse @lyse.isobeef.org
 (3w ago)

(#qf7pavq) Jaja, @movq@www.uninformativ.de, immer schön aufmerksam der guten Steckdosenpräsi folgen und im Anschluss in der Exzellenztabelle was eintragen und ausrechnen lassen! :-D Klingt alles recht albern. Ich schätz aber mal, dass einem das gar nicht mehr auffällt.

@bender@twtxt.net Fenster 11 → Windows 11; KraftPunkt (or Steckdose) → PowerPoint; Deppendrehkreuz (awesome translation btw, I had to laugh hard!) → GitHub.

#pxuqk4a
test@aelaraji @aelaraji.com
 (4w ago)

And this one with a GUI text editor xed just in case… lorem lipsum and stuff. it looks like this one didn’t get affected at all! Hmmmm… Maybe the environment variable is called VISUAL for a reason? 🤨 207 characters and counting…

#foz26rq
@marado@ciberlandia.pt @ciberlandia.pt
 (1y ago)

Oh, there is a chance, of course there is a way. Sort of.

Mind you, you will need to choose one of those options: either pay with money or with personal data. And no, choosing to “pay with personal data” isn’t the same as “staying with what you already had”*. But at least you don’t need to accept the new ToS’s if you don’t want to - now I actually went there to read them and compare/check what changes, and there there’s this:

“The updates go into effect on January 12, 2024”

So, until the 12th, you can choose one of those options, backup your data and delete your account, without having to actually accept those terms.

On the other hand, you will accept them by default - if I was on vacations or hadn’t tried to go to facebook until the 12th, I would have accepted it by default, apparently. Of course, I falled into that trap on my own, when I accepted their ToS in the first place, that say that they can change it at any time and you’ve automatically accepted it. I knew back then I shouldn’t have**, but… here we are.

#rjebz2q
@marado@ciberlandia.pt @ciberlandia.pt
 (1y ago)

I was feeling bullied, then I found my data is hostage. What next?

Well, the only remaining option is to just delete the account. Right?

Well… wrong. Because, you know, that’s also on those menus you will only have access to if you first accept the terms of service you don’t want to accept. :picardfacepalm:

#xzqpmsq
@marado@ciberlandia.pt @ciberlandia.pt
 (1y ago)

You can, of course, not accept these changes, and decide to leave Facebook. There’s no time for you to go in and say goodbye, but at least you can download your data before you go.

How? I’m glad you asked. You can do it from two different menus. But… you can’t really access any menus without choosing one of those options (thus first accepting the new terms of service). WTF?

#jw4i64q
@marado@ciberlandia.pt @ciberlandia.pt
 (1y ago)

Espantando ninguém:

Marcelo diz que nova versĂŁo da lei de metadados continua inconstitucional*.

O que tem mais “piada” é que os partidos que aprovaram esta treta já sabiam que não cumpre, que isto ia ao TC… E estão interessados nisso, porque têm a esperança que seja o Constitucional a dar-lhes “pistas” sobre como legislar sobre a matéria**.

Foram os trĂŞs partidos mais votados em Portugal!, e vai-se a ver e como legisladores valem zero.

** https://www.publico.pt/2023/10/14/politica/noticia/parlamento-espera-constitucional-pistas-solucao-metadados-2066712

#sm64z4q
@marado@ciberlandia.pt @ciberlandia.pt
 (1y ago)

“Sam Altman disse recentemente ser mais fácil fazer as pessoas agir se as confrontarmos com uma ameaça existencial. Se este paradoxo recorda as palavras de Mark Fisher/Frederic Jameson — “É mais fácil imaginar o fim do mundo do que o fim do capitalismo” —, a apropriação mais adequada seria qualquer coisa como: é mais fácil imaginar o fim do mundo do que admitir as falhas da I.A. corporativa. As mesmas pessoas que anunciam o apocalipse descrevem os modelos como ferramentas de propósito geral, capazes de desempenhar qualquer tarefa, e selam contratos para o uso desta tecnologia (por exemplo com o Estado português) num ambiente ainda vazio de regulação. E de compreensão.”

https://setentaequatro.pt/ensaio/ferramentas-mudam-mas-lutas-continuam-inteligencia-artificial-e-o-que-quer-dizer-para-o-teu

#rwrrjxq
@marado@ciberlandia.pt @ciberlandia.pt
 (1y ago)

“the European Union (EU) proposed an amendment to the Electronic Identification, Authentication and Trust Services (eIDAS) Regulation that would change provisions related to Qualified Website Authentication Certificates (QWACs). The proposal could empower governments to compel browsers to validate specific Certificate Authorities (CAs) that may or may not comply with industry best practices for ensuring security online”

https://www.internetsociety.org/resources/doc/2021/internet-impact-brief-mandated-browser-root-certificates-in-the-eu-eidas-regulation/

#5mikurq