Also to answer your original questions, you mostly have to exercise in recognising situations where certain design patterns would be appropriate to use.
For certain application types though (games, design apps, data analysis apps, etc.), there are already popular design patterns that exist and are used all the time. Look at how other applications use them.
I'm admittedly not sure if I get what you want to do with the crafting bills.
But if you mean that the reservations, delivery requests and resource checking are modular for each bill, you can make a generic bill that takes in a class of type reservation, delivery request and any other bill class attribute you want to be modular.
That way, you might not need to check for specific cases for each combinations.
I was about to say that. Biological-female and biological-male is a form of misgendering that is far too common and an innacurate way of describing someone's sex or gender.
I don't really know if I was blocked nor do I really care. I'm just explaning why people were upset/making memes about it. It's shocking once one finds out about the blocklist, but kind of funny in retrospect.
Well yeah, people are changing frontends and warned others that Tesseract has that kind of blocklist and they don't support it. If people that used the tool didn't find out until now, it's mostly a communication issue from the dev. And to the user that knows none the wiser, opinions that they would've accessed if not for using Tesseract are essentialy not available. The option to turn it off is essentially hidden, and the user can't find out that information is being blocked (as seen by the reaction it caused in the threadiverse). It's censorship by omission of information. Even if they had good intentions, the way they went about it failed to communicate what the blocklist was about, and that information was being blocked in the first place.
It's also just kind of a silly thing to implement in a client. That's the perspective the memes are coming from. Usually, blocklists should be left to the instance administrators or users. The client should only easily allow such a list to be available.
Also to answer your original questions, you mostly have to exercise in recognising situations where certain design patterns would be appropriate to use.
For certain application types though (games, design apps, data analysis apps, etc.), there are already popular design patterns that exist and are used all the time. Look at how other applications use them.
I'm admittedly not sure if I get what you want to do with the crafting bills.
But if you mean that the reservations, delivery requests and resource checking are modular for each bill, you can make a generic bill that takes in a class of type reservation, delivery request and any other bill class attribute you want to be modular.
That way, you might not need to check for specific cases for each combinations.
Never meant to imply that it was malicious, just that it's common and should be pointed out more often.
I was about to say that. Biological-female and biological-male is a form of misgendering that is far too common and an innacurate way of describing someone's sex or gender.
En tout cas, ton nom te va bien lol
This is amazing! ❤️
It is quite naive to think that nobody has thought of a sollution like that though. It was probably not implemented like that for a reason.
I don't really know if I was blocked nor do I really care. I'm just explaning why people were upset/making memes about it. It's shocking once one finds out about the blocklist, but kind of funny in retrospect.
Well yeah, people are changing frontends and warned others that Tesseract has that kind of blocklist and they don't support it. If people that used the tool didn't find out until now, it's mostly a communication issue from the dev. And to the user that knows none the wiser, opinions that they would've accessed if not for using Tesseract are essentialy not available. The option to turn it off is essentially hidden, and the user can't find out that information is being blocked (as seen by the reaction it caused in the threadiverse). It's censorship by omission of information. Even if they had good intentions, the way they went about it failed to communicate what the blocklist was about, and that information was being blocked in the first place.
It's also just kind of a silly thing to implement in a client. That's the perspective the memes are coming from. Usually, blocklists should be left to the instance administrators or users. The client should only easily allow such a list to be available.
That's not the issue. Admins running the UI and other users didn't know this was in it.
I am still of the opinion that sports should never be taken this seriously, let alone to this degree.
I could run that on my laptop 😎
(barely…)
I miss bone hurting juice
Naw the sky cannot turn yellow when I have a cough 😭
What did you mean by that?
Hesitating on staying hydrated…
Strangely enough, antidepressants help for being able to actually feel hungry.
Because they all have Lemmy accounts, of course?
Naw I'm just gonna show this convo to my brothers and sisters who have dealt with generations of trauma due to American policies lmfao this is crazy.
Whitewashing US crimes is very tolerant, apparently.