Tests? Pfffft. I am the test.
And while I’m here: https://blog.jim-nielsen.com/2024/sanding-ui/
Tests? Pfffft. I am the test.
And while I’m here: https://blog.jim-nielsen.com/2024/sanding-ui/
Right now we have no other solutions/fixes. You may be able to get Invidious working on residential IP addresses (like at home) but on datacenter IP addresses Invidious won’t work anymore.
This might explain why mine has been reliable even though it hasn’t been updated in months. I guess add me to the list of confirmations that it works on residential connections.
Good question, I’m actually not 100% sure! This seems point to ‘no’ since its the same base spell:
https://www.dndbeyond.com/sources/dnd/basic-rules-2014/spellcasting#CombiningMagicalEffects
The answer has got to be helix
;)
Forking is indeed the way forward when Mozilla loses its way a little more. For myself, I switched to Librewolf about 6 months ago, along with replacing Thunderbird with Betterbird after using it since the Phoenix days.
I cannot remember what prompted the move to Librewolf, it may have been the AI stuff they were pushing at the time, or possibly the update that forced the tabs into my titlebar without having to go into about:config to fix it. Or the fact that Firefox was constantly pushing me to sign up for an account. There were quite a few gripes that added up over time lol
Betterbird restored some removed things I liked pre-supernova as well as a native systray icon under Linux and that was enough motivation to make the switch.
It is time for a new browser to enter the market. Either Ladybird or something built with Servo seems likely.
I’ve got some bad news for you. Mozilla bought an ad company.
Apple confirmed that the Epic Games Store for iOS in the EU compiled with most of its guidelines, but it had an issue with the “a download button and related copy”.
Apparently, Apple felt that the download button and related copy might mislead users into thinking they were made by the iPhone maker. While Apple has approved the app, it wants Epic to make the changes before the next app review.
There’s the catch. Emphasis is from the original article.
I’m one of those creatures that flattens out fizzy drinks before drinking xD
Air-up water bottles. When I bought mine it claimed to be a better water bottle all-around.
Its primary gimmick of tricking the brain into tasting the scent works well, I did drink a lot more water without needing actual flavouring. The fact that I could (unofficially) 3D print my own reusable flavouring pods to be a little more eco-friendly was a nice surprise and the reason I decided to try it.
The “better bottle” part is utter horse crap. It leaks when tipped over, even when tightly closed. Their marketing team went as far as adding “sip, don’t tip” to the instructions instead of making the cap properly seal.
Drinking from it was a chore as there was no water pressure and the constant bubbling (lets be real, its more like wet fart) noises made it impossible to use in silent settings.
I ended up going back to reusing a disposable bottle until it leaks even though the thought and feeling of something flavourless being in my mouth is revolting (its a sensory thing).
I think about a feature or bugfix that I want to work on, then shoehorn it in by any means necessary. Once my code is confirmed working, the planning phase begins and I go through the module(s) I’m working with line-by-line and match the original author’s coding style and usually by that point I pick up a trail or discover a bunch of helper functions/libraries that I can use to replace parts of my code, and continue from there.
As others have said, configuration files is a great way to learn that. Pick a config option you want to learn about, jump to the config loader, find where the variable gets set, then do a global search for that function. From there it starts to fall into place.
Sidenote: I also learned rust this way. It took me around 6 months to learn the rgit codebase solely from adding features that I wanted from cgit. Now I’m at the point where rebasing from upstream to my soft-fork doesn’t mess up any of my changes, and am able add or fix things with relative ease. If memory serves, a proper debugger (firedbg is excellent!) was used on several occasions to track down an extremely annoying and ambiguous error message that was due to rust’s trait system being a pain in my ass.
Tried swiping on the blocked community in the settings? I got it to show up that way.
Definitely! Voyager has been wonderful when it comes to filtering and my filter/block list is massive. I do have the issue where the Lemmy timelines get stale quickly and All is a ghost town but its worth it to see mostly positive things. The desktop experience is atrocious.
On the microblog side, moving to an instance running Sharkey was the best thing to do as Sharkey has the feature to hide the CWs entirely.
From my experience, CW only works if the post is completely hidden from the feed without the option to view it.
Blahaj Zone had the option to yeet that shit from the timeline entirely and it worked amazingly until a migration fucked that up leaving it broken for months and my mental health dropped off a cliff because holy fuck did I not realise most of the people I followed posted so much depressing shit that triggered my cptsd. The urge to click the button was too strong.
Its par for the Fediverse course, really. Good ideas and half-assed implementations.
I use a combination of PiHole via a VPN to my home server and Orion browser.
Its greatly improved my experience.
The Talos Principle video was interesting to watch, thanks for the link! It shined a little bit of light on automated testing.
Theres also someone on YouTube who has been teaching an AI on how to walk and solve puzzles on its own, the channel name escapes me and I’m nowhere near a working computer to look it up at the moment :(
I’m sure you could end up writing a test that’s bad in just the right way to end up doing more harm than good, but I do think that’s the exception(heh).
That’s exactly why I’ve asked. That is where I’ve gone wrong with TDD in the past, especially where any sort of math is involved due to being absolutely horrible at it (and I do game dev these days!). I can problem solve and write the code, I just can’t manually proof the math without external help and have spent countless hours looking for where my issue was due to being 100% certain that the formula or algorithm was correct >.<
Nowadays anytime numbers are involved I write the tests after doing manual tests multiple times and getting the expected response, and/or having an LLM check the work and make suggestions. That in itself introduces more issues sometimes since that can also be wrong. Probably should have paid attention in school all those years ago lol
Doesn’t this rely purely on the fact that the test is right?
Tbh I’m not a web person (more of a backend person) and don’t know the recommended practices.
display: grid;
is a good friend of mine xD