cobertos
Joined 5 years ago
Joined 5 years ago
Hard thing to learn and to stomach. The you are essentially a few nodes downstream from the decision makers who commissioned the software in the first place. They have some long-term view even if you can identify in the short-term that things won't be working out well long-term. Hard to reconcile that with a steady paycheck.
You can then get yourself into product decisions, to try to steer the direction a bit, working wirh sales, but that has all its own issues too (the article mentions "selling whatever we thought would entice the salespeople enticing the salespeople enticing the brands." at one workplace)
How does anyone find fulfillment when this is the long-term prospect at most companies for software?
Does this use a library for plotting everything on the timeline or is it coded from scratch?
EDIT: I see now the code is at https://github.com/justdataplease/art-history-museum
Not even a good first-party export, gotta use some hacked together third-party one to get your data out.
This has an MCP server specifically so a workflow like that would work for you. This is just made to gold the data, and I'm a human accessible way should your AI fail you
But don't we, in real times, turn to the people we're comfortable talking to? We are not machines ranking the effectiveness of our peers for best outcome, though some of us surely still weigh that! It would be nice to go the most effective route, but sometimes that brings a lot of pain, judgement, or unforseen externalities.
(and hopefully we pick our close social relationships to make us more effective too!)
> "according to your community norms ..." ... without much real reveal
It puts data to what our understanding of those norms are. I don't know if there's a bigger reveal than "yeah, people generally are pretty comfortable with their spouse"
Tbh I was surprised anyone would/could open up and have an emotional conversation with a neighbor (when looking at risk vs reward). But, there are a lot of types of neighbors too.
> The study included a real-time alert system for intervening if a person indicated a high suicidal intent
Because it sounds a bit dystopian.
And found a little more about it[0]
> For example, in our monitoring studies, we install smartphone apps on participants’ phones. These participants are often recruited from hospitals after presenting with high suicide risk. We tell them explicitly that we monitor responses during certain hours—for example, between 9 a.m. and 9 p.m.—and that we will do our best to respond if we believe they are at imminent risk of harming themselves.
...
> We have real-time alerts when someone crosses a predefined risk threshold, and we follow a very detailed protocol that specifies exactly what actions we take at each level of risk. But we want participants to understand that this is not a replacement for clinical care. We are not a “Minority Report” system that will swoop in and prevent harm in every case.
[0]: https://primr.org/ethical-challenges-in-suicide-research/
The post office already does way more than you think it does. Like identity verification on behalf of the government and tracking which houses are considered "vacant" or not.
It would be nice to focus the USPS, but all these extra services have to be done by _some entity_, otherwise you can't have the final result. In this case, the result is a functional, auditable mail in ballot system
[0]: https://www.federalregister.gov/documents/2026/06/02/2026-10...
Feels like a language limitation to me. It is hard to describe succinctly the complexities of AI use that preserve a human element or recognizes externalities. The wording is not immediately obvious and require subtlety that I rarely see in HN, unless it's about the tech itself and it's minutae.
Curious to see if HN could have any kind of thoughtful conversation on it but so far I haven't seen one.
I found in the current version of Forgejo the most secure way to set it up was just to put the runner on a different host. There's a Docker in Docker setup [2] that was challenging to get working correctly but still didn't quite feel secure...
After setting it all up, I'm convinced GitHub actions as a concept is flawed. I wish the community would make a simpler git-defined CI/CD that didn't have the crazy surface area that actions does... Named shell scripts that can call out to other stuff in the runner Docker image and report it to the UI would be a nice start.
[0]: https://github.com/nektos/act
[1]: https://forgejo.org/docs/v15.0/user/actions/github-actions/#...
[2]: https://forgejo.org/docs/v15.0/admin/actions/docker-access/#...