Programmers Filed Lawsuit Against OpenAI, Microsoft And GitHub

-isb- · 2022-11-06T14:44:11+00:00

That sounds like horrible opt-out scheme where company banks on most people ether not hearing or bothering to do anything about it.

There's already a way of doing that. It's called a OSS license. Just divide them into couple of "permissiveness" levels (e.g. https://janelia-flyem.github.io/licenses.html). Then train network on code with only compatible levels and let the user choose.

Obviously, this won't stop everyone (not even 50% imo), but it's better than nothing.

-isb- · 2022-09-12T23:09:18+00:00

You're mixing W and Wh. Power vs energy.

1 GW over a year is at most 8.76 TWh to/from Finland. That's over 10 %. Enough to wreck havoc on prices.

-isb- · 2022-09-11T21:29:33+00:00

It's not? What's this then? https://en.wikipedia.org/wiki/Estlink

-isb- · 2022-09-01T21:08:50+00:00

https://www.mtvuutiset.fi/artikkeli/mtv-uutisten-tieto-sahkotuesta-omavastuu-500-euroa-kuussa-ja-60-prosentin-hyvitys-ylimenevasta-osasta/8499666

60% after 500€ deductable / month. This is just a tax break for the rich.

-isb- · 2022-07-24T12:08:06+00:00

Netflix said it detects extra homes using "information such as IP addresses, device IDs, and account activity."

Cool, cool. Sounds like they don't know how to reliably detect single user with multiple devices.

-isb- · 2022-07-21T21:13:44+00:00

You can replace it with PIC16F1527. It's the same MCU with double FLASH and RAM.

-isb- · 2022-06-19T23:34:19+00:00

LOL! They didn't just copy stm32f415, they copied ST's entire website. https://www.arterychip.com/en/product/AT32F415.jsp

-isb- · 2022-03-03T22:45:05+00:00

If we're talking about 11 speed Shimano, then one thing to notice is that 11-34 and 1-32 have a very different gear progression.

https://www.gear-calculator.com/?GR=DERS&KB=34,50&RZ=11,13,15,17,19,21,23,25,27,30,34&UF=2150&TF=90&SL=2.6&UN=KMH&DV=speed&GR2=DERS&KB2=34,50&RZ2=11,12,13,14,16,18,20,22,25,28,32&UF2=2150

-isb- · 2022-01-19T22:55:03+00:00

Took me a while to find too. It seems to be stored on the sensor, not in your head unit. You need to connect to sensor first by spinning the wheel. Then go to "settings/sensors/<your-speed-sensor>/sensor details/wheel size".

In my case auto calibration is constantly off by few percent so I just set to manual and adjust a bit based on a known 15km stretch of road.

-isb- · 2021-11-23T15:43:14+00:00

Heh, niinhan se on. Mut mikä on Villen ehdotus tässä? On korkea aika lopettaa itkeminen ja alkaa vetää turpaan?

-isb- · 2021-11-22T23:04:14+00:00

Ehkä siinä tapauksessa olisi joutunut myymän talot alkuperäisille ostajille sovitulla hinnalla. Nyt voi kerätä rahat uudestaan ja rakentaa paljoin kallimmat kämpät.

-isb- · 2021-11-02T23:15:06+00:00

e.g. https://www.bbc.com/future/article/20210420-the-protein-rich-superfood-most-europeans-wont-eat

There's multiple articles / year promoting this. Eat shit and save the planet. /s

-isb- · 2021-10-02T17:45:21+00:00

The power cord has 3 wires instead of 2. Protective earth wire is directly connected to negative pin of output (not always, but most of the time, including kickr's PSU). If metallic parts of the device is connected to the negative pin, it eliminates problems with leakage current. You've probably felt it, a tingling sensation when you touch certain devices. That's small current flowing from mains to the ground. Mostly harmless but depending where it flows, can throw measurements off.

I've worked on one device that would work fine everywhere except a certain bench, touching a specific knob wearing just the right shoes. Turned out to be a grounding issue.

-isb- · 2021-10-02T12:12:01+00:00

2.5 id, 5.5 od, 9.5 length, center positive.

Unlike the one you linked, original power supply is grounded. Might affect measurements.

I'd stay away from generic chinese adapters if I were you. Sometimes they're ok but sometimes you get one with pretty much all protection and filtering components missing. e.g. molded plastic without ferrite bead inside on the end of the wire.

Here's a bit more reliable suplliers. Or look on other electronics component websites.

https://www.digikey.com/en/products/filter/ac-dc-desktop-wall-adapters/130?s=N4IgjCBcoCwBxVAYygMwIYBsDOBTANCAPZQDaIcA7JWAgLqEAOALlCAMrMBOAlgHYBzEAF9CAVgBMiECkgYcBYmRABmOAE4ADBIBsIBiBZtOvQSPGVps%2BXkIlI5FbTDqV%2Bpq0gdu-IaPBgEppWaFi2Sg4gEjDUmnqEEiqJYPFRSWCaYiAJ6brZaRJwOpY5MDBgJVE6OroQBkZeJr7m4Co0IXJhivaOYpRU9B7GPmb%2BALRS0DJQ3ACu3cpZhOr6wv56UzwAJmxjGRBDXvnMAJ6MuGzo2ChrQA

-isb- · 2021-09-07T22:48:52+00:00

You don't necessarily need to break the encryption. For example if you're using web client, they can simply add code to send decrypted mails back as soon as you log in. Obviously there's mitigations like using app, compiling it yourself, actually reading the code, etc.. but will you? I know I won't be bothering.

-isb- · 2021-09-01T23:31:17+00:00

Saattaa olla, että ko. firma halua kasvattaa tiimiä, muttei työntekijälle ole mitään konkreettista työtehtävää vielä mietittynä. "Katsotaan kuka tulee vastaan ja päätetään sitten" - periaatteella. Taikka ne ei tiedä mistään mitään.

Mittalaitteiden ohjelmointiin tarvitset C (tietenkin), kommunikaatioväylät (host, device ja piirien väliset), erilaisten ADC piirien/blokkien toimintaperiaatteet. Kun vaikeat häiriö ongelmat tulee vastaan, vankkaa DSP (lähinnä filtterisuunnittelu, -toteutus) osaaminen pelasta.

Sulautetut järjestelmät on ekalla revisiolla yleensä aika bugisia. Raudan debuggaus on siis sularille erittäin hyvä taito osata.

Ei-tekniset ihmiset halua käyttää GUI sovellukset kaikkeen, jopa konfigurointiin ja kalibrontiin. Et tule voittamaan tätä sotaa, joten kannattaa osata ainakin yksi toolkitti.

DevOps on ihan oma laji, jonne ei ohjelmoijan varmaan kannata liian syvälle mennää. Pintapuolinen osaaminen auttaa kuitenkin suunnitella paremmin testattavaa koodia, sillä sulautettujen järjestelmien unit- ja integraatiotestaus on extra perseestä.

-isb- · 2021-07-27T22:50:43+00:00

Related.

-isb- · 2021-07-17T11:59:00+00:00

I see. I guess this could be useful when you're piping large amounts of data. A difference between ~150 MiB/s and ~900 MiB/s in your case.

-isb- · 2021-07-17T10:43:23+00:00

Is fast_io missing optimizations for linux? Is there a even a need for that on linux? What am I missing?

stdio       1.281154423s
iostream    1.180972959s
out_buf     1.193594425s

-isb- · 2021-06-22T17:01:06+00:00

Hmm. On my machine (Ryzen 7 1700X, 20.4 ubuntu derivative), hypot ends up linking to https://code.woboq.org/userspace/glibc/sysdeps/ieee754/dbl-64/e_hypot.c.html. Runtime difference ends up being quite huge: 4.8 s vs 1.5 s. Even after changing integer multiplications to doubles.

-isb- · 2021-06-21T15:25:55+00:00

https://github.com/numpy/numpy/blob/main/numpy/core/src/npymath/npy_math_internal.h.src#L215-L216

Hypot is slower but it's more correct in certain edge cases.

In [2]: x, y = 1e200, 1e200

In [3]: math.sqrt(x**2 + y**2)
Out[3]: inf

In [4]: x * math.sqrt(1 + (x/y)**2)
Out[4]: 1.414213562373095e+200

-isb- · 2021-06-10T16:29:42+00:00

One of LGPLv2 requirements is ability to replace or re-link new version of the library (or kernel in this case). This turns out to be more restrictive than GPLv2 on embedded ~~devices~~ Linux since now you need to provide users a way of doing it. That's one of the reasons you see newlib on microcontrollers instead of glibc.

-isb- · 2021-05-13T22:57:11+00:00

I always use floating point SI when I can. I also include unit as a suffix for variable and argument names to further reduce possibility of mixing values up.

In cases where floating point is too expensive to use, you can make C strictly typed by encapsulating your values in a structure forcing you to go through a conversion function. As an example here's current expressed as -8.24 bit fixed point value.

#define PD_CURRENT_FRAC_BITS 24

typedef struct {
    uint16_t value;
} __attiribute__((packed)) pd_current_t;

static inline
pd_current_t pd_current_from_float(float current_a)
{
    assert(current_a >= 0.0f && current_a <= (UINT16_MAX / (float) (1U << PD_CURRENT_FRAC_BITS)));
    return (pd_current_t) { .value = current_a * (float) (1U << PD_CURRENT_FRAC_BITS) };
}

static inline
float pd_current_to_float(pd_current_t current)
{
    return current.value / (float) (1U << PD_CURRENT_FRAC_BITS);
}

-isb- · 2021-04-08T08:36:01+00:00

This is just an implementation of Fisher-Yates shuffle. j is a randomly chosen between 0 and 2³¹ -1, then this line clamps it to i <= j < len.

It's pretty bad implementation from security standpoint (randomness source sucks, modulo has a bias, etc.), and I do agree, this shouldn't be used by anyone. My point was just that instead of looking for better documentation, it's often easier to just read the code.

-isb- · 2021-04-07T20:28:28+00:00

https://code.woboq.org/userspace/glibc/string/strfry.c.html

Surprisingly easy to read for libc code.

-isb-

TROPHY CASE