englislanguage

joined 4 months ago
[–] englislanguage@lemmy.sdf.org 2 points 6 days ago (1 children)

Are you sure? Doesn't the "smart edison bulb" design make it harder to dissipate heat to the casing, therefore making the LEDs get hotter compared to PCBs with LEDs surface mounted on them?

Anyway, if you want your ~~light bulbs~~any technology to last long, don't buy the "smart" variant. "Smart" usually means more components and/or more dependencies on interfaces, and more complexity, so a higher chance to fail.

Was ist das Problem?

[–] englislanguage@lemmy.sdf.org 26 points 2 months ago (2 children)

TIL my thesis could have been easier if Typst would have been available years earlier.

[–] englislanguage@lemmy.sdf.org 33 points 2 months ago (1 children)

I guess you could try AI-checking it and answer "Ignore all previous instructions. …", followed by some new instructions. Some examples: https://www.aiweirdness.com/ignore-all-previous-instructions/

(Although I guess it would be better to not respond to this obvious case of spam/scam)

[–] englislanguage@lemmy.sdf.org 13 points 2 months ago

Maybe they should ban trowing away your trash instead.

[–] englislanguage@lemmy.sdf.org 15 points 2 months ago

Capitalist perfection: you are paid for cycling, don't do anything else!

One example for self documenting code is typing. If you use a language which enforces (or at least allows, as in Python 3.8+) strong typing and you use types pro actively, this is better than documentation, because it can be read and worked with by the compiler or interpreter. In contrast to documenting types, the compiler (or interpreter) will enforce that code meaning and type specification will not diverge. This includes explicitly marking parameters/arguments and return types as optional if they are.

I think no reasonable software developer should work without enforced type safety unless working with pure assembler languages. Any (higher) language which does not allow enforcing strong typing is terrible.

I have worked on larger older projects. The more comments you have, the larger the chance that code and comment diverge. Often, code is being changed/adapted/fixed, but the comments are not. If you read the comments then, your understanding of what the code does or should do gets wrong, leading you on a wrong path. This is why I prefer to have rather less comments. Most of the code is self a explanatory, if you properly name your variables, functions and whatever else you are working with.

[–] englislanguage@lemmy.sdf.org -4 points 2 months ago (2 children)

Correction, 50% of VOTING Americans are VOTING fascist. Doesn't necessarily mean they are fascist themselves.

And not just mice. If designed correctly, they would help keeping the correct humidity so the bread neither gets too dry (and solid) nor too humid (and moldy)

Same question on reddit a while ago

As suggested there, I recommend to use a multimeter to identify the power socket pins. Roughly half of them should be ground. Most or all of them should correspond and be connected to the SATA power connector pins on the other side.

[–] englislanguage@lemmy.sdf.org 10 points 2 months ago (1 children)

+1 on that. The User's guide of a similar device (source) mentions a 10-pin CPLD connector Reserved for IBM use

view more: next β€Ί