Ephera

joined 5 years ago
[–] Ephera@lemmy.ml 1 points 3 hours ago

Es gibt keine Booleschen Operatoren zur Verknüpfung von Bedingungen

Bin der Letzte, der Python verteidigen wollen würde, aber doch, die gibt es. Sind nur etwas unüblich benannt mit and, or und not:

https://docs.python.org/3/reference/expressions.html#boolean-operations

[–] Ephera@lemmy.ml 4 points 11 hours ago

Yeah, or their parents argued a lot and they don't want to end up in a relationship where this is the case. This can also mean they're quick to exit a relationship as soon as the first conflicts need to be resolved, because it feels like a sour relationship to them.

[–] Ephera@lemmy.ml 3 points 15 hours ago
[–] Ephera@lemmy.ml 14 points 20 hours ago (1 children)
[–] Ephera@lemmy.ml 6 points 21 hours ago (1 children)

I'm towards the hyperphantasic side of the spectrum and I've also noticed that it influences quite a lot of things.
Perhaps the biggest factor is that I don't have the same drive to visit places or people. I could travel to a castle to look at it, or I could do so in my mind. I could meet back up with an old friend, but as I think of them, my desire to see them again is satiated. This does mean I'm terrible at maintaining friendships and socializing in general.

[–] Ephera@lemmy.ml 3 points 1 day ago

I would definitely contact their support. They're generally quick to respond and help. And if something is bad with the hardware, you want to resolve that now when you're still well within warranty and it is clear that you did not break it.

[–] Ephera@lemmy.ml 2 points 1 day ago

Oh yeah, I do think setTimeout executes in parallel, so only the largest element determines the execution time. It was difficult enough to make that sentence make sense, so I didn't want to cram that detail in as well. 🙃

[–] Ephera@lemmy.ml 11 points 1 day ago (2 children)

I mean, it does scale with the size of the input. Just not with the count of inputs, but rather the size of each input element.

[–] Ephera@lemmy.ml 16 points 1 day ago

To me, a big part of it is that I'm tired of commodity art. I don't care about your pretty pixel soup. I've seen other pixel soups before that were similarly pretty.

And I've been tired for many years, long before every middle-manager under the sun could cook up their own pretty pixel soup.
Back then, it was humans trying to make a living off of their passion and then settling for commodity art to make ends meet. I was cheering them on, because they were passionate humans.

Now that generative AI has destroyed that branch of humanity, there's no one to cheer on anymore.
Even if generative AI never existed in the first place, I'd like to see commodity art being relegated to the sidelines and expressive art coming into the limelight instead.

Tell me a story with your art. About your struggles or a brainfart you had, or really anything. This comic is great, for example. There's emotions there and I can see the human through the art. I would've chosen a very different illustration for whatever, for example, which tells me a lot about the artist, but also about myself.
I have never had that kind of introspection with pretty pixel soups.

[–] Ephera@lemmy.ml 2 points 2 days ago (1 children)

I agree in general, that a crash is much better than silently failing, but well, to give you some of the nuance I've already mostly figured out:

  • In a script or CLI, you may never need to move beyond just crashing.
  • In a GUI application or app, a crash may be good (so long as unsaved data can be recovered), but you likely need to collect additional information for what the program was doing when the crash happened.
  • In a backend service, a crash can be problematic when it isn't actually necessary, since it can be abused for Denial-of-Service attacks. Still infinitely better than failing silently, but yeah, you gotta invest into logging, monitoring and alerting, so you don't need to crash to make it visible.
  • In a library, you generally don't want to trigger a crash, unless an irrecoverable error happens, because you don't know where it'll be used.
188
submitted 3 days ago* (last edited 3 days ago) by Ephera@lemmy.ml to c/programmerhumor@lemmy.ml
 

Increasingly so, the more experienced I get...

142
Underappreciated top (friendo.monster)
 

Always thought top was one of those programs frozen in time since the 70s, but apparently, it has a feature set comparable to htop and the like. The default configuration just doesn't show much of it...

 
 
-14
submitted 1 month ago* (last edited 1 month ago) by Ephera@lemmy.ml to c/dadjokes@lemmy.world
 

Spoilertrans-parent

 

Found this article interesting. Some (technological) highlights for me:

She initially wrote simple Python scripts to help with chain-of-custody problems. Those scripts worked on her machine, but she had trouble delivering the software to the people who actually need it.

Yeah, Python, Java etc. are quite portable in theory, but we also always ship the runtime along with it at $DAYJOB, because we don't want to deal with different runtime versions and users failing to install them properly. And since the runtime is compiled for specific platforms, we effectively have non-portable artifacts anyways.

Deuson's first attempt at distributing her software was to bundle it using Kubernetes. That sort of worked, but it turned out to be hard to get it installed in police departments. Opening ports in the firewall is also often prohibitively hard. "Getting software into these environments is really difficult."

Eventually, she decided that the only way to make this work would be to write a single, standalone executable that does everything locally. It would need to be able to run on ancient desktop computers, in a variety of environments, without external dependencies. That's why she ultimately chose Rust to write FolSum.

I feel like our industry poured tons of effort into making things deployable via Kubernetes, but there's still an absurd amount of niches, where this just does not make sense. Always interesting to hear about yet another such niche...

One thing that users really liked about the Rust version of the application was that it starts quickly, she said. Lots of commercial software is big and bulky, and takes a while to start up, leaving users staring at splash screens. FolSum starts up almost as soon as the user releases the mouse button.

Yep, I never quite buy it when this is deemed unimportant in commercial software development. The chance of your software running all the time is really low. And if it's not running all the time, I need to start it before I can use it. If I need to wait a minute for that, that takes me out of my workflow and I'll kind of hate your software for it.

It turns out that non-technical users like the approach that she has called "GUI as docs", where the application puts the explanation of what it does right next to the individual buttons that do those things. Several users have told her that they wished other software was written like this, to her bafflement. For-profit software is often a forest of features, which makes it hard to find the specific thing one needs, especially if the tool is only rarely used, she said.

I've been looking to take that kind of approach for our GUI at $DAYJOB, too. Our software is not either something that users use all the time. They might not look at it for months at a time. It's ridiculous to assume that they will remember all the concepts, just as ridiculous as it is to expect them to look at a completely separate manual every time. So, just dotting help texts around the place seems like a good idea.

 

Result presentation (first 25 mins) and discussion of an accessibility study that Thunderbird ran. They explain various accessibility technologies (like screen readers, eye tracking etc.) and problems they encountered in their design when users relied on these technologies.

Nothing really groundbreaking in here, but still good for challenging one's assumptions.

 
 
 

Und was macht ihr so um 1 Uhr nachts? Ich habe anscheinend noch eine Verabredung. 🙃

view more: next ›