react, onyx, typescript, elixir, phoenix, gyarados
blogging at dnlytras.com
For example: `defmodule MyAwesomeSaas.Something.SomethingElse` or do you prefer a generic name? like `MyApp`?
I would hate it if I had to carry over an old name, and even more, renaming stuff down the road.
For example: `defmodule MyAwesomeSaas.Something.SomethingElse` or do you prefer a generic name? like `MyApp`?
I would hate it if I had to carry over an old name, and even more, renaming stuff down the road.
I'm not sure what to use for queues/jobs - that was always my pain point. I love how simple Oban is, and I definitely don't want to boot up a Redis instance.
I'm not sure what to use for queues/jobs - that was always my pain point. I love how simple Oban is, and I definitely don't want to boot up a Redis instance.
I spend a good chunk of my non-work time (new father) studying Elixir, Phoenix, LiveView, and experimenting with them.
I kept reading, "Just use LiveView," so I decided to try it out. I was surprised at how controversial my takes were.
Many of my @elixirlang friends will immediately dismiss this a "hating" and they'd be wrong for doing so.
#ElixirLang
I spend a good chunk of my non-work time (new father) studying Elixir, Phoenix, LiveView, and experimenting with them.
I kept reading, "Just use LiveView," so I decided to try it out. I was surprised at how controversial my takes were.
I would much rather have a bot spam Slack every two days with the output of `npx npm-check-updates -i`.
You spend so much time updating pointless patch versions with the illusion that you are fighting tech debt.
I would much rather have a bot spam Slack every two days with the output of `npx npm-check-updates -i`.
You spend so much time updating pointless patch versions with the illusion that you are fighting tech debt.
It's a very leaky abstraction. Why would I need `sent_to` in my session tokens?
Imagine needing to add more metadata (IP, Browser, Etc) to sessions now.
Almost always you have to separate them.
It's a very leaky abstraction. Why would I need `sent_to` in my session tokens?
Imagine needing to add more metadata (IP, Browser, Etc) to sessions now.
Almost always you have to separate them.
I don't hate JavaScript. So to be able to use the fantastic Elixir ergonomics, with React, is a big win.
I don't hate JavaScript. So to be able to use the fantastic Elixir ergonomics, with React, is a big win.
I can't fathom why would you want a library (Devise for example) take over your whole users table. You get some goodies, sure, but good luck debugging and patching that.
I can't fathom why would you want a library (Devise for example) take over your whole users table. You get some goodies, sure, but good luck debugging and patching that.
I also don't like the confusing and duplicate code in on_mount. This is too easy to mess up, and I'm most certainly messing up.
I also don't like the confusing and duplicate code in on_mount. This is too easy to mess up, and I'm most certainly messing up.
- Properly parse description as markdown
- Optional follow-up with downloading the 2nd part when finishing the 1st
Also finished the first challege
#elixirlang
github.com/dimitrisnl/a...
- Properly parse description as markdown
- Optional follow-up with downloading the 2nd part when finishing the 1st
Also finished the first challege
#elixirlang
github.com/dimitrisnl/a...
I love Effect-TS - it's a fantastic library, but there's a good reason to not let something take over your codebase like this.
github.com/evoluhq/evol...
I love Effect-TS - it's a fantastic library, but there's a good reason to not let something take over your codebase like this.
github.com/evoluhq/evol...
github.com/dimitrisnl/a...
github.com/dimitrisnl/a...
- "Why is this test failing"?
- "Well look at line X, ..."
- "Why is this test failing"?
- "Well look at line X, ..."