Scratched minor, the flash key – ordered from Ali Express – is intact literally. Moreover, it’s working as usually, flash memory scale. It’s too lazy mood to take pictures over the smartphone and upload them then to Dropbox, then later download them and re-post it there to prove this incident. But you can visit me at home and get convinced yourselves, anyway, it’s not a criminal offense by the status quo and consensus of the so called household (Keynes); it’s unambiguous sophistication of home office and its prerequisites.
Anyway, the agreement between house owner and its inhabitants like tenants, is to be reaching its limits – a. k. a. office scale System D spying evidence. Why on earth such a famous inits system should drag supernatural load on the laptop like squashfs and snapd – snapd.socket? It’s ambiguous, unresolved. For example, yesterday, I was performing the test online with git repository on my desk and the snapd Spotify was playing in the background with regular earphones plugged in; nothing spectacular, but one of the prerequisite stage requirements was phing testing material – like stack. It required tremendous amount of PHP mostly dependencies to be installed (package and language) and bugged my laptop into lagging state; though an equal or so contributor (notorious I mean) was at the same time – simultaneously – SystemD launched Snap Store hosted Spotify playing music streaming service.
So, it downgraded all the developing – developer – experience to non auto-completing VS Code, which rendered the 2 perk test tasks (Estonian gov project) unusable, it means the process was unveiled so that subsequent commits were debugging stage, not developer nor prod mode to the contractors. In essence, it sounds ridiculous, calling for organizational learning application on the runtime, like
systemctl disable --now snapd snapd.socket
And later on removing the latter altogether, because the SSD pollution isn’t the demanded thing on site; nor its upgrade procedures genup stage.