I don't always use recursion; but when I do, I don't always use recursion.
about 4 minutes
SQL databases are still one of the best ways of storing relational data, but sometimes you hit a wall transferring your representation to or from a table based layout.
Say we have a table full of Foos, where some Foos may have other Foo parents.
This can easily be represented in a table with some unique primary key id, a secondary key parent, which joins to the parent's id, and whatever dataFoo may hold.
Retrieving this table into a rust data structure, we'd find ourselves with something like Vec<Foo>, where Foo is defined as
Make yourself a little nest of eggs. Where your eggs are perfectly round and magically float in free space.
about 7 minutes
So you want to do some sphere packing to make your inflatable space habitats for deployment on the Moon and Mars snug and cozy.
Perfectly straightforward you think to yourself; since one can start with a triplet of spheres tangent pairwise by placing one at some origin on a 2D plane, extending the second out in the \(x\) direction and completing the triangle by identifying the third sphere's position based on the radii of all three.
Productivity tools you employ to make yourself more efficient that actually take up most of your productive time.
about 5 minutes
One side project that has been sitting by the wayside since completing my PhD has been to polish up and publish Wafer: my fancy 3D wavefunction solver.
For reasons, one of which is mostly structured procratstination, this polishing ended up being a port/re-write in Rust.
Delving into the Rust ecosystem has been fun and if you check Wafer's commit history you'll notice large rewrites again and again as I basically play around with things; having no real development schedule or design restrictions.
It may seem a little counter intuitive then, that I'm also trying at the same time to learn all the rigid structures of software development.
Proper documentation, testing, error handling, data structures etc.