I’m in a similar camp to the OP. For me, my joy doesn’t come from building - it comes from understanding. Which incidentally has actually made SWE not a great career path for me because I get bored building features, but that’s another story…

For me, LLMs have been a tremendous boon for me in terms of learning.

> But for me, it was missing something I didn't know how to name until I found it: the chance to be technical and connected.

I genuinely throught this was impossible for a very long time. In my SWE roles I’ve mostly felt disconnected and isolated.

I resigned from my last dev job and started working in donut and coffee shops. I loved it.

I’m pursuing Support Engineer roles now hoping it will provide the human focus that was missing prior.

Can relate a lot. I started off as a SWE but am pursuing a support role for similar reasons.

I was wondering the same thing.

Love it.

Only feedback I have is when I click into an image then hit back, it brings me to the top of the page which is kind of annoying. I wish it held my place.

Thanks for the feedback. I'm going to fix that.

Issue created: https://github.com/httpcats/http.cat/issues/258

Side note - is this post accessible from the site somewhere? I don’t see where you’d find it (along with the C is Best post [1] shared here recently).

[1] https://sqlite.org/whyc.html

Great, thanks!

I enjoyed the FBAPP acroymn. There should be a modern day equivalent.

I’m curious about the memory usage of the cat | grep part of the pipeline. I think the author is processing many small files?

In which case it makes the analysis a bit less practical, since the main use case I have for fancy data processing tools is when I can’t load a whole big file into memory.

Memory footprint is tiny:

Unix shell pipelines are task-parallel. Every tool gets spun up as its own unix process — think "program" (fork-exec). Standard input and standard output (stdin, stdout) get hooked up to pipes. Pipes are like temporary files managed by the kernel (hand-wave). Pipe buffer size is a few KB. Grep does a blocking read on stdin. Cat writes to stdout. Both on a kernel I/O boundary. Here the kernel can context-switch the process when waiting for I/O.

In the past there was time-slicing. Now with multiple cores and hardware threads they actually run concurrently.

This is very similar to old-school approach to something like multiple threads, but processes don’t share virtual address spaces in the CPU's memory management unit (MMU).

Further details: look up McIlroy's pipeline design.

I found out that Eastern Europe includes the Baltic States (northern) and the Balkans (southern).

I learned this because I play a daily game called FoodGuessr, where you have to guess which country a food dish is from. I tend to struggle in Eastern Europe.

I’ve been browsing this site for a decade plus and this idea was new to me. Maybe the author is in the same boat.

Edit: I see referencnes to shadyurl in the comments and I have heard of that, but probably wouldn’t have thought of it.

Fair. I’d think they would look for prior work beforehand, but that’s perfectly valid.

https://xkcd.com/1053/

Again, this was not a criticism, but a genuine question.

I can’t speak for the author, but this strikes me as the kind of thing you might not want to check prior work on. It just seems like a fun little project and sometimes seeing that other people have done it can be a bit demotivating.