HNHacker News
TopNewBestAskShowJobs

not_kurt_godel

1,671 karma · joined February 4, 2014

submissionscomments
not_kurt_godel··on A worker fell into a nuclear reactor pool
In technical fields: Accredited formal education, professional certification(s), and/or recognition from other experts in the field who have the same.
not_kurt_godel··on A worker fell into a nuclear reactor pool
There is also incentive for people to inflate their sense of importance by weighing in on topics they're not qualified on, especially if it's motivated by a sense of familial pride. You can see elsewhere on this thread that arthurcolle self-admits a lack of familiarity with basic interpretation of CPM.

Misinformation, whether ill-intentioned or not, does real and tangible harm to our society. Misinformation about the supposed dangers of nuclear power, as arthurcolle is spreading, are especially harmful because they form the foundation are the biggest obstacle to safe, clean, cheap, and abundant energy that could radically improve our lives at the systemic level.

not_kurt_godel··on A worker fell into a nuclear reactor pool
Do people on the Internet have an incentive to baselessly speculate in order to indulge their own Dunning-Krugerized delusions of grandeur?
not_kurt_godel··on A worker fell into a nuclear reactor pool
I care enough that I would trust assessment of their health and condition only to qualified professionals with access to the relevant information, just like anyone else that I care about
not_kurt_godel··on A worker fell into a nuclear reactor pool
That'd be a very interesting statement if you were qualified to make it
not_kurt_godel··on A worker fell into a nuclear reactor pool
Yep you know better than the people who have the credentials you don't and the access to internal data you don't. I don't see what's holding you back from doing surgery, qualifications and context are no barrier to the application of your self-imagined expertise.
not_kurt_godel··on A worker fell into a nuclear reactor pool
So you don't have the necessary credentials, and you still wouldn't be qualified to comment even if you did have them unless you had access to the internal data. But no worries, I'm sure you'd be OK getting surgery from a surgeon's son who never went to medical school nor read your chart.
not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
I will concede the thrust of my argument probably does not fully align with Fielding's academic definition, so thank you for pointing me to that and explaining it a bit.

I'm realizing/remembering now that our internal working group's concept of HATEOAS was, apparently, much stricter to the point of being arguably divergent from Fielding's. For us "HATEOAS" became a flag in the ground for defining RESTful(ish) API schemas from which a user interface could be unambiguously derived and presented, in full with 100% functionality, with no HTML/CSS/JS, or at least only completely generic components and none specific to the particular schema.

not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
Deriving a presentation layer from an API definition has no bearing on whether the client has to be stateful or not. The key difference for 'true' HATEOAS is that the API schema is sufficiently descriptive that the client does not need to request any presentation layer; arguably not even HTML, but definitely not CSS or JavaScript.

https://ics.uci.edu/~fielding/pubs/dissertation/rest_arch_st...

> any concept that might be the target of an author's hypertext reference must fit within the definition of a resource

not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
It's a broader definition of HATEOAS. A stricter interpretation with practical, real-world benefits is a RESTful API definition that is fully self-contained that the client can get in a single request from the server and construct the presentation layer in whole with no further information except server responses in the same format. Or, slightly less strictly, a system where the server procedurally generates the presentation layer from the same API definition, rather than requiring separate frontend code for the client.
not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
I'm not confusing it. I was heavily motivated by business goals to find a general solution for HATEOAS-ifying API definitions. And yes, a web page, implemented in HTML/CSS/JS is a facsimile for it in a certain sense, but it's not self-contained RESTful API definition.
not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
...which are a presentation layer and not a semantic, RESTful API definition.
not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
Your point would be much stronger if all web forms were served in pure HTML and not 95% created by JS SPAs.
not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
Altering the presentation layer is not the same thing as deriving it from a semantic API definition.
not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
It's not. The whole point of HATEOAS is that the presentation can be entirely derived from the API definition, full stop.
not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
I worked on frontend projects and API designs directly related to trying to achieve HATEOAS, in a general, practical sense, for years. Browsing the modern web is not it.
not_kurt_godel··on Context engineering is sleeping on the humble hyperlink
I appreciate the conceptual analogy, but that's not really HATEOAS. HATEOAS would mean your browser/client would be entirely responsible for the presentation layer, in whatever form you desired, whether it's buttons or forms or pages or not even a GUI at all, such as a chat interface.
not_kurt_godel··on Leaving serverless led to performance improvement and a simplified architecture
The solution is to use the appropriate tool for the job. If you're locked in to highly crusty legacy software, it's inevitably going to require workarounds. There are good technical reasons why arbitrary-size single-part file uploads are now considered an anti-pattern. If you must support them, then don't be shocked if you wind up needing EC2 or other lower-level service as a point of ingress into your otherwise-serverless ecosystem.

If we want to treat the architectural peculiarities of GP's stack as an indictment of serverless in general, then we could just as well point to the limitations of running LAMP on a single machine as an indictment of servers in general (which obviously would be silly, since LAMP is still useful for some applications, as are bare metal servers).

not_kurt_godel··on Extreme weather caused more than $100B in damage by June
https://apnews.com/ is a good place to start. In the meantime, perhaps you should refrain from opinionated commenting on current events if your opinion is self-admittedly derived from "clickbait whores".
not_kurt_godel··on Extreme weather caused more than $100B in damage by June
I'm sure, then, that you must you have some alternate means of keeping abreast of current events so that your public discourse is grounded in a shared understanding of objective reality. Care to share what those are?
not_kurt_godel··on Claude Sonnet 4.5
3 * 0 = 0.

Checkmate, aitheists.

not_kurt_godel··on Redis is fast – I'll cache in Postgres
You probably don't need Redis until you have thousands of requests per minute, nevermind per day.
not_kurt_godel··on Improved Gemini 2.5 Flash and Flash-Lite
Agreed. People talk up Claude but every time I try it I wind up coming back to Gemini fairly quickly. And it's good enough at coding to be acceptably close to Claude as well IMO.
not_kurt_godel··on Amazon has mostly sat out the AI talent war
How small are you? How small are you multiplied by 5?
not_kurt_godel··on Amazon has mostly sat out the AI talent war
> Leaving aside the pendatic "you can't be a multiple smaller than another object"

Feel free to not leave this out, it's a pet peeve of mine. Thank you for the moment of catharsis.

not_kurt_godel··on Are we decentralized yet?
And in many ways it actually is remarkably meaningfully decentralized - or perhaps "effectively" decentralized - in terms of every node having a full working copy of entire repositories that can be trivially cloned to another provider or stood up on a self-hosted server.
not_kurt_godel··on I tried every todo app and ended up with a .txt file
If you work at an office, you can set your reminders to be location-based with daily recurrence so that you get reminded when you leave the office or arrive home. I imagine you can also integrate Reminders with IFTT if you want a "Done with Work" button on your phone if you WFH.
not_kurt_godel··on I tried every todo app and ended up with a .txt file
I'm familiar with the pain point you're describing. In general, I would say a recurring calendar event is a better solution for your particular preferences. Personally my mental model is that the act of deciding to not do an optional task constitutes completion of the reminder for that occurrence. And if I forget or deprioritize that decision, the reminder still hangs out in my Today list until I do as a mitigation.
not_kurt_godel··on I tried every todo app and ended up with a .txt file
I agree it would be nice to have more alarm-like notification options. Flagging, setting as high priority, and assigning a date/time and getting in the habit of checking the Today category regularly all help mitigate; a bug-me-until-this-is-done feature would be a welcome alternative. (I will note that the GP's emacs stack isn't even close to offering native mobile push notifications, to state the obvious.)
not_kurt_godel··on I tried every todo app and ended up with a .txt file
Apple's Reminders app does all of those things and many more without having to learn emacs
← PreviousPage 5 of 22Next →