nik9000 @ nik9000 @programming.dev

Posts

1

Comments

133

Joined

2 yr. ago

I've been using a sonicare for years now. I think it was expensive but it's lasted forever and does a great job.

I was bored on an airplane a while back and discovered a Japanese movie adaptation of A Door Into Summer: https://www.rottentomatoes.com/m/the_door_into_summer

It'd been 25 years since my mom read the story to me so I can't tell you how accurate the adaptation is but it hit the parts I remembered.

https://youtu.be/A6_LW1PkmnY?si=3hFwliooS3sevlYT

My entire professional persona is tied to the username I thought was super cool when I was 12. I'm so glad it's not offensive and only a little lame.

I like this video with it.

That's why I hate Ferris wheels. Every time.

Although it was his first day in charge, Sliney had an over-25-year background in air traffic and management in the FAA.

Sorry. I wasn't clear. If the conditional is constant a compile time you get the dead code optimization. The path not taken is removed. If it's not constant at you may get the loop invariant movement. But only if the compiler can tell that it's invariant.

My point wasn't that you should always rely on this behavior. At least, I didn't mean to say that. I suppose what I should have said is more like "in many cases you won't see any performance difference because the compiler will do that for you anyway."

I suppose I have value judgements around that like "generally you should do the thing that is more readable and let the compiler take care of stuff like moving the loop invariant". That's been mostly true for me. But only mostly.

I don't believe you have to specify the condition at compile time. I think that optimization would fall under dead code elimination.

For the invariant code motion stuff the comparison just has to be invariant from start to finish. At least, that's been my experience. The compiler will just shift the if stement.

But, like, there are totally times when it can't figure out that the thing is invariant. And sometimes it's just more readable to move the if statement out of the loop.

I'm reasonably sure compilers can shift the if out. I believe it's called "loop invariant code motion". Won't work in call cases, but in the variable case it should.

I'm bad at everything else.

The last project I fell in love with was Elasticsearch. About ten years ago. I was building a search and everything was wrong with solr. I switched to elasticsearch and it was smooth. They had built so much of what I needed. And at the time they were apache licensed which was amazing for us. The world's kind of moved a long way since then. I'd love to fall in love like that again. I just don't haveany opportunities.

We ask algorithm questions and I feel bad about it. But a nontrivial portion of the job really is adapting these algorithms to novel scenarios. Not most of the job, but maybe the hardest part.

I use it for work so to entirely leave it they'd have to move away. That seems unlikely.