lyse @lyse.isobeef.org

Follow

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@lyse does not follow you (they may not see your replies!)

Recent Twts

Recent twts from lyse

(#c2afqsq) @movq@www.uninformativ.de Yeah, I don’t get it either. Some “security” scanner at work also complains about “dead” libraries all the time, just because the most recent commit is a few years or even just months old. What a giant joke.

This mindset might come from today’s kids who can build stuff only with gazillions of dependencies. And plenty of these suck, are full of bugs, vulnerabilities and bad code in general. So they have to be patched constantly. If one is always surrounded by that, it just feels normal. One might even come to the conclusion that it simply has to naturally be that way. And then, the incorrect deduction is that the project is abandoned, once there are no new commits in a week. It maybe doesn’t occur to these people that it is actually possible to work out differently.

To be fair, there is also a lot of unfinished and truly dead code out there. So that assures their theory even further, once they stumble across one of those projects.

And the same doesn’t only happen to private projects. All enterprise software systems also pull in so much stuff, that there is always something to update.

The lack of proper planning, just building and delivering buggy banana software in cycles and the mindset of shipping fast and often and doing things agile in general does not do this any favor. It just feels like today’s sofware is never ever finished. And if it finally reaches such a point, it must be dead.

I know of some otherwise reeeeaaaaally great software developers who also think that way. I don’t understand why they disagree with us here. :-?


#d2lmxdq

(#bl7a36a) @movq@www.uninformativ.de Why would that be surprising? :-) They definitely fit my style of music. Well, I don’t wanna know how much a ticket is. And the Wasen is also a terrible location. :-D

The overcrowded train was run by GoAhead, the S-Bahn by DB. They’re interchangeably bad.

Over fifty kilometers is a very long bike ride. That at least doubles my commute to more than six hours in total. No, thanks. ;-)


#jjk7zla

(#c2afqsq) @movq@www.uninformativ.de @prologic@twtxt.net Good analysis! Another aspect is: Trying out new stuff is appealing to a lot of people. I’m certainly not unguilty of that either. But when you experiment, things will naturally go wrong somewhere at some point. You probably don’t even know that at this point in time and realize this only much later. If at all.

To make it better, throwing things away and starting over with the newly aquired knowledge would be the right thing to do. But that doesn’t happen for a myriad of reasons. So you ended up with overly complex stuff.

A bit like building a prototype and keeping it alive forever. “Denn nichts hält länger als ein Provisorium.” – “Nothing is more definitive than the temporary.”

Then there comes in feature creep. And preliminary optim^Wfeatures, “hey, maybe somebody would like to bla in the future, let’s add this”.


#lmywqfq

I just heard AC/DC play live in Stuttgart-Bad Cannstatt for the first time in my life!

Well, when I was waiting for my train home on the station platform. I didn’t recognize that it was Acca Dacca, and I tried hard. In fact, the stage was 500 meters away, so it was just some music-like sound that found its way into my ears. Still kinda cool to know that I heard them live.

I had a barbie with my old workmates. That’s why I have a story to tell now. On the way there, the train was hopelessly overcrowded with AC/DC fans. You couldn’t fall down, simply impossible. It was like in the videos of Japanese subways, where guards press in passengers to utilize every square centimeter. At later stations, plenty of people didn’t get in. Not a chance. This caused quite some delays. And boy, was it hot in there. Streams of sweat running down everywhere.

Originally, I wanted to meet up with a workmate in a city train for the second part of the trip. Due to a signal failure, his train was delayed, though. It got delayed even more and more and was finally cancelled altogether. I eventually got my connecting train while he was still stuck and decided to abort mission and go home after 40 minutes. Catching my connection was another adventure. It was rerouted to another platform, of course without announcement. Because why would you? Fuck the passengers! Luckily, I noticed that it took a different branch at the switch on arrival and ran down and up the stairs to the other platform. The delay counter in this train showed 40 minutes when I finally got off.

With the exception of Acca Dacca, the way home was pleasantly uneventful. Just a few minutes delay and a relatively low passenger volume.

I’m so grateful for not having to experience all this shit on a daily basis anymore. Not looking forward to the next time I have to go into the city. Not at all.


#bl7a36a

(#smnew7a) @movq@www.uninformativ.de Oh dear, people who have to always get an answer immediately have all sorts of issues. :-( They’re dead losses.

I will not use WhatsApp in a million years. It’s not worth it. Might be trickier with family members, but I also refuse to use such stuff. It definitely degrades some friends to aquaintances, but oh well. If I don’t know what I’m “missing out” on, then I simply cannot miss it. On the positive side, it frees my time for other things. :-)


#pla4ifa

(#5e6d54a) @movq@www.uninformativ.de Yeah, my software is definitely completely irrelevant to everyone else.

I don’t send my bank or insurance company any bug report e-mails or the like. I’m talking about mailing software developers or projects. On a side note, though, I’ve seen lot of (German) companies use GMail & other terrible mail providers. My former employer fell also in this category (so does my current one, but at least I receive all e-mails).


#mwqjf6q

(#q4hmq2q) @prologic@twtxt.net Haha, we’re already in summer. :-)

@movq@www.uninformativ.de No, both are a manmade lakes and ponds, but the fish are real. :-) In fact, the fish are in the much smaller “tadpole pond” as I call it. The tadpoles are now all gone and we’ve seen tiiiiiny frogs jumping around. But we were not successful in capturing them on film. Maybe fish were brought in these artificial lakes by mankind, too, I don’t know. Good question.


#xeyzn4a

(#5e6d54a) @movq@www.uninformativ.de @prologic@twtxt.net Maybe your softwares are just perfect and there are simply no bug reports and contributions required. :-)

I reckon if someone really wanted to participate, they will. Despite where it is hosted.

I just also see the issue with smaller mail servers being blocked by the large ones. This also happened to me I believe. My mails just never made it to the people. Or they were ignored, I cannot tell.


#6hkl3fa

The 26°C humidity was through the roof and we just barely escaped the thunderstorm on our stroll. Only the adjacent rain hit us hard. Black clouds caught up on us and we decided to take cover at a barn. Not even a minute later it started to rain cats and dogs for ten minutes straight. Holy crap, that was cool to watch. :-) Also, the smell of rain was just beautiful.

We then decided to continue our return in the light drizzle. But it then got much heavier again and we got completely soaked. With the wet t-shirt and the wind it actually felt rather cold. I anticipated to get rained on, so I left my camera at home. Plenty of paths turned into brook landscapes, several centimeter deep creeks ran down the hilly trails. Quite fascinating. :-)

The sunset a few minutes ago wasn’t too bad:


#4nlm4ca

Oh, this is interesting! Reading the Crafting Interpreters book, I came across a table of exit codes in FreeBSD.

I didn’t know that a command line usage error is supposed to report exit code 64. In the past I either simply exited with 1 or sometimes each exit statement got its own dedicated number. The latter came in useful for debugging shell scripts. I exactly knew which branch was executed. That was handy when the error messages were similar or even the same.

I was always wondering if there is some kind of a standard, but I never did my reasearch. Looking at other people’s code, it always seemed to me that everybody just did wantever they wanted to in regards to exit codes. I just looked up what else is out there and systemd also defines heaps of errors. It even references the FreeBSD one and links to the Linux Standard Base specification, too. Cool, cool!

Do you guys know of these conventions and make use of them?


#kzjdhia