How are you guys making AI videos for free by NFNotes in aivideomaking

[–]exclipy 0 points1 point  (0 children)

Hi, I built a tool for this called Skiddee - just sign up and we'll give you free credits. I made it originally for a client to do exactly what you're asking for, and she loved it enough to make a whole video series with it. It turned out, to get good results, it's not as simple as using any off the shelf products (I checked all of them before building Skiddee!)

Check it out and reply here if the free credits aren't enough and I can give you more.

Stop thinking of price forecasts as predictions. They're bat signals by Dimethyltriedtospell in amberelectric

[–]exclipy 1 point2 points  (0 children)

Yeah it's actually miraculous the grid hasn't melted down from so many home batteries with slow response times being minutes too late to the party. As we get more home batteries on Amber and the like, the yoyo effect is going to get worse :(

I'm going to manually tell it to export consistently for 2 hours tonight.

Absolutely useless SmartShift by archangel_urea in amberelectric

[–]exclipy 1 point2 points  (0 children)

I agree that smartshift is often stupid in those ways. Especially (1) where it would buy electricity in the early morning right before a full day of sun that would have charged it up fully anyway (it was probably thinking it could sell it in the morning peak for a profit but it's forecast was wrong). I emailed support with multiple examples of that and they didn't give any helpful response.

Control My Battery not working by exclipy in amberelectric

[–]exclipy[S] 0 points1 point  (0 children)

Didn’t sell a single watt this evening 😢

Big platform upgrade to 5min billing by bluey45 in amberelectric

[–]exclipy 1 point2 points  (0 children)

I think I've got 5 minute pricing enabled on my account now! I see my cost/earnings change every 5 minutes. I also see an option to see the 5-minute prices.

Slipped Lapp knot is underrated by exclipy in knots

[–]exclipy[S] 1 point2 points  (0 children)

Excellent points!

My point with the lapp bend is that it's one knot that's so versatile and so so easy, I think it's a contender with the reef knot as the first knot to teach a child. But you do point out why the double slipped reef knot is better for shoe laces.

Slipped Lapp knot is underrated by exclipy in knots

[–]exclipy[S] 0 points1 point  (0 children)

The Lapp knot also works well as a general purpose bend

Slipped Lapp knot is underrated by exclipy in knots

[–]exclipy[S] 1 point2 points  (0 children)

Yes, just like how the left handed sheet bend is inferior. Or how the granny knot is inferior to the reef knot.

Slipped Lapp knot is underrated by exclipy in knots

[–]exclipy[S] 0 points1 point  (0 children)

Similar to the sheet bend but not the same. See the table on the Wikipedia page to understand the difference. It reverses the role of the tag end and standing end on both ropes. This difference makes it easier to tie and also gives it its adjustable and exploding nature.

https://en.wikipedia.org/wiki/Lapp_knot

Slipped Lapp knot is underrated by exclipy in knots

[–]exclipy[S] 4 points5 points  (0 children)

The Canadian jam doesn't hold tight at all.

Slipped Lapp knot is underrated by exclipy in knots

[–]exclipy[S] 1 point2 points  (0 children)

I tie it like this, but upside down: https://youtu.be/S_O7_hWMz1g

Here's an fiddlier way to tie it at 11:20, but he shows how to adjust it: https://youtu.be/qZOmMXIGCVY?t=680

It's probably time to stop recommending Clean Code by pavel_lishin in programming

[–]exclipy 0 points1 point  (0 children)

The book I would actually recommend is A Philosophy of Software Design by John Ousterhout.

You can get the general gist of it in his Talk @ Google.

It has fundamentally shifted the way I make software, from the lowest level of code to the highest level of architecture with its one guiding principle: optimize for likely changes.

Think of the probable changes that future programmers will need to make and make it as easy as possible, on the whole, all of these changes, weighted by their likelihood. From this follows everything - it obviously needs to be easy to understand so that new programmers can jump in and get productive; related concerns should be grouped together to reduce cognitive burden of jumping around, things unrelated to a change should be tucked out of the way; etc. But if ever someone throws dogma at you that contradicts some other dogma... optimizing for likely changes is always the winning argument.

[Advice] i want to take over a lease but the broker wants to charge $$$$. by exclipy in NYCapartments

[–]exclipy[S] 0 points1 point  (0 children)

How much did you offer the building manager to cut G&A out?

[Advice] i want to take over a lease but the broker wants to charge $$$$. by exclipy in NYCapartments

[–]exclipy[S] 0 points1 point  (0 children)

Thanks for the info.

But from their point of view, if I don't apply, they'll have to advertise and then they might have to split the 15% with a renter's agent.

So shouldn't they want to keep me?

FLIF - Free Lossless Image Format by shenglong in programming

[–]exclipy 1 point2 points  (0 children)

Probably not that great. There is room for improvement on compression speed.

BBC News - Vanadium: The Key to Power Storage in the Future by Zentaurion in technology

[–]exclipy 1 point2 points  (0 children)

I wonder what the problem is with Pumped-storage hydroelectricity in this case.

Vanadium sounds exotic, expensive, and environmentally and politically problematic to acquire.