Does anyone on here have a good book recommendation that walks you through things like dithering algorithms, poisson distribution, voronoi, etc? I want to get better at thinking about algorithms and understanding their implementations. I typically will find code that does a thing and I'll use it as a tool in my toolbelt. I can usually tell that the code isn't optimal, but it's a different skill to see that the algorithm isn't a good fit for project / platform.
Remote
Jonathan Gerlach
@JonathanGerlach@mastodon.social
mastodon 4.8.0-nightly.2026-10-06He / Him
336 Followers
960 Following
26 Posts
Joined January 06, 2017
Location:
Burlington, VT
Replying to
@isaiah@mastodon.social If you have IDs which link back to the description of the work, put it in the branch name, for your future self.
Replying to
@isaiah@mastodon.social Make a new branch for each bug. Use git to hop between branches. Delete the branch afterwards. You can probably get away with force push to rewrite a branch’s history, but as soon as you have other people, you’ll want to disable that. I use git flow, but I don’t always follow it so strictly.
I said to someone that I’m not doing the Magic: The Gathering tournament today because I don’t know how to play and, in a very Vermont fashion, someone turned to me and said he runs Dad Guild and they have a “Learn Magic to play with your kid” event I should attend. There are kind people hiding in the shadows.
Replying to
@iKyle@mastodon.social Eli Schiff did some great work on making really "buttony" buttons. https://elischiff.com/blog/2013/05/04/aesthetics-and-the-question-of-dimension/ https://dribbble.com/EliSchiff I don't know where he went, lately.
Replying to
@isaiah@mastodon.social When I’m a team lead, I think it’s important to go “by the book”, so there’s a pattern for others to follow. At my current company, things are really loose, so I don’t have as many processes or branches. On my home projects, I can’t ever get anything done. 🙃
I’m daydreaming about retrofitting Donut Labs’ batteries into all the things. Phones, laptops, wireless headphones, etc. I know thot these will probably be used for grid support and EVs first, but I hope tech-oriented people will get them too (and soon). https://www.donutlab.com/battery/
Downtown Burlington today
Replying to
@drwhitt@mastodon.social @fahrni@curmudgeon.cafe I ported ffmpeg to the iPhone in 2011 for a project. I plan to build a library which falls back to ffmpeg if it doesn’t have a more performant tool in the toolbelt. It will probably be very difficult, which is why I would start small.
Replying to
I realized that STL is something that maybe only old people would know about.
STL is a C++ library which attempts to separate algorithms from their storage. For example, you have a sorting algorithm that can sort a bunch of things. The algorithm and the things being sorted and the way they're stored in memory are all orthogonal. You can swap out your own novel storage mechanism.
I would be building something similar, but for making codecs.
Replying to
@dosnostalgic@mastodon.social https://dos.zone/howitzer/ is the one I played a ton. https://archive.org/details/Howitzer_1020
Replying to
@fahrni@curmudgeon.cafe @roadside@tech.intersects.art Walkie Talkie Coffee Shop in Canton, OH
Replying to
@fahrni@curmudgeon.cafe The indie game developer who made Braid wanted a better language than C++, so he made one. The language compiles very fast, but last I saw it was still in beta and closed source. Maybe it will always be closed source? Imagine a better Swift, where any reasonable app could be built in one second. 100k lines? One second build, where 60% of the time is linking.
Replying to
@fork_dev@mastodon.social Thanks for your hard work. I was very happy with Tower, but when they switched to a subscription model, I added up what it would have cost if they had been a subscription the whole time (too much). I found Fork and I've been happy this whole time!
Replying to
If would be nice to have a copy of Wikipedia that’s private and shared with your group.
My thoughts have drifted from development team to community. I wonder if you could scale something like this or if someone’s bad computer hygiene would ruin it? Think “device posture”, not Tragedy of the Commons (which is made up).
Replying to
I assume it’s temporary and will wear off, like when you stop going to church or stop drinking soda.
Replying to
@Aaronvegh The Death Star does bring a lot of value to the empire.
Replying to
@isaiah@mastodon.social This is the best news. I remember when I found out that AirParrot and Reflector had done $2 million in sales. Feels good.
Replying to
@itsfoss@mastodon.social This is also how I feel using Ubuntu when I'm used to illumos and Alpine.
I wonder if anyone had yanked the guts out of the MacBook Neo and put them in a thicker case with a better keyboard.
I wish it was easier to know the impact of going IPv6-only in my mail system. There are a few others that I wish I could just magically know.
The impact of:
- IPv6-only mail delivery
- Strict TLS-only connections
- Rejecting mail without the basic DKIM stuff
- Moving the actual mail server to my home network and using proxies and WireGuard tunnels to pass the mail to the server
I could try all of these out, but it would take precious time.