TBD #115
Labels
chore
a tedious but necessary task often paying technical debt
elixir
Pull requests that update Elixir code
in-progress
An issue or pull request that is being worked on by the assigned person
tech-debt
A feature/requirement implemented in a sub-optimal way & must be re-written
technical
A technical issue that requires understanding of the code, infrastructure or dependencies
Please don't read this. 🙏
This is just me capturing my thoughts. It's not fully-formed and I'm not inviting comments/feedback yet ... 👌
Will be adding to this over the next couple of weeks and we can discuss when each section is updated.
As you can see, it's just an outline, that's very much on purpose.
Boilerplate, Misdirection and Magic 🪄
Phoenix
has ballooned in it's scope and complexity and thus a basicPhoenix
project has considerably more "boilerplate".A good history lesson is to look at Chris McCord's
phoenix_chat_example
which is built withPhoenix 1.3
:https://github.com/chrismccord/phoenix_chat_example/blob/7fb1d3d040b9d1e9a1bbd239c60ca1f4dd403c24/mix.exs#L24-L30
It has 5 dependencies and considerably less code.
By contrast we recently updated our
phoenix-chat-example
toPhoenix 1.7
dwyl/phoenix-chat-example#152https://github.com/dwyl/phoenix-chat-example/blob/e10e8dcdf730c1da22f3ab7d7357ebe608848833/mix.exs#L45-L59
15 dependencies. and this is only because we created the example app with the
--no-mailer --no-dashboard --no-gettext
flags to excludemailer
,dashboard
andgettex
(translation).Phoenix
1.7
🚀https://www.phoenixdiff.org/?source=1.5.0&source_variant=live&target=1.7.0
Modals 🤦♂️
dwyl/product-ux-research#38
Ecto
💔Maintenance ⏳
Types 🤷♂️
Supervision 👮♀️
AI / ML 🤖
Parallel Processing 💻
Channels ⏩
Presence 👥
Auth 🔒
UI Frameworks 🦄
Sunk Cost Bias? 💸
...
The text was updated successfully, but these errors were encountered: