agateau

You're welcome! :)

The game is actually open-source (https://github.com/agateau/pixelwheels/), so which side do I pick?

(author here)

I am sorry this came up sounding entitled: I don't expect Google policies to change on this subject, and since this is not business threatening to me I just decided to write something I thought would be snarky and hopefully amusing to read.

[Shameless plug] If all you need is the ability to manage a bunch of personal repositories hosted on your ssh server, you may want to try "reposetup", a minimalist, shell-based, repository manager: https://github.com/agateau/reposetup

I hit a similarly puzzling bug a few years ago in Gwenview (an image viewer) when a user reported it could not open some PNG files of a certain width.

I wrote about it here: https://agateau.com/2012/qt-image-decoders-stepping-on-each-...

Paris firefighters are part of the French Army [1], so they are used to being commanded.

[1]: https://en.wikipedia.org/wiki/Paris_Fire_Brigade

I don't have a strong opinion on monoliths vs microservices, as long as you don't go overboard with splitting things leftpad-style, but I believe splittings VCS repositories result in a huge waste of time when making cross-micro-services API changes.

On the other hand, the king of the hill of VCS these days, git on GitHub, does not make it easy to have this kind of setup:

- it is not possible (as far as I know) to checkout a subdir of a git repository hosted on GitHub), which is annoying for deployment

- it becomes difficult to only follow the PRs your team is interested in, since you can't tell GitHub to only notify you of changes in the subdirs you are interested in.

What are your experiences on this? when you split a monolith into microservices, do you also split the VCS repository into as many repositories?

Looks like a locale problem. `locale-gen en_US.UTF-8` should fix it.

I have heard this called early-returns. I like to write code this way too. Proponents of one-return-per-function probably write code in languages like C which does not have GC or RAII so having only one exit point makes it easy to ensure all resources allocated by the function have been released.

There are ways to do early returns in C without duplicating resource releasing code though, using gotos (it's one of the few cases where gotos make sense, IMHO). Code looks like this:

  int aFunctionWhichMightFail() {
      int result = FAIL;
      Foo* foo = allocateSomething();
      if (!someFunction(foo)) {
          goto fail;
      }
      moreWork(foo);
      result = SUCCESS;
  fail:
      releaseFoo(foo);
      return result;
  }

The Linux kernel makes heavy use of this.

He did.

I contributed a few minor fixes and got an email from David asking for permission to re-license.

I do self-host a few repositories as well, but I do not set up a separate user: I just create a git/ dir in the home dir of the account I want to host the repositories on and put the repositories there.

To simplify the initial setup, I created a handy shell script, reposetup [1]. It makes to create repositories, push to them and remind me their urls.

[1]: https://github.com/agateau/reposetup

I have been using it for the week, I like it!

Yes, we consider a task to be done when code has been reviewed and merged, so our estimates include review time.

Looks interesting, can it distinguish time spent in the browser, so one would know if time was spent on pull request #33 rather than on Twitter?

The thing is, we often have tasks estimated to last 2 or 3 hours. 10 or 20 minutes of review starts to be a significant duration in this case.

I disagree with the article for two reasons:

1. Many computer-illiterate users always click to switch from one input to another, so clicking on a select does not make them much slower

2. Many users are not aware that the text part of a radio button is actually clickable and will loose time precisely aiming at the round circle to select it. And they are unfortunately often right to aim at the circle because of the many loosely design pages which do not make the text part of a radio button clickable.

I wrote mup [1] to help with this: it is a markup previewer. It support multiple markup formats and for markdown multiple markdown implementations: pandoc, commonmark, kramdown, python-markdown and also previewing using GitHub API (slow but the most reliable for README.md editing)

[1]: https://github.com/agateau/mup

> Once there's a critical mass of cars with cameras, cars could communicate road conditions automatically.

I would be frightened to trust the data coming from a random car in front of me. Inferring road condition from another car behavior sounds reasonable, using data supplied from it, not so much.

I suspect (haven't checked!) this is actually Ubuntu kernel not allowing mbox to do what it tries to do. See https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening

While the trademark feels abusive, gamezebo really did not pick the best example: how can one name his game "All Candy Casino Slots – Jewel Craze Connect: Big Blast Mania Land" and then pretend he did not try to take advantage of the name of famous games?

Most likely because KHTML license was (still is) LGPL, which allows the creation of proprietary products with it (Safari) but requires all source code changes to be published.

Had KHTML been licensed under a BSD or MIT license, the browser world could potentially be very different from what it currently is.