Live data from Hacker News

Ask HN: Tools you have made for yourself?

news.ycombinator.com

281–290 of 458 posts

Re: Ask HN: Tools you have made for yourself?

#282
The first one that comes to mind is a super simple (and hideous) app to stick images together in the layout of your multiple monitors in order to create a spanned wallpaper with a different image on each display. I created it ages ago when Electron was relatively new, and I still use it every month or so.

https://github.com/jacobmischka/wallpaper-adhesive

Re: Ask HN: Tools you have made for yourself?

#283
I've been learning rust recently and trying to make a few CLIs/TUIs for simple tasks.

I have a simple CLI for handling the `$PATH` environment variable [0].

And I have a simple TUI for keeping track of financial statements for various accounts [1].

[0]: https://github.com/jrhawley/pad-path

[1]: https://github.com/jrhawley/quill

Re: Ask HN: Tools you have made for yourself?

#284

Earlier quoted context omitted.

"as well as the parts I don't want (which I indicate in-video)" How do you indicate that in the video?

Well, https://youtu.be/Bdoi7BDhrWc explains that with a demo. But tl;dr-- after a segment I want to keep, I switch my background to solid green; after a segment I want to drop, solid red. (Segment == clip between two solid red or green backgrounds)

That's a really interesting and clever idea, well done.

Re: Ask HN: Tools you have made for yourself?

#285

I made this for fun after watching some breathless microsoft video about AI in VS code which amounted to autocomplete sorted by popularity. I told a friend I could knock out something more useful (at the time) in half an hour. It's a ahk wrapper of howdoi designed to find code snippets from stack exchange and put them right into the code file you are editing. It is so simple but I actually found it pretty useful for…

Can you explain what it searches for? Is it the 'I feel lucky' first code block from the first match of the search term?

How does it know the language? Window title?

Re: Ask HN: Tools you have made for yourself?

#286
I made Strainer, a CLI utility for finding duplicate lines in one or more files: https://github.com/brundonsmith/strainer/

My original use-case was looking for copypasta across a CSS project, but more recently I dug it back out to strip duplicate entries from a set of enormous EasyList (https://easylist.to/) files I was working with

Re: Ask HN: Tools you have made for yourself?

#287

I built a weightlifting workout tracker. I did this because at the time I wrote it (2014) none of the current tools fit my use cases due to the fact that I compete in the sport of Olympic weightlifting and this was still pretty rare back then. I also wanted to be in control of my data and be able to run analysis on it as I saw fit. I began by writing a django app deployed via heroku. I then decided I wanted to rewrit…

I did something very similar using via a flutter mobile app when that was pretty new, and I also still use it every time I lift multiple times per week. Well done!

Re: Ask HN: Tools you have made for yourself?

#288
https://codingfriends.github.io/Tincta/

While studying a friend and I used a text editor called Smultron for all our VHDL and HTML/JS scripting. The developer stopped supporting it for a while and we got annoyed by unfixed bugs. In the end we missed having this little, easy to use tool so much that we wrote Tincta. It was heavily inspired by it. It doesn’t get enough love nowadays but I still use it for short notes.

Re: Ask HN: Tools you have made for yourself?

#289
post #266

My SEO Live Test Framework https://chrome.google.com/webstore/detail/franz-enzenhofer-s... Runs a lot of SEO checks (including Google Search Console Data) over your websites Static,Rendered and Idle DOM Built it cause I can and put lots of my technical SEO edge cases knowledge in there.

Nice I will have to have a proper look at this when i get back to work on Monday

Re: Ask HN: Tools you have made for yourself?

#290

I have a small YT channel [1] and I used to spend 30-40 mins recording and then 2-4 hrs editing to get a final 10-15 min video. Then I fully scripted my video editing using Python+MoviePy [2]. The time savings are sweet. I just feed it my raw video and get the finished video a few minutes later. It cuts out all the dead air as well as the parts I don't want (which I indicate in-video). In general scripting video edit…

As an oldies station DJ from back home would say, this is good stuff! The use of screen color as an in-band indicator for what segments to keep or toss is especially elegant.

One question: If you find yourself silent for some period that you want to keep (maybe while something happens on the screen), how do/would you inhibit the dead air filtering?

Post reply on HN