2,189 karma · joined January 18, 2008
- https://cautomaton.com
- https://jamandtea.studios
- https://earlgrey.ai
- https://bsky.app/profile/cautomaton.bsky.social
I hadn't considered HTML and I'm definitely going to try this.
gnu and emacs already have a long history of cli and text friendly solutions that LLM dev agents can easily use and are trained on.
Or for structured data, just use a database. Dev agents can work with SQL just fine.
I didn't know about Kiro specs. I've been playing around with my own org-mode based approach with mixed success in keeping dev agent work tracked:
My take: The "not a game" positioning feels like surrendering before the real design challenge begins. With our first experiment (Retail Mage [1]), we deliberately created a hybrid between traditional game structure and AI improvisation. We released it precisely because we were getting similar feedback from folks that an early implementation was too open ended and didn't "feel like a game." While I think we proved our point, we also learned a lot (including some mistakes we made).
That said, I _also_ think we can build _more than games_ with this technology. I think we’re edging into a new genre or medium: more improvisational and participatory than either traditional games or film. Structure still matters in this space, though. Without it you're really in the fanfic engine or writing assistant space. That’s fine! But it's a different goal.
Honestly, I'm very interested in this space. I was just speaking on a panel about this Monday at GamesBeat in LA and a few of us have a new podcast about this topic "Playing With Inference" [2] with folks like Nick from AI Dungeon as guests.
[1] https://www.jamandtea.studio/news/making-retail-mage-a-new-a... [2] https://playingwithinference.com/
Some other highlights, specific to the Hacker News folks:
- We have our own AI backend, running in AWS. - Costs were a major issue and we did a lot to lower it - We use a hybrid approach of mixing traditional game AI with machine learning - We have not just AI NPCs, but an AI world interaction model
Anyway, happy to answer questions!
"So we have won. That is decisive. The world will be never ever like before. Globalists have lost their final combat. The future is finally open. I am really happy."
https://x.com/AGDugin/status/1854136340184490282
Dugin wasn’t exaggerating when he said, “We have won.”
Today’s White House display is exactly what he meant. A decade ago, the GOP would’ve never echoed Russian talking points. Now, they’re openly aligning with them.
This isn’t just isolationism—it’s the dismantling of U.S. hegemony from within.
We use LLMs for real-time gameplay. We released Retail Mage last year on Steam as a tech demo of what we can do. We've found FP8 to be the current sweet spot for accuracy and performance for our use case. It's one of the many techniques we applied last year to bring our real-time inference costs down by 3 orders of magnitude to make Retail Mage releasable.
Anyway, we're just sharing this with anyone who finds it useful.
You can read a few more note by our ML engineer, Yudi, on LinkedIn here:
https://www.linkedin.com/feed/update/urn:li:activity:7290455...
https://distill.pub/2020/growing-ca/
"Differentiable Model of Morphogenesis"
If you don't actively stay up with the tech, your understanding will atrophy. Consequently, because you intend to remain a PM, your tech will never be as strong as someone who is dedicated to it and you need to be okay with that.
Another classic example for this are engineering managers: people management (like project/product management) is its own discipline with a deep set of skills, research, training, etc. To become a good EM means you _will_ sacrifice some of your technical edge. That "deep technical understanding" that good EM's maintain is built on a foundation of years as a practitioner and, even then, requires continual investment.
I don't mean to discourage you, I just want to ensure you have realistic expectations.
Given all that and given your goals, I think you should just ask yourself a question only you can answer: how do you best learn?
If that's in the classroom, then go get that masters (online or in person). If that's with hands on projects, then set aside time for tinkering and get going. Likewise with books, videos, meet-ups, etc. You know what motivates you and what techniques keep you focused (because you'll need that discipline).
Regardless, I wish you luck and enjoy the journey!
In my case:
- I had 10+ years of experience in linux/unix development
- Career change to AAA game development which is predominantly Windows based
- Day to day do Unreal C++ developing in Windows with Windows toolchains
- Still use WSL (and thus bash) for everything else, including DevOps related work, cloud/container development work, and personal notetaking/productivity via emacs+org-mode.
So, some of us have reasons to co-exist in multiple OS's. I tend to write up scripts in Python if I can so that there's at least a chance that I can run them in both Windows + Unix environments.
I know it's not as popular or sexy as it used to be, but the whole point of a foundation like Apache was to avoid these situations, even more than the way the Linux Foundation is setup. Apache _explicitly_ manages projects to avoid these downsides.
- Single corporation ownership. Projects cannot get out of the Incubator unless they demonstrate a diverse and healthy community. That doesn't mean popular, it doesn't necessarily mean best-in-class, but it means that there shouldn't be just one entity backing a project.
- Membership in Apache is _personal_ not a seat for a given company. If you're a committer on an Apache project and you move jobs, you're _still_ a committer on that project
- The Foundation owns the trademarks. There have been fights about this in the past, but the whole idea is that the _community_ owns the name, so some corporation can't claim to be the sole or official owner by naming their company or product after the open source product.
The core premise of the Apache Software Foundation is community over code, that healthy, diverse communities have a better chance of standing the test of time than open source projects backed by a single individual or company. That's the thesis at least.
The is starkly different from several other foundations, notably the Linux Foundation or Eclipse Foundation which are modeled more around industry consortiums.
Both models have their place, but I believe Apache better models the core values many of us feel strongly about when it comes to free and open source software.
That said, this is still good work, especially considering your experience and age (I checked out your 2D physics library on github and I found the trailer on youtube).
One suggestion: As someone in the game industry, I personally wouldn't label it an MMO as it doesn't include many of the features, particularly the "massive" part of MMO, that is usually associated with that term. The work is already impressive enough, you don't need to give it a label that could open it to criticism.
Otherwise, this is solid work. If you're aiming for a career in the game industry eventually, it's a good foundation to build on.
If you want to learn more about actual game development stories, I recommend Blood, Sweat, and Pixels:
https://www.harpercollins.com/products/blood-sweat-and-pixel...
May seem a bit obvious to to the Hacker News crowd, but within the game industry I haven't seen it discussed as much. Curious for other takes and feedback.
Check out the physical ebook for Fist of the North Star as an example of this:
https://goodereader.com/blog/reviews/hands-on-review-of-the-...
My experience has been: start with Google until it's too painful to continue, choose between Azure AD or Okta. Self-hosting for plenty of firms is just asking for worse scenarios. Is there some market leader I'm unaware of?
To add to your list: I have a copy of Designing Games: A Guide to Engineering Experiences that I recently started reading.
For simplicity, I was considering "story" as part of the "status" side too (i.e.- there's a story here that I'm better than you for these reasons).
I know it's Hacker News, but come on folks, it's not that hard to understand that marketing, branding, storytelling and whatnot are real, meaningful forces in human dynamics.
You're only considering intrinsic value. That's helpful for raw commodities.
For nearly everything else, value is tied to perception, history, etc.
If I have two identical baseballs, they're both "just" baseballs. But one of them could have much more value due to its history: maybe it was a homerun ball by a famous player, or a ball that I or a family member hit/caught. Same function. Could be otherwise identical, but could also be worth very different amounts.
The stories we tell is where the primary value is.
In this case, your wife values the story of a natural diamond that was formed through long, natural processes and required the effort of finding, excavating, cutting and so on.
Now you could disagree with that story, or you could dislike the tellers and amplifiers of that story, but the fact remains that your wife and many others value that story, making it more precious than merely "shiny carbon."
This is branding and marketing 101. Humans are storytelling machines and they understand value largely via stories and relationships. Misunderstanding that is a failure to understand essential human characteristics.
Not sure how well any of the non-emacs parsers work though.
That goes for technology, words, political concepts, music...
Which is exactly what REST was originally designed to do: provide an architecture for the Internet (not your app or service) that allows for humans using software clients to interact with services developed by programmers other than those which developed the clients. It was about an interoperable, diverse Internet.
If the distributed application is not developed across distributed organizations, particularly independent unassociated organizations, then the architectural style of REST is overkill for what you intend and you could have just kept using RPC the whole time.
The point of the later RESTful API movement was to create distributed applications that leveraged the underlying architecture principles of the internet within their smaller distributed application. The theory being that this made the application more friendly and native to the broader internet, which I do agree is true, but was never the original point of REST.
That said, xcamvber [1] is right: this is me being an old person fighting an old person battle.
https://archive.stsci.edu/prepds/relics/
https://archive.stsci.edu/prepds/relics/color_images/smacs07...
That's the best original source I've found so far. It's also unclear to me if these images are largely from Spitzer or Hubble or a combination of data from both.