mike1o1

7 ms·

1.
by mike1o1 3mo ago
other discussion: https://news.ycombinator.com/item?id=48544781
2.
by mike1o1 3mo ago
You can see the CREDITS.md which has links to the models: https://github.com/levy-street/world-of-claudecraft/blob/mai...
3.
by mike1o1 10mo ago
https://github.com/historicalsource/zork1 Direct link to the repository
4.
by mike1o1 11mo ago
I have some projects with a fairly steady load that I'm currently running on a VPS on Digital Ocean. I have some non-critical ones that I'd be interested in moving to "bare metal" for learning purposes, but having a hard
5.
by mike1o1 1y ago
My youngest is absolutely obsessed with construction trucks. We really love the "Construction Site" series by Sherri Duskey Rinker. Some of the later books in the series go into how roads are built, airports, etc. Really lots of f
6.
by mike1o1 1y ago
If you haven’t yet, you should try out usage_rules mix package. I mostly use Ash, which has great support for usage rules and it’s a night and day difference in effectiveness. Tidewave is also really nice as an MCP as it lets the agent quer
7.
by mike1o1 1y ago
A bit late but it’s been fantastic so far. I’m using it for a GraphQL backend so I haven’t tried with LiveView yet but I don’t think it’ll differ too much. I know Ash has their own changesets which might be a bit different, but can’t say fo
8.
by mike1o1 1y ago
Very cool to see usage_rules mentioned in the blog. That tool is such a great idea, and leveraging that for Ash development has made a drastic improvement in LLM development for me. Excited to see that get more adoption across the Elixir ec
9.
6 weeks of Claude Code(blog.puzzmo.com)
581 points by mike1o1 1y ago|590 comments
10.
by mike1o1 1y ago
I use Tidewave which is a package for my Elixir app, and it allows the LLM to get access to some internals of my app. For example, Tidewave exposes tools to inspect the database schema, internal hex documentation for packages, introspection
11.
by mike1o1 1y ago
I guess, but you'll be writing a _lot_ of code yourself, that might be hard to maintain and can become brittle overtime as requirements evolve. As an example, I wanted to add support for adding tags to a resource, and support filtering
12.
by mike1o1 1y ago
My current project is using React Native (for native and web) and getting GraphQL setup was initially a pain, but having React and GraphQL subscriptions gives me enough of the "live" functionality, but without having to worry abou
13.
by mike1o1 1y ago
Yes, the learning curve is a extremely high. It took a few false starts over time, but after the "Ash book" came out, I gave it a more serious try and it finally started to click for me. I think it helped that at the time I was tr
14.
by mike1o1 1y ago
I've been using Elixir for about a year on a side project and I've been enjoying it more than any other backend I've used (Node, Rails and C#). I recently discovered Ash and I feel like after that initial learning curve my pr
15.
by mike1o1 1y ago
Claude Code has pretty much replaced Copilot overnight for me, though I wish the VS Code plugin was a bit more integrated, as it's only a little bit more than a terminal, though I guess that's the point. I was hoping for syntax hi
16.
by mike1o1 1y ago
I absolutely loved EverQuest and it’s still probably holds some of my fondest gaming memories. My favorite feeling about it is that it felt like a real world first, gameplay second. It had a real sense of danger and wonder that I think will
17.
Ash AI: A Comprehensive LLM Toolbox for Ash Framework(alembic.com.au)
8 points by mike1o1 1y ago|0 comments
18.
by mike1o1 1y ago
The GraphQL layer is built on top of Absinthe. If you really find something you can't model with Ash's actions, you can always just jump to your Absinthe schema and write you own queries/mutations/subscriptions. You&#x27
19.
by mike1o1 1y ago
I've been working on a project for a few months, and I had some of those initial pain points early on as well. I've actually found the codebase surprisingly approachable and have found the team to be very open to bugs and merging
20.
by mike1o1 1y ago
I'm also very comfortable with Phoenix and Ecto (and LiveView), and initially found Ash a challenge to wrap my head around. After working through the book and really keeping an open-mind on my next project, I've found it a real jo
21.
by mike1o1 1y ago
I wouldn't let the fact that the book is in beta dissuade you from getting it. It's mostly feature complete and is a _fantastic_ resource - it really helped get Ash to click for me, and I've found it a joy to work with after
22.
by mike1o1 1y ago
While DHH is the face of Rails, I’d say Shopify are the real stewards of the framework these days.
23.
by mike1o1 1y ago
Yes, unfortunately that is the big weakness of LiveView. It also suffers from what I call the elevator problem, where LiveView apps are unusable with unstable connections and flat out stop working in an elevator or areas with spotty connect
24.
We fell out of love with Next.js and back in love with Ruby on Rails(hardcover.app)
523 points by mike1o1 1y ago|519 comments
25.
The Post-Developer Era(joshwcomeau.com)
4 points by mike1o1 1y ago|1 comments
26.
by mike1o1 1y ago
I love using Elixir on the backend, and I tried really, really hard to get LiveView, but it was just too hard of a paradigm shift for me to manage more complex state, plus too hard to walk away from my productivity with React. For example,
27.
Garfield Minus Garfield(garfieldminusgarfield.net)
780 points by mike1o1 1y ago|246 comments
28.
by mike1o1 1y ago
It might be a contrived example, but I found the example of syntax highlighting a blog post to be a good example of the benefits of RSC. If you hydrate on the client, you need to run the same exact code on the server and again on the client
29.
by mike1o1 1y ago
There was a large group of folks that left Ruby on Rails for Elixir (even has a similar looking syntax), yet it wasn't on your list of languages to consider. Just curious, was there a particular reason?
30.
Sync Engines Are the Future(instantdb.com)
1 points by mike1o1 1y ago|1 comments

More ›