pentaphobe

Or making knives that turn into overcooked noodles if you try to use them on anything except vegetables and acceptable meats

Obligatory Benn Jordan link (YouTube - ~11mins)

This Flock Camera Leak is like Netflix for Stalkers

https://youtube.com/watch?v=vU1-uiUlHTo

For anyone else who was entirely unfamiliar, here's a low-effort search

"Incoherent Conspiracy Suggests Ghislaine Maxwell Is a Powerful Redditor"

https://www.vice.com/en/article/incoherent-conspiracy-sugges...

Was offline and had no tech people or resources around, but got access to an unused 286 which booted into a mysterious "C:\" prompt

Slowly worked out how navigate the system, then tried running the various built in things I found

One of these was QBASIC. Started reading through and messing with the example games which were part of the built-in QBASIC in MS-DOS

Reverse engineering how they worked gave a lot of the core concepts (variables, loops, procedures)

After writing a few (very) naff text adventures I stumbled across the intriguingly named "DEBUG" tool

Used debug to step through some of the other built in MSDOS utilities and try to work out what the mysterious symbols were doing (how I learnt assembler and machine code)

Later when I finally found BBSs I started debugging/disassembling some of the BBS mini-demos which were ubiquitous those days, which introduced me to manipulating graphical memory etc.. The smaller size of these, and fact that they were generally coded in assembler was much more useful than reading through compiled code

I do not recommend writing assembler in DEBUG, but wouldn't trade in the learning I got from exploring a total black box with no references or learning resources (beyond time and curiosity)

Felt like doing alchemy

Yeah it's wild - not only not improving but seemingly getting worse

doesn't seem like anyone outside the audience thinks it's a serious problem (?)

I was toying with the same thing for a bit - the hope was if it worked well you could build it into a little unit (audio or HDMI eARC)

Doesn't solve for single units but could help with people who use soundbars or amps

Abandoned though - was basically just multiband compression and couldn't find a way to make it adaptable enough (some media always ended up sucking)

Would be super interested to hear what you tried!

There's been a lot of speculation/rationalisation around this already, but one I've not seen mentioned is the possibility of it being at least a little down to a kind of "don't look back" collective arrogance (in addition to real technical challenges)

(This may also apply to the "everything's too dark" issue which gets attributed to HDR vs. SDR)

Up until fairly recently both of these professions were pretty small, tight-knit, and learnt (at least partially) from previous generations in a kind of apprentice capacity

Now we have vocational schools - which likely do a great job surfacing a bunch of stuff which was obscure, but miss some of the historical learning and "tricks of the trade"

You come out with a bunch of skills but less experience, and then are thrust into the machine and have to churn out work (often with no senior mentorship)

So you get the meme version of the craft: hone the skills of maximising loudness, impact, ear candy.. flashy stuff without substance

...and a massive overuse of the Wilhelm Scream :) [^1]

[^1]: once an in joke for sound people, and kind of a game to obscure its presence. Now it's common knowledge and used everywhere, a wink to the audience rather than a secret wink to other engineers.

https://en.wikipedia.org/wiki/Wilhelm_scream

EDIT: egads, typing on a phone makes it far too easy to accidentally write a wall of text - sorry!

Big fan of this trend, well done!

Personally this kind of thing is just always gonna be self hosted or local only, but I see the appeal for folks who don't have that option

Brief off-topic greybeard cloud yell: I hate that we've all adopted the colloquial use of "algorithm".

Although it's interesting to imagine whether software is even possible with "no algorithm" :)

I've always associated this sort of life satisfaction & ritual spectrum with Zen "no-mind" [^1]

Whether it's coffee ritual, or doing dishes there's something pretty magical about the quiet flow state of engaging with the moment

[^1]: https://en.wikipedia.org/wiki/No-mind

> what topics are you interested in?

That's just it - any list I give would probably miss the mark. I guess it all ties back to computational thinking in some way? (physics, neuroscience, rendering algorithms, medicine, linguistics, category theory)

Perhaps if recommendation algorithms could be that generalised it would scratch most of the desire for a good anti-bubble..

But still misses that special sauce of discovering papers/topics I didn't know I was interested in.

Libraries and stumbling into random university lectures did this very well (or newsagents, video shops, etc..) -- broadening rather than narrowing

LLMs / vector space seem well placed to automate this kind of expansive/lateral matching -- but it does seem we (or marketers) tend to build recommenders around the assumption that individuals' interests are a singularity to zero in on.. (and so likely train our models for same)

Anyway - end rant - thanks again, really cool project! Clearly got me inspired :)

This is really neat!

If there was one of these for non-AI papers I'd easily lose hours each day

Totally off topic, but come to think of it, I'd love to see more feeds support anti-bubbling (show me _less_ of what I've frequently consumed)

Not sure if helpful, but..

Ive found that systems which _don't_ support this often end up accidentally putting people's cursors in the same sentence/block (resulting in one or more editors losing content or wasting time trying to get detached from the other cursors)

What makes it a hacker's file manager?

Feature list seemed almost exclusively focused on superficial stuff

Not meaning to be combative - I for one am always on the prowl for the next Norton Commander :)

but I saw more features of interest skimming the last 3 release summaries than in the whole readme

Second English speaker here who didn't make that connection at all

100%

Though it's notable [^1] that only in America does "esquire" imply any credentials or expertise

Tonnes of non-special boys in the UK get "esquire" as a suffix (maybe some go on the become attorneys, but unrelated :)

[1]: EDIT: on second thought - it's not "notable" at all, perhaps "interesting" was the word I sought..

Nice! You packed in so many things which are often drip fed, and take folk a while to find

Kudos

If you don't interpret the intent as "90% of human code will be AI" but instead as "90% of code being created globally" it's probably a really conservative estimate.

Creating 9x more code is depressingly easy - but zero correlation to percentage of meaningful output

You uh.. ask permission first?

In fairness 2/3rds of that was probably a regex for email addresses :)

popularity is irrelevant - the context is day-to-day. Prices change slowly over time of course, but that's different.

If there was less egg available for a given day, McDonald's [^1] don't charge more for a McMuffin, they sell fewer McMuffins

I'd argue AirBnb's approach here is more like Uber's surge rates. Which are clearly more extreme than anything taxi cabs did (bar the occasional bad actor)

[^1]: mcdonalds is stretching the "restaurant" analogy here, but they have a higher consistent turnover so seem like a closer comparison

The most consistent non-durability I see these days is business logic intertwined with external (API / file system / env vars) resource access - all scattered throughout layers of a codebase.

(Basically a violation of Factor IV in "Twelve Factor App" [^1])

Certainly not the _only_ durability concern present, but it seems to crop up more extremely and in more places.

Dependency Injection can help mitigate this a little but seems to often be a crutch which covers for poor architecture and enables eventually atrocious readability (a sad admission as I'm fundamentally a fan)

TLDR I find a good question to ask is whether the core logic and journeys can be executed in total isolation from any real resources. If it can't, you'll likely have a rough time testing, maintaining, or scaling - or at least changes will be more troublesome than they could be

(NB: bunch of sibling comments saying similar - but felt worth highlighting the local-first / isolated / separable aspect)

[1^]: https://12factor.net/backing-services

> but why would you watch this?

Surely if it's the _only_ video which understands MCP I need no more reason /s

Yeah, funny how property markets always seem to have that same response.

I bet most of those same people would lose their minds if their favourite restaurant tried to double prices overnight. "Yeah we sold a lot of burgers yesterday..."

Ah fair enough, thanks!

possibly patched now but definitely going to try breaking it now before moving any more stuff into it

Interesting that the author chose that title despite the existence of NSAIDS [^1] and paracetamol(acetaminophen) - the latter of which they even mention (but only in the context of combination with opioids)

Did I miss something?

EDIT: answered in sibling post, thanks @ggm!

[1]: Non Steroidal Anti-Inflammatory Drugs

TLDR: please don't stop doing exit interviews! (But do be very clear on who you're talking to and what their intention is.)

A whole lotta nuance lost with this headline..

A good reminder to be cautious , but I don't think the absolute position justified..

I run voluntary exit interviews with departing engineers - I'm not in HR (more of an engineering advocate / practice lead) and any disclosure of content is entirely opt-in, as it's not remotely necessary.

The purpose of these exit interviews _actually is_ to make us better & hold leadership accountable. (And give an escape hatch to The SNAFU Principle [^1])

Ideally we wouldn't only learn this stuff when someone's leaving, but alas sometimes that's how it goes.

FWIW: generally collate insights and themes from these interviews, periodic skip 1:1s, etc.. and use them to report on broad trends we're doing well / sucking at.

For me these things are invaluable.

[1]: https://en.m.wikipedia.org/wiki/SNAFU_Principle

Out of interest - What wasn't working for you?

I use Just inside (and outside) mise, almost exclusively with embedded shell/python scripts. Have used mise tasks a little, but didn't meaningfully add enough for me

Or do you mean justfiles with shebangs?

Either way, curious what problem you hit (and may be able to unblock ya)

Neat! The nostalgia is palpable.

Off topic: we always referred to mode-x variants as MCGA, TIL that's more of a colloquial term than a technically accurate one [1]

[1]: https://en.m.wikipedia.org/wiki/Multi-Color_Graphics_Array

That's a great approach - definitely adding your framing to the toolbelt, thanks for that!

kind of organically landed on a similar thing, where initial task is kept pretty simple (but not covered by common libs)

Some folk solve and code this quickly, so we add a requirement. (Generally up to a few stages - think like Advent Of Code)

Any leftover time can be spent discussion wishlist items for productionising, optimising, tests, etc..

But: plenty of people only complete the first stage, but this can absolutely be a pass too (based on comms style, approach, etc..)