zachdaniel

6 ms·

1.
by zachdaniel 3y ago
I think its also important for people to realize that 1. its opt-in, if you don't like it don't use it :) 2. we don't do magic migrations. We generate a regular ecto migration from your resource changes. So you can use it as
2.
by zachdaniel 3y ago
We tried to make it a bit clearer recently with the section on "Compatibility". "Works great with Phoenix, Ecto and all the other first rate tools in the Elixir ecosystem."But you aren't the first person to say this
3.
by zachdaniel 3y ago
Ultimately we avoid that with a few specific things: 1. As sane config as possible. 2. ability to hook into functional processes and see what's going on 3. Layered escape hatches. You can add functional hooks to actions, or you can use
4.
Ash: A Gentle Primer(jon.hk)
102 points by zachdaniel 3y ago|15 comments
5.
Ash: A gentle primer(jon.hk)
6 points by zachdaniel 3y ago|0 comments
6.
by zachdaniel 3y ago
Okay, fixed :)
7.
by zachdaniel 3y ago
Yep, because I pushed a different change and accidentally removed the word Elixir again. Pretty stupid of me, it’s been a hectic day. We’re putting it back as we speak.
8.
by zachdaniel 3y ago
Not at all! Just an oversight :)
9.
by zachdaniel 3y ago
Thank you
10.
by zachdaniel 3y ago
Thanks for the feedback! Its pretty difficult to find someone with no context on what we're building at all and say "hey does this tell you what this thing does/what info is missing", so this is very useful.
11.
by zachdaniel 3y ago
We share a lot in common with those design principles, yes. Ultimately though I don't believe in modeling as a sort of "pure" thing that you can do in advance of coding. Our tools are aimed at essentially doing both at the sa
12.
by zachdaniel 3y ago
It now says "Elixir" right on the tin :)
13.
by zachdaniel 3y ago
Our recent changes to the website aimed at trimming it down were clearly overzealous.
14.
by zachdaniel 3y ago
We used to have tons of information and I spent a bunch of time removing it all trying to simplify. I very clearly removed too much . But, it’s definitely not GPT generated.
15.
by zachdaniel 3y ago
So, something that is very clearly true is that was need to make the website better :). We aren’t being vague on purpose! Most people who go to our website have gone with an idea of what Ash is already having seen a talk from me or talked t
16.
by zachdaniel 3y ago
When they don't you just write them yourself. All we do is generate migration files to provide a good starting point. Its a convenience tool.
17.
by zachdaniel 3y ago
To clarify: it's the same reason that I like plug.
18.
by zachdaniel 3y ago
For the same reasons that the author dislikes Tesla, I prefer it :D
19.
by zachdaniel 5y ago
Very kind of you to say! Getting it out of Alpha has definitely taken longer than I initially expected, probably something any other OS maintainer would have told me, but we're getting closer! Mostly need to make a few big documentatio
20.
by zachdaniel 5y ago
Hey there! I'm the author of Ash Framework, happy to answer any questions you have. A few people have deployed to production with Ash and are seeing good results, but it is definitely at the "sharp edges" phase, where its gre
21.
by zachdaniel 5y ago
https://elixir-lang.org/cases.html here you go
22.
by zachdaniel 6y ago
This highlights something interesting for me: I've literally never heard anyone "arguing" that they should have the title of "software engineer" or "programmer" or "software developer". I don&#x2
23.
by zachdaniel 6y ago
Ultimately it seems strangely exclusionary to draw lines in the sand like this. Everyone who learns how to program doesn't need to A.) be god's gift to the science of computing and B.) have the same level of understanding/flu
24.
by zachdaniel 6y ago
No need to be rude.
25.
Are You Really Ready to Start Adding Business Logic?(softwhale.io)
5 points by zachdaniel 8y ago|0 comments
26.
Managing Your Personal Configuration with Puppet(softwhale.io)
2 points by zachdaniel 8y ago|0 comments