lukstru

Tbh I don’t care about the sponsor segments in videos. It’s actually my favorite way of advertising, as I can skip it or watch the funny ones (tomska does really funny - although slightly incorrect - segments).

But boy do I hate sponsored results on Amazon or similar platforms. I feel like I have to search through them to get to the actual products, and then I can’t trust the reviews

I think the problem with creating a printer is that you have to have a reliable source of ink that will not sue you if you use their designs

That moment when you put the hat on your head, and it puts you in Hufflepuff, but then you put it on your dick and it puts you into Slytherin

Anyone else has the head canon of them having daily physical fist fights? I would get annoyed by that as well.

Oh thanks, I didn’t know that. I thought it was an all purpose PCIe connector. Is there any way to find out whether it supports SSD storage? Is that way the dmidecode from my other comment (and basically saying that it doesn’t support storage?)

It looks like it is one, but dmidecode doesn't show it.

# sudo dmidecode --type slot           
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.

Handle 0x001C, DMI type 9, 17 bytes
System Slot Information
        Designation: J6B2
        Type: x16 PCI Express
        Current Usage: Available
        Length: Long
        ID: 1
        Characteristics:
                3.3 V is provided
                Opening is shared
                PME signal is supported
        Bus Address: 0000:ff:10.0

Handle 0x001D, DMI type 9, 17 bytes
System Slot Information
        Designation: J6B1
        Type: x1 PCI Express
        Current Usage: Available
        Length: Short
        ID: 2
        Characteristics:
                3.3 V is provided
                Opening is shared
                PME signal is supported
        Bus Address: 0000:ff:1c.4

Handle 0x001E, DMI type 9, 17 bytes
System Slot Information
        Designation: J6D1
        Type: x4 PCI Express
        Current Usage: Available
        Length: Long
        ID: 3
        Characteristics:
                3.3 V is provided
                Opening is shared
                PME signal is supported
        Bus Address: 0000:ff:1d.0

Handle 0x001F, DMI type 9, 17 bytes
System Slot Information
        Designation: J7B1
        Type: x1 PCI Express
        Current Usage: Available
        Length: Short
        ID: 4
        Characteristics:
                3.3 V is provided
                Opening is shared
                PME signal is supported
        Bus Address: 0000:ff:1c.5


Wrong DMI structures length: 3135 bytes announced, structures occupy 3136 bytes.

Sugar increases the risk of health complications, therefore selling products containing added sugar is assault

Science hippies answering questions no one asked

It matters as soon as a requirement change comes in and you have to change something. Writing a dirty ass incomprehensible, but working piece of code is ok, as long as no one touches it again.

But as soon as code has to be reworked, worked on together by multiple people, or you just want to understand what you did 2 weeks earlier, code readability becomes important.

I like Uncle Bobs Clean Code (with a grain of salt) for a general idea of what such an approach to make code readable could look like. However, it is controversial and if overdone, can achieve the opposite. I like it as a starting point though.

Yep, that's what it usually boils down to. However, I think a slight approach shift for basic materials could be useful, where introductory books / papers / ... write out formulas. That makes it easier to understand the basic concepts before moving onto the more complex stuff. It should be easy to create such works, as they are usually created digitally, and autocomplete is available. Students can and will abbreviate those written outs words by themselves (after all, writing is annoying), but IMO reading comprehension is the key part that can be improved.

Also, when doing long formulas that you want to eliminate members of, writing stuff out can be a nightmare.

I recently held a science slam about this topic! It's a mix of the first computer scientists being mathematicians, who love their abbreviations, and limited screen size, memory and file size. It's a trend in computing that has been well justified in the past, but has been making it harder for people to work together. And the need to use abbreviations has completely gone with the age of auto completion and language servers.

Nice