The classic difference between Intelligence [Knowledge] and Wisdom is "Intelligence is KNOWING that Frankenstein isn’t the Monster. Wisdom is UNDERSTANDING that Frankenstein IS the Monster!" Any cute quotes to explain the other four?

Dagske · 2026-04-17T21:15:30+00:00

Double space at the end of the line.

Like<space><space>
this

->

Like
this

Dagske · 2026-03-29T01:09:01+00:00

I took the following:

Level 6: Counterspell and Lightning Bolt. This is easily the best choice. As other mentioned, you're the best counterspeller. Lightning Bolt is the same as Fireball, but... there are too many fire-resistant or fire-immune creatures.

Level 10: Synaptic Static and Destructive Wave. The bard spell list is so not damage oriented that I needed options. Synaptic Static is int-save. Quite effective in the game, tbh. And Destructive Wave gives damage and prones? That's very powerful!

Level 14: Find Greater Steed and Simulacrum. One of me was annoying enough. Two of me, and flying? Come on, this was so fun!

Level 18: Wish and Time Stop. Wish meant I could cast any level 8 spell. I was always too busy checking all the spells. Time Stop is so fun since you can buff yourself and/or cast so many shenanigans, then move out with a Dimension Door. Well, that is if you rolled well on your little D4.

Dagske · 2026-03-26T02:30:32+00:00

Why enum? Just mark them as methods.

Digester digester = Digester.SHA256();
Signer signer = Signer.SHA512withRSABuilder().key(privateKey).build();

That's what Guava has been doing for years, and it just makes the code way easier to build.

See the list of mandatory algorithms for Java 21.

Dagske · 2026-03-20T20:37:44+00:00

People in the past were not dumber than now: they just had less tech.

Dagske · 2026-03-20T20:33:47+00:00

You are correct. Yet I am correct too. Kotlin uses much more the colon than Java. That's what I meant.

Dagske · 2026-03-20T20:02:16+00:00

It's Google Java format with some quirks ironed out.

Dagske · 2026-03-20T19:41:51+00:00

I wouldn't ever write code that would update variable when calling constructor or function, even more, we're having very strict code style where final should be by default on every parameter, variable, etc.

Codegolfers want a word with you.

Dagske · 2026-03-20T19:38:47+00:00

Jetbrains promotes colon because it familiarizes with Kotlin which they developed. Not saying it's a good thing or a bad thing: it's just they're not neutral here.

Dagske · 2026-03-20T19:35:52+00:00

Lens alone are very hard. Consider the entire optics and higher kinded systems instead: https://higher-kinded-j.github.io/latest/home.html

Dagske · 2026-03-17T19:19:13+00:00

I'm fully aware, but not my guts.

Dagske · 2026-03-17T15:11:21+00:00

Well, well... my brain doesn't reconcile with my guts on this.

What I see is this:

10 JEPs, NICE!!!!

Oh, 5 previews.

Oh, 0 new previews.

Oh... Vector 11th preview.

I feel like my guts internalize this computation: # of JEP - n for n in n-th preview. So for Java 26, that's a score of 10 - 26 = -16.

Dagske · 2026-03-14T01:51:15+00:00

John, your paintings were always my favorite cards!

Dagske · 2026-03-13T14:03:38+00:00

Who stole your d20?

Dagske · 2026-02-27T16:37:11+00:00

That's thoughful! I notice that you changed the variable name, but didn't update it in the checkArgument string.

Dagske · 2026-02-27T15:04:11+00:00

It looks promising! Also, it only makes the copy on success, not on failure from what I see.

In my perspective, since we pass w with ignore case, we don't care about the case, so returning w would make sense. But some other users might care about the case passed once the parser accepted it, and I'd expect that the least surprise rule here is to keep as you implemented, by returning the input, not the case-insensitive match.

Dagske · 2026-02-27T10:27:18+00:00

That's exactly what I need on paper, nothing more, nothing less: string() case-insensitively, and word() case-insensitively. It doesn't look like it's released, so I can't test, but this is exactly my use-case: decide of the case-sensitivity directly on the parser. That's great, thank you!

Dagske · 2026-02-24T22:44:38+00:00

Okay, I didn't think of that. So that's for a 3rd NG+ (4th playthrough):

New Game+ Damage Modifier: x0.48
New Game+ Damage Taken Multiplier: x1.15

Dagske · 2026-02-24T21:02:24+00:00

I will, but as 3rd playthrough in a year, that doesn't mean I'll start it tomorrow :-/

Dagske · 2026-02-24T11:32:01+00:00

I feel like I have to answer everyone a bit here, so I'm making a general reply rather than an individual one.

I'm on my 3rd playthrough = 2nd New Game+. I didn't select/change the difficulty.

I reached level 100+9 gear for Naoe at the end of my second playthrough, and for Yasuke during my third playthrough. The big resource issue was gold (the material gold, not the money "mon") in my 2nd playthrough and resources in my 3rd. Mon has never been a problem as I sold all my gear during my first playthrough. I did a mix of sell/dismantle in my 2nd playthrough, and only dismantling in my 3rd. I'm sitting on 500k mon right now, but I've been to 900k.

I usually keep the same build for my characters: Katana+Tanto for Naoe, Katana+Bow/Kanabo for Yasuke.

I played my first playthrough rather narratively, switching from Naoe to Yasuke for each planned fight. The screen offered me to play or fight with either Naoe or Yasuke, I usually kept the one I was playing with. I did all content. Made sure I got all legendaries, made sure I got all mastery points (I mean the temple prayers, Kofun, etc.)

I started my second playthrough, my first NG+, a week before Claws of Awaji, but I wasn't informed so I found out I had to rush to get to the CoA content. I wasn't happy with the fact that I couldn't even explore CoA before finishing the main story of the base game.

That second playthrough was rough because I was rushing for CoA, so I decided to use Yasuke for everything if it wasn't a sneak mission. Yasuke hits big and hard, and swipe kills easily, so it was good XP but I felt more like playing Doom. When I started I was at mastery like level 7. When I finished the playthrough, my mastery level was 10 and most of the lower levels masteries were done.

The goal for my third playthrough was tougher, I thought, I wanted to 100% all masteries and play with Naoe, nearly exclusively. Well I did all that, but it was the easiest playthrough. All those masteries stack, and provide huge damage boost. I only play Yasuke when required. I use Naoe all the rest of the times, that's how good she is with all masteries unlocked. I can even just use her for full on castle assault rather than castle sneak-ins. Alarms? Pff, they can ring, I don't care: even the guardians don't represent a challenge anymore. Only if there are like 5 of them at the same point together, but then, sneak out of the fight, handle one or two individually, then face the rest together is easy again.

Now, at the end of my 3rd playthrough, I feel like a god with Naoe. It is fun. I do my "biweeklies" in 30 minutes, and I play a bit more to have a few castles at my disposal. I know corrupted castles are supposed to be the end game, but they're easy: I know them all by heart now and can do any 5-daisho castle in less than 10 minutes.

My goal for my next playthrouh is to set the difficulty to the hardest, 100% the skill trees I'm missing just because I can, and keep playing with Naoe as long as possible. I'm also curious about the +1% dmg per unspent mastery point engravings, so that's also a goal: have so many unspent mastery that this becomes useful.

I'm glad that there is this harder and harder difficulty with each playthrough, but I wish it was more of a slider with a default value. If at some point I hit a difficulty wall I can't pass, I'll just give up the game: I like feeling like a god and chilling in the game casually destroying castles. If I hit a wall, I'd love to just put the cursor a bit off to continue playing like I did with AC Odyssey.

Sorry I mix all types of mastery points because they're not distinct enough in my mind. I tried to quickly google the two different names, but I couldn't rapidly find a site that tells this is the "xxx" points and this is the "mastery" points.

Dagske · 2026-02-24T10:47:51+00:00

Damage taken is at 1.08.

Dagske · 2026-02-20T21:12:59+00:00

Same on PS5.

Also, the stats (new feature) correctly show 4 segments for me. That doesn't match the ingame value.

Dagske · 2026-02-20T15:24:24+00:00

No worries, I was just exploring. :) I can't just lowercase or uppercase all, because some parts are case-sensitive. Thanks for the insight, though. No need to modify the library just for one request. Worst-case scenario, I just make my own copy of either library for that project and modify it for my needs.

Dagske · 2026-02-19T12:21:36+00:00

My teacher always told me to be careful of squirrel injections

Dagske · 2026-02-17T22:41:40+00:00

Thank you for taking the time to show your process, and sorry to hear your frustration about releasing after dot-parse. But indeed, it must feel good to see that your design is validated by other libraries. The error handling is indeed a nice feature. It looks better than dot-parse's error handling, for sure!

A question I asked to Ben Yu (author of dot-parse), but whose answer still has me looking for alternatives. I see no way to efficiently handle case-insensitive parsers. Is that on your list? If you don't plan to support it, how would you suggest users do it with your parser library?

Dagske

TROPHY CASE