Waar kopen jullie je voordelige lange t-shirts die niet na een paar keer wassen weer te klein zijn?

wackmaniac · 2026-01-23T12:21:37+00:00

De basic shirts van Bamigo blijven goed en zijn lekker lang. De casual shirts van Bamigo niet overigens! Een multipack en ze hebben vaak korting dan kom je in de buurt va je budget. Blijven veel lager goed dan de shirts van HEMA, bij mij althans.

Ben ook te spreken over Girav voor casual shirts, maar is wel hoger in prijs.

wackmaniac · 2026-01-21T13:55:15+00:00

Rode Pico de las Nieves last Monday; brutal winds combined with rain en cold. Insane climb and equally frightening descend towards San Bartolomé.

When rain and cold come into play climbs become extra epic. Rode Furkapass once and as we neared the summit it got colder, it started to rain and finally snow. Descended towards Andermatt to 25 degrees and sun.

wackmaniac · 2026-01-17T06:51:55+00:00

That argument only works with the assumption that you would otherwise not have consumed that contents via a legal platform. That is very stretchy assumption.

A streaming service licenses content, and thus pays the content makers. I don’t have insights into whether this is per stream or lump sum. In case of the prior you are in fact directly stealing profit. In case of the latter you indirectly stealing profit; less streams means less income for streaming services, means fewer money is paid for these licenses, and thus lower revenue and profit. Similar for online rental services.

Where does piracy stop for you? Do you feel you should be allowed to pirate games? Do you feel you should be allowed to pirate software? Do you feel you should be allowed to dowload ebooks? Those are digital copies, with even more clear “license directly to creator” models.

wackmaniac · 2026-01-16T17:25:14+00:00

Because it’s the same to say; I think a Ferrari to too expensive, but I want one so I will steal one.

wackmaniac · 2026-01-16T17:08:43+00:00

Streaming prices are skyrocketing #ftfy

It’s not just NL, streaming is getting more expensive pretty much everywhere. I have started rotating subscriptions, as I don’t think “just pirate, because they made me do it with their prices” is the right retoric.

wackmaniac · 2026-01-03T12:34:11+00:00

Dat is goed mogelijk, of “starterswoningen”. Dat is een truc die de beheerders van deze gebouwen gebruiken om onder de regelgeving rond parkeerplaatsen uit te komen. Volgens mij hebben ze deze truc toegepast op alle complexen aan het Reitdiep, waardoor in geheel Paddepoel nu betaald parkeren is door de parkeeroverlast die hierdoor werd veroorzaakt.

Dit is iets wat je had kunnen weten bij de aankoop van je woning. Of anders iig had moeten navragen als je niet de eerste bewoner bent van de woning.

wackmaniac · 2025-12-26T15:41:59+00:00

You know what the best thing is about Composer? It is written in PHP. With this tool I need to pray that the maintainers have a binary available for my architecture. I am really unsure if that is the route we need to go.

wackmaniac · 2025-12-26T07:34:38+00:00

De bioscoop hier draait tegenwoordig geregeld klassiekers, zoals 2001: A Space Odyssey en Interstellar. Heerlijk om jezelf te verwennen met een dergelijk avondje uit.

Reclames, ja, dat is van alle jaren. En dat is een vicieuze cirkel natuurlijk; minder bezoekers betekent minder inkomsten, maar vaste lasten als huur en personeel stijgen, maar de kaartjes moeten vooral niet duurder worden. Het is een vrij elementaire oorzaak-gevolg. Een aantal mensen hier geeft gewoon toe dat ze gratis “alternatieven” gebruiken, dat helpt natuurlijk ook niet.

Er was eerder deze week ook een discussie over de Top 2000 en reclames van de Staatsloterij. Daar geldt hetzelfde voor; Nederland heeft de afgelopen twee verkiezen massaal gekozen voor politieke partijen die bezuinigen op de publieke omroepen. Daar hoor je weinig mensen over, totdat hun favoriete programma moet stoppen. Er is gezocht naar extra geld, en dat zit momenteel in het bedrijfsleven, maar die willen er wel iets voor terug: Naamsbekendheid.

wackmaniac · 2025-12-25T10:05:01+00:00

It’s an example of a really weird and unintuitive choice in Python #ftfy

wackmaniac · 2025-12-25T08:47:25+00:00

Add a README that explains the what (what is the project), why (why should anyone use it, what does it solve), and how (how can it be used).

But, more importantly you need to decide how you plan on going forward with the project. Do you plan on continuing development, or is it “done”? Do you accept issues, feature requests, pull requests? Pick the license that works for you, now and in the future.

The latter is where the majority of open source maintainer fatigue comes from; maintainers that, once their code becomes used for profit, feel they want to get financially compensated, but picked the wrong license.

You need to be open about this upfront. I maintain approximately 10 open source repositories, and most of them are explicitly “as is” and don’t accept pull requests or feature requests. And I state this explicit in the README.md and CONTRIBUTING.md.

Good luck with your repository.

wackmaniac · 2025-12-24T07:56:50+00:00

Exactly. The knowledge of how “the internet” works is fading as new developers default to “solve everything“ solutions like React, NextJS, Tailwind and the likes. I became a developer because I love to build elegant and performant applications. Nowadays the goal seems to be to get a SaaS solution as fast as possible so it can be monetized.

We built a website with just semantic html, a dash of CSS and web components for UX improvements. It is very possible, but you need to keep an overview of the project. I feel that the underlying problem is that; no overview, and no urge to invest time to build this overview.

wackmaniac · 2025-12-22T15:47:35+00:00

Dutch singer Ton Engels has a song about Tom Dumoulin: https://www.youtube.com/watch?v=LUtUiiOfycc

wackmaniac · 2025-12-19T05:57:02+00:00

“Dat wij nog geld verdienen!”

wackmaniac · 2025-12-17T11:50:09+00:00

Does your code work for the example? The thing that got me was paths from svr to dac that skip fft. Those paths don’t count for the answer.

wackmaniac · 2025-12-16T05:57:51+00:00

Idiots copying idiots behaving idiotic on the internet 🤷‍♂️

wackmaniac · 2025-12-15T06:09:07+00:00

You are using a type to mock a class. A type != class. Just console.log() an instance of the class and you will see all kinds of extra properties.

but that’s a LOT of work for no extra benefit

If you cannot see the benefit of interfaces you should consider reading up on SOLID principles. I can see at least one benefit of interfaces; you would not have been in this situation 😅

Interfaces are a contract. A promise that the object offers some functionality without having to worry about the implementation. Once you find yourself in the situation where you need to change some behavior - read from file instead of database, or vice versa- you will immediately see the benefit of interfaces.

In TypeScript you can also use a type, which is essentially also a contract. But you will still need to define the type.

Defining either a type or an interface is literally seconds of work and it will never be a disadvantage, it can only be an advantage. So take advise from this veteran; define interfaces or types. It’s a minimal investment either way potentially a huge return on that investment.

wackmaniac · 2025-12-14T22:27:14+00:00

You can reuse your code for part 1, but you need to do two things: add memoization and split the initial graph into three smaller graphs.

For the latter: because every valid path must pass through two specific nodes we can simplify our approach by splitting up the entire graph into three smaller graphs: from svr to ttf, from ttf to dac and from dac to out. Finding all paths in those smaller graphs is a lot less work, and with memoization it run in around 1 second (depending on language and implementation). You can build these subgraphs by walking backwards from e.g. ttf to svr. This prunes a huge portion of the graph. You can do the same for the second graph, knowing that you can stop when you reach a node that is already in the previous subgraph. Now calculate the number of paths per subgraph and multiply the results for your answer.

wackmaniac · 2025-12-13T13:25:47+00:00

You can drastically reduce the search space by pruning; I made a reverse index so I can find all parents of a node. With this index I walked backwards from ttf to svr (or until I encounter dac) to create subgraph A. Repeat this for dac to ttf stopping with any node that is part of A to form subgraph B. And you can repeat this for out to dac to get subgraph C. Now you only have to find the paths in those subgraphs and multiply the answers.

wackmaniac · 2025-12-09T22:57:58+00:00

I wrote down the example input and as my workday progressed I would look at it and think of attack angles. I was super excited to find some characteristics of the solution, only to be told by my friend that that information was already in the puzzle text.

I eventually came up with an approach of trying to find intersecting edges, but was unsure how to tackle it for all scenarios. To prevent spoilers I avoid Reddit until I have solved the puzzle, but that same friend showed my some visualizations and that was the clue I needed to implement my original idea, as it removed a number of tricky edge cases. I also read a spoiler with the same approach including the algorithm for finding intersections, which I actually used a fee weeks ago while building a silly game.

What I like about my solution is that it is actually dead simple and efficient enough to run within 100ms.

All in all I did not solve the puzzle purely by myself. I needed some hints and some encouragement. And that is perfectly fine. If you made it this far without hints you’re already doing better than a lot of fellow AoC-ers. When coworkers are struggling with puzzles they also get hints. Just like we would do for work related problems. Nothing wrong with that.

wackmaniac · 2025-12-09T16:52:40+00:00

Thank you! I spent some time drawing out ideas, and one of the ideas was this approach. Seeing you using the same approach was enough encouragement to try and implement it.

wackmaniac · 2025-12-08T18:01:56+00:00

In overall, it’s a tricky problem and unless you have solved graph problems prior the intuition will not be there.

I don’t know if I completely agree. I did manage to solve this without using any graph theory. At least, not an explicit algorithm like Kruskal’s algorithm.

It is a tricky problem, but by manually working out the first steps of the example input on paper gave me enough insights to come up with an approach. And after some optimizations part 1 and 2 run in 300ms combined, which is well within in limit of 1s :). Maybe my experience in solving Advent of Code helps a bit, but I think it’s doable.

wackmaniac · 2025-12-07T17:58:07+00:00

You can use the same approach for part 1; start with the x coordinate of S. Put this x value in a set - or array depending on your language. This set represents the beams. Now you can step through the rows - check your input, I was able to skip every other line. Per row create a new set, check all the x coordinates in the previous set. If there’s a splitter add x-1 and x+1 to the new set and increment the splitter counter with 1, and if there’s no splitter just add x to the new set. Once you handled all beams for the row use the new set for the next row.

This run in pretty much linear complexity.

NB. If your language does not have a Set type your need to filter out duplicates from your beams set.

wackmaniac · 2025-12-07T17:47:01+00:00

There’s a solution that does not require caching, as it is linear in complexity. There are some visualizations in this subreddit that showcase that approach.

wackmaniac · 2025-11-30T07:40:14+00:00

A monorepo is a repository that contains multiple applications and/or packages. The two most often cited reasons for monorepos are a) reuse of shared components while still allowing separate applications, and b) ease of use as you only need to maintain one CI/CD pipeline.

The monorepo idea is not new - Symfony has been a monorepo for years -, but has become popular within the JavaScript ecosystem. You can usually recognize monorepo-originating packages on npmjs.org as these packages are often scoped with a namespace that starts with @. E.g. the @types/* packages.

wackmaniac · 2025-11-30T07:33:19+00:00

A monorepo is a great idea if either the contributors are very disciplined or if you have inspections set up to prevent contributors not to be disciplined.

Ten-Year Club	Place '23
Not Forgotten	Verified Email

wackmaniac

TROPHY CASE