ruffsl

joined 1 year ago
 

Having recently picked up woodworking after building my own office desk, this hit rather close to home.

Related HN discussion:

[–] ruffsl@programming.dev 3 points 11 months ago

Thanks, fixed!

24
10 weird algorithms (youtube.com)
submitted 11 months ago* (last edited 11 months ago) by ruffsl@programming.dev to c/programming@programming.dev
[–] ruffsl@programming.dev 2 points 11 months ago (2 children)

Has Bryan done any more recent recorded talks?

 

I feel like there was a missed opportunity to use some of the spare computing power on the desk to add some helpful navigational autonomy. Like using a backward facing web camera for lane assist, obstacle avoidance, route following, etc. Could leverage something open source like Autoware.org to get most of the way there.

Source video by Joel Creates:
https://youtu.be/mDndd_EzkgA

[–] ruffsl@programming.dev 2 points 11 months ago

The only experience I have with working with Fortran would be setting up gfortran when building SciPy from source, and perusing its codebase to see how it's FFT functions were so optimized. Not enough to diligently mod I'm afraid.

[–] ruffsl@programming.dev 3 points 11 months ago

That's would be one long commute to the job site. Likely only a one way trip. I guess if cryostasis every becomes viable for human space flight, you'd have a better chance living long enough to catch up to the craft, but then you'd probably have the hassle of getting reassigned to a new office team, given all your old colleagues would have long retired, and who would really want to start patching hardware in production with a support crew you only just met after waking up. Sounds like a tough remote working environment, with all the cons in a aynchronous workplace, but with none of the perk in working from home.

[–] ruffsl@programming.dev 9 points 11 months ago (4 children)

I was thinking of cross posting this to a Fortran community, but it looks like we don't yet have one.

73
submitted 11 months ago* (last edited 11 months ago) by ruffsl@programming.dev to c/programming@programming.dev
 

Have you ever wondered how NASA updates Voyager's software from 15 billion miles away? Or how Voyager's memories are stored? In this video, we dive deeper into the incredible story of how a small team of engineers managed to keep Voyager alive, as well as how NASA could perform a software update on a computer that's been cruising through space for almost half a century.

[–] ruffsl@programming.dev 2 points 1 year ago (1 children)

I'm not sure why, but GitHub's search engine, Blackbird, seems to be returning some erroneous results for this query:

Any chance you could narrow down your search to a list of repose that use the library that pulls in tnt_select() function, then clone and manually grep just those, or is it's use too common to index by?

Real funny that even narrowing down GitHub search to just the same repo doesn't help the query results:

[–] ruffsl@programming.dev 1 points 1 year ago* (last edited 1 year ago) (1 children)

Ah, I've got a old android phone that could be perfect for this. Thanks for the heads up about Macro Deck!

By the way, does Macro Deck utilize multi touch support? That could enable the use of modifier keys to expand the button functionality, without having the add so many dedicated buttons. For example, the video makes use of modifier for individually switching the keyboard and mouse without changing the video, in case using a multi screen KVM setup.

[–] ruffsl@programming.dev 2 points 1 year ago

That was really cool and got me inspired! Thanks for cross posting.

[–] ruffsl@programming.dev 1 points 1 year ago (1 children)

Is this like multi window support, or just floating panels within the VS code window's canvas?

For dual screen setups, sometimes I end up opening two instances of VS code for the same workspace, which seems a bit overkill.

[–] ruffsl@programming.dev 3 points 1 year ago (1 children)

I think you need two spaces before a line break, or double carriage returns, before starting a bullet list. That's the original markdown spec anyways. Other markdown flavors, like what GitHub uses are a little more forgiving with that but are then non standard.

[–] ruffsl@programming.dev 13 points 1 year ago

Pain... This too painful to be posted as just a meme...

view more: ‹ prev next ›