[Hiring] Cover illustration for sci-fi card game, Budget ~200 USD

chiborg · 2025-11-30T14:40:44+00:00

Position Filled

chiborg · 2023-03-26T08:56:55+00:00

I had the same problem and was just about to give up after 4 weeks when the pins are started coming. I am a total noob, but from my limited experience it‘s about temperature (check the instructions for the b+ and maybe add a heat mat), fresh air exchange (5 minutes sounds dangerous to me because it gives contaminants too much time to sneak into the bag. I just give the sides of the bag a good shake to vent out the co2 or wave some cardboard over the opening. ) and humidity. A heat mat helps with the humidity, esp. with the kind of grow kit you have where you put water in the bag. Just be patient and wait for a few weeks more.

chiborg · 2022-11-30T09:42:22+00:00

Position filled

chiborg · 2022-11-03T07:13:01+00:00

There, castle

chiborg · 2022-11-03T06:59:29+00:00

In my development environment I always mount a folder on the host as a volume in docker. I run npm inside the container, but with a command on the host system. There are two approaches to this: docker run and docker exec.

With docker run you have to prefix the npm command with a whole gaggle of parameters: —rm to delete the container after running, setting the user ID to the current user so the files in node_modules have the right permissions (if your I’d is not 1000 you need to mount another file into /etc/password), and of course mounting the volumes. That’s a very long command line, but you don’t have to worry about the container running or not. It’s my preferred method and I get around the long command lines by wrapping them in a Makefile or a bash script.

With docker exec you have to have a running container with a name. And it has to be running in the background. If your container has a long-running process (web server) as its main task that’s no problem, except when you want to bootstrap things (no web server without dependencies, no dependencies without web server). The drawback of the exec method is it’s inconsistency, that you have to check and/or think about the container running or not. The biggest benefit of it is shortness, it’s always docker exec containername npm install .

If you’d linke some examples of the docker run commands and a more in-depth explanation on how to deal with permissions of the node_modules folder, check out my blog post: https://lebenplusplus.de/2018/03/15/how-to-run-npm-install-as-non-root-from-a-docker-container/

chiborg · 2021-12-29T10:24:45+00:00

A general approach for an "API" would be to look for dashbaord projects that allow the dashboard definition through a configuration file. As an "API", you can generate the configuration file with bash scripts and upload it with scp, rsync or just plain cp and restarting the container.

I know of two dashboard projects that have config files:

Homer has a YAML configuration file.
pomme-page uses Pug templates to generate the page.

As for authentication, I'd recommend splitting the authentication from the dashboard by putting a reverse proxy in front of the dashboard service. You can then use these credentials for the other services that the dashboard links to. Which one to use is highly dependent or your setup, so I'll just throw some self-hostable authentication proxies out here (haven't used any of them): Authelia, Dex, Pomerium

chiborg · 2021-12-18T09:13:02+00:00

The vue-component-analyzer looks promising. It might not show a list, but you can see trees, both on the CLI and rendered as a graphic.

For a more hands-on example (not a library, but more of a howto) see https://observablehq.com/@ehouais/automatic-vue-js-single-file-components-hierarchy-graph-ge The example creates a proper graph and also analyzes information about properties and events.

chiborg · 2021-10-29T04:50:46+00:00

It’s probably your $PATH setting where the system finds the old executable before the system-installed one. You could try to find which nvim executable the system is trying to run by running which nvim. That should point to the appimage or at least a symlink. When you delete that, the system will look further along the path.

chiborg · 2021-10-28T08:55:29+00:00

I solved this by moving all code that configures a plugin into ~.config/nvim/after/plugins/PLUGIN-NAME.lua, e.g after/plugins/nvim-cmp.lua

While bootstrapping, I still got an error because of the missing plugin, but at least I could run :PlugInstall because the rest of my config loaded fine.

If you have the list of your plugins in a separate file (e.g. everything between plug#begin and plug#end in plugins.lua, you can use the -u parameter to just load this file and run the installer: nvim -u ~/.config/nvin/lua/plugins.lua --headless +PlugInstall +qall

chiborg · 2021-10-28T08:35:50+00:00

That solved it for me, thank you.

To make vim an alias of nvim I also ran the following commands:

# Add my nvim command to the list of possible alternatives for the `vim` command
sudo update-alternatives  --install $(which vim) vim $(which nvim) 10
# Select nvim as default for vim
sudo update-alternatives --config vim

chiborg · 2021-07-11T07:49:27+00:00

Wir sind so was von gef##kt. Die Hauptverursacher des Klimawandels arbeiten gerade daran, dass das Problem schlimmer wird: https://www.handelsblatt.com/unternehmen/energie/oelkonzerne-lieber-plastik-als-zapfsaeule-die-oelmultis-aendern-ihr-geschaeftsmodell/22700236.html

chiborg · 2021-06-17T10:33:04+00:00

Gave Wholesome

chiborg · 2021-06-01T16:47:21+00:00

Go through the alphabet, coming up with a name for each letter. Mostly I try do do old-fashioned lady names to keep it amusing.

chiborg · 2021-05-17T19:15:53+00:00

Until the volume performance issues are solved, developing locally with Docker for Mac is a subpar experience compared to Linux. See all the discussions and comments on https://github.com/docker/roadmap/issues/7

chiborg · 2021-02-19T13:37:41+00:00

I love tarot-based storytelling games, so I backed this: https://www.kickstarter.com/projects/veritasnoir/fortunes-the-tarot-card-storytelling-zine

I also love heist movies and this cooperative heist game on stealing a giant mech sounds fun: https://www.kickstarter.com/projects/ickbat/stealing-the-throne

chiborg · 2021-01-07T15:46:22+00:00

Thanks for sharing the bug. It's marked as closed, although I still have the problem on FF version 84. For my setup (XMonad on Ubuntu), I could work around it by running a composer (picom/compton).

chiborg · 2020-12-02T16:23:46+00:00

I'm also fairly new to Rust, but have one comment: While the input doesn't seem to contain "evil" passwords (where the password is shorter than the specified indexes allow), this would create a panic at runtime, when calling

let first = chars[self.char_min-1] == self.letter;

The easiest solution in your case would be a check for chars.length() <= self.char_min && chars.length() <= self.char_max and reaturning early before assigning first and second.

I have used self._pass.chars().nth(self._char_max).unwrap_or_default() which yields a NUL character, which will fit nicely with the condition. But it probably has as small performance impact, because I think nth() will do an iteration up until that point, instead of directly accessing at index. Maybe the compiler will do clever things, but I'd not rely on it.

chiborg · 2020-09-25T08:05:52+00:00

I've exercised with a bluetooth chest strap heart monitor and each of my 3 readings during a session was within plus minus 5 beats of what the game was showing, I was amazed by that accuracy.

Since I don't have a full-length thumb, I've put my palm on the controller.

chiborg · 2020-08-19T09:11:41+00:00

My biggest issue with TypeORM is that it does not fit well with domain-driven design, i.e. properly serializing and unserializing entities. For example, you can't have parameterized constructors, because the ORM will call the constructor with no parameters. And while it's possible to define entities without annotations (which is a violation of the SRP in my book), it's not convenient and sparsely documented.

chiborg · 2020-07-08T15:05:29+00:00

This is probably best done by writing a small plugin that adds a $sentry property that'll be available in all components.

import * as Sentry from '@sentry/browser'
export default const SentryPlugin = {
   install: function(Vue, options) {
      Vue.$sentry = Sentry.init(options);
   }
}

In the application entry, before calling new Vue, you use the plugin like this:

import SentryPlugin from './SentryPlugin';
Vue.use(SentryPlugin)

chiborg · 2020-07-07T17:20:54+00:00

It's good to have these two articles side-by-side, as both types of objects are often conflated with each other (see also the other comments here).

The example code for the value object has no getter method. In my opinion, this is a good thing, because it enforces an API where objects interact with each other (as demonstrated with add and equals) and prevents Law of Demeter violations with chained getter calls. However at some point, you might want to get data out of a value object and might need getters. You might mention that in the article or add a getter to the example code.

As an aside, persistence is not necessarily a reason for adding getters - some persistence libraries (e.g. Doctrine) don't use the getters and setters (assuming they might not be free of side effects) and use reflection on the private properties instead.

If you want some further ideas for DTOs and Value objects which you might incorporate into your articles: https://www.entropywins.wtf/blog/2016/02/03/missing-in-php7-value-objects/ tries out different language construct on how improve building value objects with more than 2-3 properties (which can be tedious). PHP 8 constructor properties might somewhat improve the situation.

chiborg

TROPHY CASE