FizzyOrange

joined 2 years ago
[–] FizzyOrange@programming.dev 6 points 2 weeks ago

Uhm, ship both. Most type systems are not expressive enough to 100% explain the correct use of an API.

[–] FizzyOrange@programming.dev 4 points 2 weeks ago

In my experience unless you are pretty much immediately popping the stash it's much better just to make a branch and do a normal commit. I would recommend avoiding git stash in general.

[–] FizzyOrange@programming.dev 2 points 2 weeks ago

Why? MATLAB is pretty dense normally, and most MATLAB code is hacky scripts that wouldn't bother with "boilerplate" anyway.

[–] FizzyOrange@programming.dev 1 points 2 weeks ago

Oh that reminds me. I wouldn't recommend PIC in the 21st century but there's a really cool project called BIO that is an open source alternative to Raspberry's PIO (programmable IO). It's RV32-E with custom x16-31 registers that control the pins directly. Very neat idea.

It's by Bunnies Huang and he talks about it in this talk about Xous.

The hardware is (or will be) here: https://www.crowdsupply.com/baochip

May be a bit hardcore for a beginner though.

[–] FizzyOrange@programming.dev 11 points 2 weeks ago

Sounds like you know plenty to learn Rust.

[–] FizzyOrange@programming.dev 3 points 2 weeks ago

Yes it has definitely changed. Before AI, writing code strongly indicated that the author had thought about the problem and put effort into solving it. Of course they could have still done it wrong but a) the chances are much higher with AI, and b) they're using up your time without spending any of theirs which breaks the social contract.

[–] FizzyOrange@programming.dev 3 points 2 weeks ago

Yeah I think just counting fully unique lines is going to really capture the repetitiveness of a language. I think you'd get more accurate results just asking people using pairwise ranking.

[–] FizzyOrange@programming.dev 5 points 2 weeks ago (2 children)

They wanted me to make some changes and with the normal workflow that's just git commit and git push. With git send-email I have no fucking idea and it got beyond the point where I had enough cared enough to fight the process.

[–] FizzyOrange@programming.dev 6 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

For bare metal definitely get a microcontroller and do some fun electronics project.

Easiest to get into is Arduino, but don't stick with that because its only redeeming feature is that it's easy to get into. The IDE sucks, the build system sucks, the APIs really suck, and the code quality is very low (probably because it's easy to get into so you get a lot of inexperienced people doing stuff).

After Arduino I would recommend either going to the Nordic nRF5x series - you can do some cool Bluetooth stuff, or even make you your own radio protocol since the radio peripheral is fully documented... Or ESP32 with Rust and Embassy is probably the most modern and slick way to do microcontrollers.

It does require learning Rust but Rust is really really good so you should do that anyway.

There are some extremely good videos on YouTube about that: https://youtube.com/@therustybits

I would probably still start with Arduino though since you know C. Just don't stay there for too long.

[–] FizzyOrange@programming.dev 9 points 2 weeks ago (4 children)

Yeah it's mad. Tbh I don't think GitHub PRs are the best workflow, but I absolutely know that git send-email is the worst. I tried to use it once to contribute to OpenSBI, which inexplicably also insists on it. Suffice it to say my patch was never merged...

[–] FizzyOrange@programming.dev 37 points 2 weeks ago (14 children)

... if you have a super janky patch file workflow.

If you are using Git like normal people do this can't happen.

[–] FizzyOrange@programming.dev 3 points 2 weeks ago

This is just straight up "ChatGPT write me an article about merge vs rebase".

It's also missing any discussion of squashing, CI, git blame, git bisect etc.

view more: ‹ prev next ›