Lupa provides constant basic statistics about the Gemini network. Stats like how many servers are online, number of virtual hosts, TLS distribution, and so on. It’s a really nice project. It got me asking.. what kinds of information can I extract from TLGS’ index? Furthermore, I want to provide some more information for Gemini users. Helping us to understand the network we love. It also helps me to build a better search engine.

Amid the current crypto price drop, I want to write about what cryptocurrency is actually useful for. And what I believe crypto should be used for. Non of those NFT and ICO bulls*it. Or you can think this as my DD for investing in crypto. Or confirming my confirmation bias if you read WSB. At the very core of the cryptocurrency is the idea of trust and decentralization. Our current banking system depends a whole lot on trust.

I was put in charge of improving the quality of an application in a certain project, so I decided to use indicators to quantitatively express the quality of the software. This is because various indicators are sometimes used to prove the quality, especially in projects that have been ordered by customers. Number of tests Number of reviews Test density (= number of tests / number of lines of code Bug density (= number of bugs found / number of tests) Code coverage Number of lint warnings … are commonly used indicators of software quality.

I do not step shyly back from your stack, but look upon it always as my stack, in which I respect nothing. Where did we go wrong? Accidentally discovering and rediscovering the joy of computing, and ending up with what we have, instead? All tech stacks and standards are spooks in the spookiest sense of the word, and any grand idea of what a computer aught to be is inseparable from the ramblings of a god-fearing human, or an appeal to societal norm, or the allure of the athiest god in scientus

Me and my friends often talk about software design. They’re skeptic about Agile Software Design, calling it “software design by trial and error”. I share their criticism. Yesterday I took a two-hour LinkedIn Learning class on Agile Software Design. It was an introduction only. My first impression is that Agile is, at one level, moving a to-do list of sticky notes around on a bulletin board, assigning programming tasks to the programming team with verbal instructions and discussion about how to program something.

So at work we were talking about interviewer questions for graduates, and one of them was the standard simple test to weed out graduates who faked it till they made it. it went something like this: You are given a list of characters, please return the list with commas seperating each element. do not leave a trailing comma. There may have been language restrictions or something, honestly I wasn’t paying a huge amount of attention, but it got me thinking about my honest answer to that, and here is what I came up with.