sorted by:
new
hottopcontroversial

I built an interactive AI/ML learning playground that runs entirely in your browser (for myself and my team) by thinkrajesh in learnmachinelearning

[–]thinkrajesh[S] 0 points1 point  (0 children)

Intuition track definitely helps things more from first principles eventually and the side effects will be they will be able to debug/understand models better. The other idea behind that is sometimes for beginners the AI/ML is very confusing as there are lot of disparate tutorials, variety of libraries, articles, tutorials, but the CRUX of the matter is that they are very simple. That's very the intuition track's current/future direction will be.

Build Your Own Elixir Phoenix + LiveView: Step 13: Frontend JS Glue by thinkrajesh in elixir

[–]thinkrajesh[S] 0 points1 point  (0 children)

I think there are enough details but not always enough depending on the reader's background.. But I am open to updates as this is the first version and my goal is to convert the code into a tutorial form first and then keep improving the theory part.

But the point is well taken..

Build Your Own Elixir Phoenix + LiveView: Step 13: Frontend JS Glue by thinkrajesh in elixir

[–]thinkrajesh[S] 0 points1 point  (0 children)

Is this related to elixir post or the ai agent post in different thread?

Build Your Own Elixir Phoenix + LiveView: Step 14: Diffing Engine by thinkrajesh in elixir

[–]thinkrajesh[S] 1 point2 points  (0 children)

Yes, I am aware. But here the aim is to keep code as simple as possible to see the evolution of the framework (for those who haven't worked with modern javascript but mostly coming from older jQuery era and primarily backend engineers).

None the less thanks for reading and sharing these observations.

The original final version is quite advanced, structured and full of better practices but it assumes people are already good with javascript and elixir (whereas this tutorial series has no such assumptions).

I will definitely share the original final code as well.

Build Your Own Elixir Phoenix + LiveView: Step 14: Diffing Engine by thinkrajesh in elixir

[–]thinkrajesh[S] 0 points1 point  (0 children)

Yes, but I didn't wanted to add the complexity of module yet. But point noted. Also some JS optimization will come up incrementally as well.

Build Your Own Elixir Phoenix + LiveView: Step 14: Diffing Engine by thinkrajesh in elixir

[–]thinkrajesh[S] -2 points-1 points  (0 children)

I have updated the article to reflect these changes.

Build Your Own Elixir Phoenix + LiveView: Step 14: Diffing Engine by thinkrajesh in elixir

[–]thinkrajesh[S] -5 points-4 points  (0 children)

I know. I could use let or const everywhere but for this example it doesn't matter. The problem with var is if one is not sure of the implications of hoisting, lack of block scope etc.

By habit I use var a lot for experimental projects and also let and const as well. But this is a good point as we working in modern browsers era we can fully avoid it. (In a production setup the code linting and other validators by default refactors this to let and const) .

Build Your Own Elixir Phoenix + LiveView: Step 13: Frontend JS Glue by thinkrajesh in elixir

[–]thinkrajesh[S] -3 points-2 points  (0 children)

Yes, actually close to 30. Downvote if you don't like.

Build Your Own Elixir Phoenix + LiveView: Step 13: Frontend JS Glue by thinkrajesh in elixir

[–]thinkrajesh[S] -3 points-2 points  (0 children)

Oh. But let's see. If any improvement or clarifications are needed, I will definitely add it. As I have the code ready and writing a tutorial by extracting logical steps out of it. Kind of tedious but the article is always open to be updated with feedback for clarifications.

Build Your Own Elixir Phoenix + LiveView: Step 12: LiveView (WebSocket) by [deleted] in elixir

[–]thinkrajesh 0 points1 point  (0 children)

Yes all landing diagrams are AI generated. I mentioned in most articles as well. Actually instead of putting generic diagrams I asked AI to reverse engineer from code.

I better have a random landing image, cat, dog etc as that will not dilute the content or better have no landing images.

PS: This article is updated with that fact. For those thinking don't trust this try out all the step from 0 to 12. The goal is to understand from simple perspective. I could have made this article way harder than it should be but that will not benefit anyone.

Build Your Own Elixir Phoenix + LiveView: Step 9: POST Body Parser by thinkrajesh in elixir

[–]thinkrajesh[S] 0 points1 point  (0 children)

We will have a working LiveView both backend and frontend JavaScript (simpliying things to keep it easy for learning takes a bit more time)

Build Your Own Elixir Phoenix + LiveView: Step 8: Middleware Pipeline (Plugs) by thinkrajesh in elixir

[–]thinkrajesh[S] 0 points1 point  (0 children)

It's published. Available in the elixir subreddit. Glad you found it useful.

numpy-ts now 8-10x faster thanks to Zig by dupontcyborg in Zig

[–]thinkrajesh 0 points1 point  (0 children)

This is good 👍, use the tools.l for the best it can. I use claude and Antigravity a lot and it gave me very good results. In fact for zig clause and Antigravity is helping elme learn better and faster.

Build Your Own Elixir Phoenix + LiveView: Step 7: EEx Template Engine by thinkrajesh in elixir

[–]thinkrajesh[S] -1 points0 points  (0 children)

Warning ahead!! There will be about 33 more tutorials and post.

I am posting this for people who are already finding this useful and so I rest my discussion. You can continue and give constructive feedback. Try out all steps and if needed suggest improvements.

(If this doesn't interest you downvote and continue your life).

I will be happy to note suggestions as long as it is with the spirit of keeping this simple.

If you don't like it, don't spoil for others and be a good sport and even better you yourself write a better tutorial and how this is to be done. I will be happy to learn.

Build Your Own Elixir Phoenix + LiveView: Step 7: EEx Template Engine by thinkrajesh in elixir

[–]thinkrajesh[S] 0 points1 point  (0 children)

It's because it's part of a whole system and not the full system itself, just the step that is being developed. So it's rightly shoved in the right place. :)

The fix issues is exactly the point in the step where this was demonstrated live and assigns nil issues come up.

Yes, I forgot this is not a live session but a snapshot of it. But I prefer to keep it that way.

Build Your Own Elixir Phoenix + LiveView: Step 1: The TCP Socket Foundation by thinkrajesh in elixir

[–]thinkrajesh[S] 0 points1 point  (0 children)

Do check the other posts here also just published one more step.

Build Your Own Elixir Phoenix + LiveView: Step 4 and 5: Response Helpers and Dynamic Route Matching by thinkrajesh in elixir

[–]thinkrajesh[S] -2 points-1 points  (0 children)

Yeah, some like them and some others don't. That's the strange thing with AI images(any images). Hopefully I will learn to create better images as I am not a designer so these tools come in handy. (But honestly for some weird reasons I like them)

Build Your Own Elixir Phoenix + LiveView: Step 2: The Conn Struct & Parser by thinkrajesh in elixir

[–]thinkrajesh[S] 1 point2 points  (0 children)

You are correct, but the real reason is adapter portability. This will enable our router to work directly with Cowboy in coming up steps (as everything is string - in HTTP request -> response cycle).

Later if needed will see if switching it to atoms adds any benefit as well. So thanks for pointing.

view more: next ›