1. 12

Feel free to tell what you plan on doing this weekend and even ask for help or feedback.

Please keep in mind it’s more than OK to do nothing at all too!

  1.  

  2. 12

    I’m working on a new type of “paint this like that” algorithm:

    https://twitter.com/marekgibney/status/1434534326943748100

    It already looks somewhat realistic, but creates some funky artifacts. I hope that by throwing more compute power at it, those will go away.

    1. 1

      Looking nice! Would be interested to hear how it works, are you using neural networks, or some other approach?

      1. 2

        Glad you like it!

        It is not really a conventional NN. It is a new direction I have been researching into for a few months now.

        I am not yet sure if and when I want to publish it. Or if it just stays the secret sauce of my personal artistic expression. We will see.

        For now, I will just explore it a bit more and tweet the results.

        1. 1

          Ah cool. I asked because I messed around myself with a realtime painterly effect, where I would render flow maps as textures on 3d meshes, then use a fullscreen compute shader to “paint” lines along the flow map. Ended up looking pretty cool, but more sketchy than painterly, was wondering if your approach might provide some inspiration :D

    2. 6

      I’m building new website called showing up It’s a collection of productivity app, that I normally need in one place. No sign up required everything is in localstorage.

      Currently brainstorming, what else I normally need

      1. 1

        That reminds me of a project idea I had a while ago but never really started: learned.today. A mix of “today I learned” and bookmark manager. I should come back to that.

        1. 2

          I always try to make tools that I need. If you need that, definitly go for it 👍🏽

      2. 6

        I will happily say: resting! I hope you do too!

        1. 3

          I fell into the Handshake rabbit hole. But I also have to finish a small game project that involves projected targets and axes

          1. 3

            My regex engine is this close to being ready to show. I’m hoping to get it feature complete this weekend.

            1. 2

              I love and hate regex at the same time. Curious of what you build

            2. 2

              I have a pull request opened for the asdf package manager that requires some attention, so time to fix it and hopefully it will get merged.

              1. 1

                good luck!

              2. 2

                Going to do some auditing of my personal infrastructure (thinking about splitting it up into smaller servers), setting up a proper VPN for my home server so I can expose my home devices more simply (so I can peek into things like my PVR setup) and then begin looking into rebuilding some stuff I had on a multi-cloud setup for Koype.

                Not expecting to finish any of this - just to start it.

                1. 2

                  good luck!

                2. 2

                  Continuing the play area/sandpit build I started during my week off. Hopefully get the rest of the fence panels/posts/gates installed.

                  1. 2
                    • Having a lot of fun with Perl (currently working on perlfetch)
                    • Preparing for GED studying (starts monday)
                    • Updating my website, it’s out-of-date projects wise, and I feel like there’s more optimizing I can do with it
                    1. 2

                      I started by making Unfeeder completely autonomous: no accounts, no manual actions, no external APIs for top stories. I continue working on Subreply for faster Django ORM queries.

                      1. 1

                        Curious about subreply, since I also make a forum discussion for my community. At first I make it very plain just ‘post’ and ‘comments’, with same reason. But after a while, community start asking for features like wysiwig, reply on reply, etc.. what will you do if similar things happen? Good luck BTW

                        1. 1

                          Think about solutions that you can build while meeting some of their expectations. Markdown instead of WYSIWYG, mentions instead of reply to reply, etc. In the end, just ask the community.

                      2. 1

                        Finish up my first ClojureScript project, License Wizard 2000 by publishing the source code and setting up hosting. I’m considering turning it into a tutorial on YouTube.

                        1. 1

                          congrats. Go for it, nothing bad happen if you make tutorial on youtube :)

                        2. 1

                          More work on https://littlefish.fish and some pixel art.

                          1. 2

                            looks fun!

                            1. 1

                              thanks 😄

                          2. 1

                            I’ll be picking at how to document (and, necessarily, documenting) a slice of behavior of common UNIX CLI programs.

                            Not quite like manpages–I’m not sure how to explain…

                            Before the pandemic settled in I started work on resholve, a tool that replaces bare commands in shell scripts with absolute paths. (My main motivation is to improve support for Shell projects in Nix, but the tool isn’t Nix-specific).

                            For the past 6+ months I’ve been on a longer yak-shave than I thought it’d take to pull together an ~MVP of something that can separate executables that might execute their args from those that can’t.

                            This is an essential stepping stone to support for recursive resolution (the extra-tricky problem of resolving commands that show up in the arguments to other commands).

                            The resulting project, binlore (plus a shell-based YARA callback scaffold I named yallback) actually came together in a fraction of this time, but I had to do a lot more refactoring than I anticipated to wring bugs out of recursive resolution on the resholve side.

                            I don’t think it’s possible to do this (fully identifying sub-execers) ~deterministically in code (at least not with current tooling), so for now it’s mostly about automating chunks of the problem space and filling the gaps with human knowledge.

                            Common commands are the obvious first targets. This means reading man/–help and source code to look for exec behavior, figure out whether it’s under user control or not, and document it. I’ve already built parsers for a number of common commands, but I’ve realized that figuring out how to document the decisions made (and how/why) will be an important step towards being able to maintain the decisions as the software evolves.

                            1. 1

                              Attending the second live event of The Late Brake Show in the UK - https://thelatebrakeshow.com/leicestershire. Really looking forward to it, and with Edd China in attendance as well. Taking my Golf GTI mk5 to shove in the Hot Hatches corner, intrigued to see what everyone else brings and what Jonny’s managed to organise. The sneak peaks of confirmed cars (and tank) coming is exciting already.

                              And on Sunday I’m back at the sailing club racing again. I thought all our racing slots had been booked up every week, turns out I’ve just missed an email saying no need to book slots to race anymore just turn up. </facepalm>

                              1. 1

                                Going out of town and visiting some friends. Maybe putting together some stools from IKEA on Sunday depending on when I get back

                                1. 1

                                  I would like to keep poking at a combo of Turbo with server-rendered React as the templating language.

                                  In reality we have a newborn in the house so I’ll be supporting my wife with whatever she needs. I also have trees I need to get planted and other chores to do. At least I will get outside a bit.

                                  1. 1

                                    I’m continuing to work an a (partial) reimplementation of LLVM’s IR APIs in Rust: https://github.com/woodruffw/mollusc

                                    I’ve been blogging about the different interesting bits of writing a bitcode parser from the ground up here: https://blog.yossarian.net/series#llvm-internals

                                    1. 1

                                      More Elixir and Phoenix! One of my personal goals for this year was to learn how to build web applications. I picked Elixir, Phoenix (with LiveView) and Tailwind for my “stack”. I’ve been following the http://pragmaticstudio.com course on LiveView which has been great.

                                      1. 1

                                        http://pragmaticstudio.com May I know what kind of personal project is? I love learning new technology, but sometimes not excited if build the same thing again (blog/crud/etc.. ) , especially when it doesn’t show the real intention of that particular technology.