oweiler

Or use tests and/or a debugger. Which gives you all the listed benefits w/o an additional dependency.

So like Testcontainers Cloud?

That game felt like a graphics demo though. Almost unplayable.

https://github.com/helpermethod/pk/blob/main/pk

I have a tiny shell function to kill whatever is listening on that port

His first "what" example actually explains "why" clear is called two times. The code perfectly captures the "what".

You can also check in an .sdkmanrc into each respective project which defines the required Java version.

Then SDKMAN! will perform the switch automatically when you enter the directory.

https://sdkman.io/usage/#env-command

It just gets rid of the boilerplate. Never had a problem with ctor injection in Spring.

Use the builtin Result class and runCatching/fold and be done with it. Yes, it has shortcomings but works well enough in practice.

This is honestly the main reason I prefer Playwright to Cypress. Playwright leans heavily into using POs, while for some reason Cypress doesn't.

So in almost every project the Cypress tests are a procedural mess, while the Playwright tests are mostly well structured.

I know that Cypress has other patterns for dealing with this but they never seem to get applied.

I use Starship without any customizations and its good enough for my every day use.

Reminds me of a game I've played on C64 AS a kid.

Bash has no standard library. It has builtins, and commands. And commands are just external tools.

I have read almost the same thing 5yrs ago. And 5yrs before that. And so on.

Yet. It's a drop-in replacement, and both faster and cheaper.

Can such a company actually be profitable? The market seems tiny.

When I started running I had horrible cramps and the mg made them much less severe.

Running for a year now, it doesn't seem to make a difference.

`alias` is shell builtin.

This. Functions are almost always the better solution.

This is the first thing I recommend to new Mac users.

Performance is one problem, but much worse are the countless bugs which plague the last releases.

Did you do thorough error handling in Bash?

That's why I prefer test frameworks that make parametrised tests so easy that they become the default.

Kotest and Spock are such frameworks.

Aurora Serverless Postgres e.g.

They are also slow AF because a lookup takes linear time.

That's why suggestions like RTFM! are stupid. I just don't have time to read every reference documentation of every tool I use.

Kotlin is much better in that regard.

I use Kotlin scripts (.main.kts) as a replacement for Bash scripts for years.

You can inline dependencies without additional tooling, and Kotlin is still much more expressive than Java.

I will probably solve the first 7 puzzles like every year and then just stop.

Great library for scripting, especially in combination with GraalVM and JBang!

While web dev remains a shit show, it's also amazing how much innovation is happening there.

Curlwind looks super nice.

What's missing from the article: The innovation heroes will not only leave, they will most likely also burn out.