__A garden-path sentence is a grammatically correct sentence that starts in such a way that a reader's most likely interpretation will be incorrect; the reader is lured into a parse that turns out to be a dead end or yields a clearly unintended meaning. "Garden path" refers to the saying "to be led down [or up] the garden path", meaning to be deceived, tricked, or seduced.__
I wish he built a "Edit a form in a slideover". Modals are already part of the core_components and the Phoenix team has done a good job of covering edge cases around CSS transitions. But slideovers have one aspect that's not well covered in modal flow: in/out transitions. Slideovers have a slide-in effect when they are invoked and at the end of transition load the form component which is a live_component. When you cancel/close they slide-out along with the form component. At the end of the transition is when you want to remove the live_component from live_view. Handling these transitions with live_components is very tricky.
Just came off your Elixir talk photos on Twitter to find this on HN. Please share your ElixirConf talk recording. Producing a nice emoji/avatar for an AI agent seems like a cool idea.
I got ChatGPT to write a python script to scrape entries in this post and output it as a csv file. Download it here https://github.com/subbu/ask-hn-candidate-list-chatgpt/blob/... and open in it Excel/Numbers. Finally I got ChatGPT to output my conversation with it into markdown https://github.com/subbu/ask-hn-candidate-list-chatgpt. I can host this script on modal and run it in a cron job, but that's overkill. I'll probably run this again and update the candidates list. This whole thing took me ~30 min.
Your youtube playlist combined with NanoGPT and your Lex Fridman podcast is like having a university level degree with a free internship guidance. Thank you!
This, totally. I manage a large B2B CRM with complex user-auth requirements and we use an off the shelf provider. It was an easy decision when we began, but now it has become a bottle neck in many ways. As your application becomes big you need a lot more customization to your auth logic. Large customers have specific customizations that off the shelf auth providers don't provide, or make it complex to implement. Over time auth and RBAC becomes crucial to your application. Engineering effort required to read through your providers documentation and implement workarounds exceeds a purpose built, native solution.
I really wish intelli-j provides a first-class editor. I could never get VSCode + ElixirLS to work smoothly. It's just broken. I have switched to NeoVim + plugins. It feels better mostly because of Vim's eco-system. But I am missing a lot of productivity due to lack of a good IDE.
I rewrote a large Rails+React+GraphQL with LiveView. LiveView replaced most of React. I still use React for rich text editors and complex browser based UI. LiveView plays well with this. I am happy not using GraphQL at all. It also consolidated all MVC code in one place. Phoenix made a few other things possible: in place chat, live updates (via websockets. No more polling).
I struggled with Ecto. It seemed too complex. I missed find_by_sql and the scopes of ActiveRecord. But once I went past the initial learning curve Ecto is a seriously well designed library. I have not written a single sql query by hand. Now I feel find_by_sql is an anti-pattern as I was mixing sql with ORM.
Once your database becomes sufficiently complex you start writing a lot more sql.
ActiveRecord's way of chaining scopes to combine multiple scopes is brittle. You can't customize the conditions. Ecto solves this by giving you composability. You can build on top of your earlier commands. If you combine this with pattern matching in the functions or Enum.reduce you have an extremely powerful and a flexible query engine.
Ecto also relies on the strengths of underlying database engine rather than treating it as a black box. If you are dealing with 100s of tables Rails way of polymorphic design doesn't give you referential integrity. I like Ecto's recommendations: https://hexdocs.pm/ecto/polymorphic-associations-with-many-t...
I am building a property management software (PMS). It's a specialized form of CRM. I have dumped MVC entirely in favor of LiveView. handle_event and handle_info are a better programming model for high-level of interactivity in a page. It also gets you closer to the database, entirely bypassing GraphQL and client-side JavaScript. I had to expose a whole API endpoint to set a flag here, a preference there. No more of that.
I implemented this feature in a shared flat context. The problem gets simplified as the users are all part of a group already and even the settlement happens without exchanging any money. Your share gets added to the monthly rent. Full write-up: https://blog.simplyguest.com/flatmate-expenses.html
Thanks. That helps. Looks like you can build a middleware using hooks alone. I found a good video from a React guru: https://www.youtube.com/watch?v=nUzLlHFVXx0. He builds a few Redux concepts in the video.
I have been on the fence for using Redux in a large-scale project and I am still not convinced about its usefulness. I feel its too much code for too little gain. You have listed it as one of the tools you have used in org-web. Does it add value?
I am a long time user of OVH. I don't care about fancy UI; I have hardly used it to get anything done except pay bills. I just wish they open a data center in India. That's the reason I was looking at DO; they have a DC in Bangalore.
One of the biggest problems with react-table is you end up with 2 headers. There doesn't seem to be a way to get rid of it. Its annoying if you have to fit the table in small space, or if you have just a few rows.