In the UK this is known as the "good chap" theory
Posts by Andy Jones
Hey @elixir-lang.org folks: what are some of the best system prompts or cursor rules youβre using on the daily?
As a software developer there is a direct inverse correlation between the number of ACTUAL emails you receive and participate in and the amount of code you write
In a software development team almost any problem, friction or pain-point can be solved by just being able to iterate faster. The great thing is that you can iterate out of a slump but also iterate to a summit.
Yes! This vision speaks to me!
Where can I sign up?! π€
Has anyone worked on a project which had a really good seed data story? What made it so great?
I want to make our seed data story better at {day_job} - Im wondering if there are any great examples out there we can copy
Does anyone else use LLMs mainly to make suggestions on the perfect reaction gif?
That post says more about the author than it says anything about either Go or Haskell
Sounds very reasonable to me π
Hey #ElixirLang folks: great job opportunity to be one of the first hires at srcbook.com. The product is epic and the team behind it is super strong. They pay very well. US only. Can intro to founder.
Are you using REST or GraphQL?
What do we prefer as a general pattern for validating function arguments? #ElixirLang
How about if instead `create_widget` actually takes 20 arguments or more?
bsky.app/profile/did:... has been really good for elixir.
Iβm still yet to find a good indie hacker feed but Iβm sure there is one out there
I might be wrong but I think @zachdaniel.dev had the same question which is what led to hex.pm/packages/ign...
Heads up Elixir-ists
We, the BlueSky elders, have decided many moons ago to retire #MyElixirStatus for #ElixirLang now that we ascended from hell (X) to heaven (π¦)
The vote was unanimous (if you exclude the votes against) so please adhere to it
Also, #Elixir is wrong and shall never be used, ever
I would guess folks are excited to augment LiveView but have realised that js is actually the solution for any complex client-only interaction. I've built multi-step dropdowns + datepickers entirely in LiveView (plus js hooks) - it was a massive timesink and it was a poor UX
With a little sadness I've now deactivated my Twitter/X account - so long, it was a great 14 years but now its time to move on π
Yes in public functions it would be an absolute no from me
What do #elixirlang peeps think of handling ok/error tuples as part of a pipeline? Essentially piping results to a function and pattern matching the ok/error values in the function head.
Good? Bad? Unimportant?
Lets say you have a GQL mutation which requires a specific user permission. There is a middleware to enforce the permission. The middleware is well-tested. Do you write a test at the mutation-level which also tests the user permission, or is the test at the middleware-level enough? #elixirlang
Just did a LiveView upgrade from 0.17 to 0.19 on a 2 year old codebase with a lot of LiveView cruft β¦ apart from some very minor changes everything just worked!!! #elixirlang
Can you just call a function from inside the worker?
Would be great to hear you discuss LVN on Elixir Outlaws podcast. Youβd have me as a listener at least
I'll sign-up to that - Its easy to over-dose on pattern matching in function heads but rarely does it actually improve readability over a `cond` or an `if`
Im trying to push towards Keywords for this and am also experimenting with NimbleOptions for validating these (at least in the main service/interface layer).
With this pattern do you ever struggle to setup data which exactly matches some very specific state of the system which is hard to create through the API? The sort of edge-cases or unexpected states a running application might find itself. Do you just create API funcs for those specific situations?
I really like the idea of storytelling/scenario based. I think being able to instrument your βgivenβ or initial test state like that helps readability. Iβll take a look at oaken π
Yes Iβve never felt completely comfortable with ex_machina. It often just feels like a wrapper around Repo with another API to have to learn