Impressive how certain projects just vanishes from day to nigh in the crypto world. Linxdot was a miner that simply stopped working. Not that it was giving any meaningfull reward, but hey! Why just dying from nothing?

I thought it was a Wifi issue and then after a very long time I entered the discord server of Linxdot. What a mess! Completely abandoned and I wonder why they still sell these devices, they don’t even work anymore.

Anyway, I had this paper weight laying around and I needed to ressurect it. I then saw I guy talking about the Crankk.io project and it seemed it can not only mine Helium but also do some other mining activities.

But…. I needed to flash this piece of plastic and here we are after weeks researching (cause all tutorial were for Windows).

I come from a background in Ruby on Rails and there things are extremely simple, or at least I find them quite simple.

I decided then to start a new pet project using NextJS, I am obviously quite lost. So I am doing little by little, step by step, rediscovering things in a completely different environment.

Today I wanted to make a simple task: seed my DB.

Recently while doing some migration from objective-c to swift and I found a line of code that seemed to me that it should crash, and yet, it didn’t crash on production. It was an objective-c code bridged to swift as an implicit unwrapped (!). So here is the snippet, more or less:

// The bridged generated interface from the objective-c
class BridgedClass {
    var importantNote: String! // contains a nil value
}

// ... then I had a function:

func doSomething(importantNote: String?) {
    print(note)
}

// ... and it was called

doSomething(importantNote: myBridgedInstance.importantNote) // Should it crash?

Today I stumbled upon having to know if a specific commit was present or not in the release branch. I of course checked stackoverflow, i didn’t have it right in my mind.

VERSION=2.4
COMMIT_HASH=123acaef123acaed
git log origin/release/$(VERSION) | grep $(COMMIT_HASH) | wc -l

1. git log - that’s I assume it is ok, just checking the origin branch
2. grep - also I think that’s ok, just finding the commit hash from the git log list
3. wc -l - stands for word count and is a command-line utility that counts the number of lines, words, characters, and bytes in a file. and -l flag tells wc to count only the number of lines.

and there you go! You have effortlessly checked if your commit was present in a specific remote branch

These days I was working on making the iOS application complaint to the new EU regulations for accessibility. With a proper auditory of the app, it is rather easy to implement a better accessibility.

However I must say, until this momentm I did not find ANY testing framework that actually covers accessibility as it is required by law.

We have AccessibilitySnapshot that is very limited, we also have ViewInspector which you can try to guarantee certain attributes. But I couldn’t find a framework that would tell me: hey you are not doing it right, group these elements, this and that should have a different accessibilityTrait etc. (In fact there is one, but I am not mentioning because it relies on ui-test and on top of that it did not find any really useful issue).