@bender@twtxt.net Nah feeling pretty rubbish today actually 😢
@prologic@twtxt.net woah, such a good life! 🙈
@marcorocco@roccodrom.de What are you updating and changing out in your bathroom? 🤔 We probably need to update our bathroom too, the spa pipes are getting a bit uggh 😅
@aelaraji@aelaraji.com I just woke up fianally 🤣 It’s 12:45pm here (midday)
@aelaraji@aelaraji.com here as in, here? It’s a quarter to 22:00 here, and after a rather tiresome day I am trying to rest, while alternating with folding freshly washed and dried clothes. Quiet indeed! 😅
It’s kinda quiet in here today!
renovating the bathroom on the upper floor
@bender@twtxt.net Haha I know and @lyse@lyse.isobeef.org is awesome🤣
To expand on this, Lyse is the only person I know to send in code contributions with a full test suite. That’s awesome.
Looks like there’s not a lot of fancy magical stuff:
- https://komh.github.io/os2books/progfaq/112_L2_Whatisthebestwaytoco.html
- https://komh.github.io/os2books/progfaq/111_L2_Whatisthebestwaytoco.html
There is, however, a DosKillThread()
function, which, as far as I know, does not exist on POSIX. 🤔 You can only send a signal to a POSIX thread and then it’ll hopefully end some day, right?
Killing threads is probably a bad idea, though. Who knows which state it’ll leave behind. It’s not like a process which will be properly cleaned up by the OS.
I think I’ll leave it as is. 🙂
-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.
@prologic@twtxt.net isn’t it evident? It surprises me you need to ask! 😂
@dfaria@twtxt.net plunk.
@dfaria@twtxt.net you are not who you say you are, you are who you show to be. You demonstrated a certain lack of levelled engagement, and sound reasoning; you were borderline hysterical. All qualities everyone should have, even more so someone who has chosen the teaching path.
This is not a train terminal. No need to give so many warnings about leaving, so many “bye-byes”. If that’s your intention, just leave.
@dfaria@twtxt.net Appreciate this 👌 Right now the algorithm is quite dumb – and I’d also hate to develop any algorithm that abuses any data from users. So definately needs to be things like:
- one post per day per domain
- or latest post per domain
etc/./
@sorenpeter@darch.dk Yup! Some good simple ideas there 👌
@sorenpeter@darch.dk Thanks for your positivity and support ! 🤗 This is exaxrly spot on, however I also realize getting things “right” is actually quite hard 😅
-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.
@lyse@lyse.isobeef.org How much emphasis do you place on test coverage?
To be fair cleaning up “noise” is quite hard to do. Obciously all the 1-way Mastodon feeds were easy because there’s just no way to interact with them!
@dfaria@twtxt.net That’s fair. Also removed the block on your domain btw.
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. ;-)
@bender@twtxt.net You don’t know me and you’re already making arbitrary judgments about me. I only got upset because they didn’t warn me that they were going to block my domain. Nobody likes being canceled without warning. There were other civilized ways of letting me know that there was a problem with my domain instead of blocking it unilaterally. Bye-bye!
@bender@twtxt.net I guess all I can do is unblock the domain and sit down and rethink the “Discover” view’s design and behavior? hmmm 🧐 Alternatively, build a new yarnd
2.0? as a single-user pod only?
@bender@twtxt.net Yeah I could get behind that. Define minimalistic though? What features (if any) would we drop? Would it be mobile-first or desktop-first?
@bender@twtxt.net I couldn’t agree more 🤣
@bender@twtxt.net I never see problems on my end, so I suspect this has to be Cloudflare doing this occasionally. I’ll have to poke around there again. At least I have a close enough timestamp :D Maybe message me your IP and approximate timestamp?