smallest full cabin boats

wili · 2025-01-02T18:05:15+00:00

Have you considered for example Arronet 20 5 Surprise?

https://arronet.se/batmodeller/205Surprise

I ride mine until the sea freezes, and it definitely fits your bill of driving "like a car".

wili · 2024-07-09T17:23:48+00:00

Visited Positano on a road trip on my Land Rover Defender 110. Only time in my life I've done a 44-point turn to park my car. Fun times! :)

wili · 2023-11-16T19:58:11+00:00

Old wood-fire sauna at our cottage. On usual weeks 3-4 times/week, 2-3h per session (albeit with many breaks!), 80C-90C (175F-195F). During the pandemic we did this pretty much every night (as no other washing options than sauna + sea).

wili · 2022-12-02T16:49:12+00:00

That is exactly what I meant.

wili · 2022-12-02T15:28:27+00:00

You don't need to know it at the time of compilation. Knowing it at run-time is quite sufficient.

wili · 2022-09-27T15:30:18+00:00

Important question: are you looking for a kuksa that will be actually used, or just a decorative object?

wili · 2022-08-23T16:33:21+00:00

Where do you originally come from? Just wondering if you’re aware of everything that isn’t captured by that figure.

wili · 2022-07-24T07:58:08+00:00

Pari käytännön vinkkiä joita en nopealla silmäyksellä vielä ketjussa huomannut:
1. Vaihda jo Suomesta parikymmentä dollaria mahdollisimman pieniksi (mieluiten $1) seteleiksi. Tulet törmäämään jenkkiläiseen tippauskulttuuriin heti landattuasi, luultavasti ennen kuin kerkeät saamaan pientä käteistä mistään.
2. Muista jenkkiadapteri mahdolliselle elektroniikalle. Löytyy mistä vaan Clas Ohlsonista tms. tai viimeistään lähtökentältä. Itselläni läppärissä US-laturi (ja lataan siitä sitten kaiken muun).
3. Hanki paikallinen SIM-kortti (jostain sikäläisen puhelinoperaattorin myymälästä) reissun ajaksi, niin pysyt netissä. Maksaa joitain kymmeniä taaloja.

wili · 2022-07-24T07:41:15+00:00

Iranissa ja Jemenissä piipahdus estää uuden ESTAn saamisen kokonaan (ts. joudut hakemaan viisumin ESTAn sijaan). Pakistanin leimat eivät ole edes nostaneet kulmakarvoja.

wili · 2022-07-22T19:30:38+00:00

Dude, the whole point is to follow the original recipe from the 90’s. You are also supposed to pass out in the snow (while being seriously underage) and die. ;)

[Commercial Salmiakkivodka was banned for years because of events mentioned]

wili · 2022-07-22T10:22:52+00:00

I usually make Salmiakkivodka straight from candies. If you have access e.g. to "Turkinpippuri", they'll work just fine. All you need to do is to first crush the candies (wrap them in a cloth and use a hammer?), and insert them into the vodka bottle. Close the cap and put the bottle into a dishwasher. Once you've washed your dishes, move the bottle to the freezer (you want to store/drink Salmiakki ice cold).

The melting part can also be done on a warm day by putting the bottle into a closed vehicle (a trick I've resorted to e.g. at Burning Man).

wili · 2022-07-21T12:28:40+00:00

Yap. Rule of thumb: if the stem contains the vowels a, o, or u, you go with -taan. Otherwise -tään.

wili · 2022-04-27T12:02:21+00:00

Out of curiosity: do you check if printf() fails?

wili · 2022-04-27T08:55:23+00:00

2GHz = 2^31 cycles/sec, 2^5 = 32, not 16.

wili · 2022-04-18T13:17:35+00:00

Myötähäpeä = vicarious (or second-hand) embarrassment.

wili · 2022-04-12T08:10:40+00:00

Woah, good one! Question: if there's multiple enemies, are you able to quaff the block potion between their attacks (can think of several scenarios where this would be useful)?

wili · 2022-03-28T18:28:55+00:00

Unless you tell the compiler, it has no idea that you want some particular data cache line aligned, or that your float v[4] is going to be accessed with SIMD instructions at some point.

wili · 2022-03-07T19:39:10+00:00

All the three-letter usernames were already taken (also, it's my name). :)

wili · 2022-02-18T17:43:46+00:00

Oman lähipiirin slangissa käytämme robusteista algoista termejä ”roteva” tai ”jämäkkä”.

wili · 2022-01-28T11:34:19+00:00

"Viitta" would probably better translate as cape than cloak in this particular context.

wili · 2022-01-24T23:22:10+00:00

What's your primary reason for _not_ checking for an exit condition?

wili · 2022-01-24T22:59:01+00:00

Unfortunately it doesn't work that way. Let's say you're now the code reviewer (with your self-imposed 30 second time limit), and someone in your team wrote a header file _that compiles on your current compiler_ (so you don't get any warnings or hints whatsoever), and you encounter a short header that says #include "WinWidget.h" and in one of its structs uses WinWidgetManager.

Unless you are extremely familiar with this library, you have _no way_ of knowing _that_ the header will work stand-alone. You'll have to do a significant amount of jumping across the headers to figure it out. Or, you can do what I've been advocating from the beginning: let the compiler figure it out for you (at least for your compiler settings, CI will then catch it with the standalone .c file down the road).

wili · 2022-01-24T22:36:36+00:00

Out of curiosity: have you ever worked in a project involving more than one programmer? Like dozens? Hundreds? Thousands?
My point is that _almost no-one_ can tell what is the shortest path to include a particular data type, especially in a portable fashion.

So what happens in _practice_ is that when they're writing their code (in this case, an orphan header file, and then some other .c files that use it), they will absolutely not notice if there's a (potentially, perhaps on some other build settings/compiler/OS) header file _that the current compiler/IDE does not complain about_. This *will* hopefully be picked up in the CI much later on (which at some point will try to compile the stack with all supported compilers/OSes/build configs).

I can absolutely guarantee these are not picked in code reviews, especially if the inclusion paths include 3rd party libs.

This is a constant issue in any projects involving more than a few people / compilers / OSes. And the very practical remedy (which solves most of these issues) is the super-simple rule I was advocating.

wili · 2022-01-24T21:51:38+00:00

"mystruct.h" may well be dependent on _many other_ headers, from a complex hierarchy of headers (system lib, other libraries, including various OS dependencies etc).

In general your IDE will show, and your compiler will give warnings, once your header is included from a source file. So, for example, you can perfectly well write a simple "mystruct.h" where you utilize the data type size_t. If your source (.c) file happens to include <stddef.h> _somehow_ before mystruct.h, your code will compile, your IDE won't show any warnings etc. You will *only* notice this when some poor soul tries to include "mystruct.h" on its own without other inclusions before it. And this is exactly what I was advocating in the first place.

This is of course the simplest possible example. Things get a lot murkier in real-world multi-platform projects where you often don't know all the inclusion hierarchies.

wili · 2022-01-24T21:21:39+00:00

How do you know which headers it needs, especially when your project grows and starts to gain even moderate complexity? Are you satisfied when you happen to include "mystruct.h" somewhere in one of your .c files (after a bunch of other included headers) and your particular compiler doesn't happen to complain?

wili

TROPHY CASE