mrjoelkemp

10 ms·

1.
by mrjoelkemp 3y ago
Not really. Working on a 2+ year, large, monolithic phoenix liveview app at Spotify. VS Code runs dialyzer on file save, which shows type mismatches. I also run dialyzer on pre-commit for a sweeping check. Ideally, we'd have the same o
2.
by mrjoelkemp 5y ago
Google does provide elixir clients for most of their products: https://github.com/googleapis/elixir-google-api
3.
by mrjoelkemp 5y ago
I have https://elixirdaily.link (an elixir/beam news aggregator running) on the smallest, free Gigalixir VM just fine. Does a ton of memory intensive work and doesn't go OOM (had to be careful with # outbound http conn
4.
by mrjoelkemp 5y ago
1.5 years in and Phoenix Liveview is perfect for internal webapps. Have personally seen development take half as much time with half as much people compared to traditional stacks. You don't need super rich interactions nor offline mode
5.
by mrjoelkemp 6y ago
For completeness, you should check out Elixir and Phoenix (channels and presence) for the server. Easy websockets, isolated player processes, non-blocking VM, plus deep introspection for debugging issues. https://youtu.be/Jv
6.
by mrjoelkemp 6y ago
Actor model with Elixir/Erlang and the BEAM VM.
7.
by mrjoelkemp 6y ago
I find building a simple game (like tictactoe) in Phoenix Liveview to be a good learning project. You can layer on multiplayer using Phoenix pubsub once you have a working one player version. You can also then layer on structs, typespecs, o
8.
by mrjoelkemp 6y ago
In my opinion, Java as a web language is good when you don't need to really understand what's happening (like in low-traffic situations). If concurrency isn't an issue, then the massive amount of libraries can help you a lot.
9.
by mrjoelkemp 6y ago
I found that my JS experience made a lot of Elixir feel very familiar (lambdas, destructuring, default args, string interpolation, optional typing). And compared to Node, the BEAM is a godsend in terms of its non-blocking process scheduling
10.
by mrjoelkemp 6y ago
A talk in ElixirConf this year showed that the pipe operator in Elixir is just a macro. A Code BEAM V conf Q&A with Jose had a (playful, trolling) question about implementing right handed assigns and Jose said that you can just write a
11.
An algorithm for algorithmic interview questions(medium.com)
2 points by mrjoelkemp 10y ago|0 comments
12.
Open source actually hinders teamwork(medium.com)
2 points by mrjoelkemp 11y ago|1 comments
13.
Giving better code reviews(medium.com)
3 points by mrjoelkemp 11y ago|0 comments
14.
by mrjoelkemp 12y ago
Thanks Kevin. This has been fixed. Thanks for trying linklink.
15.
Show HN: LinkLink – deep link to almost any website(linklink.herokuapp.com)
3 points by mrjoelkemp 12y ago|6 comments
16.
Ask HN: Why do you star GitHub repos?
8 points by mrjoelkemp 12y ago|7 comments
17.
YA: A no-hassle, front-end build tool(github.com)
1 points by mrjoelkemp 13y ago|0 comments
18.
JavaScript: An Exploration of Prototypal Inheritance(mrjoelkemp.com)
2 points by mrjoelkemp 13y ago|0 comments
19.
OSX open current terminal directory in finder
2 points by mrjoelkemp 13y ago|0 comments
20.
Backbone.js Declarative Events(github.com)
2 points by mrjoelkemp 13y ago|0 comments
21.
ShowHN: Facebook style mentions for Backbone apps(mrjoelkemp.com)
1 points by mrjoelkemp 13y ago|0 comments
22.
by mrjoelkemp 13y ago
Cheers for mentioning the closure compiler; I'll look into it. I haven't noticed much literature on its use in current build systems; I guess r.js gets all the fame due to its easier api.
23.
by mrjoelkemp 13y ago
Interesting. Something else that I should have included as a con for 3 is that Backbone would then be a requirement for the model-based solution. It sacrifices flexibility for smaller projects that need services.
24.
Large-scale JavaScript: A monolithic service layer(mrjoelkemp.com)
6 points by mrjoelkemp 13y ago|6 comments
25.
Developers vs. Engineers(mrjoelkemp.com)
4 points by mrjoelkemp 13y ago|0 comments
26.
by mrjoelkemp 13y ago
Thanks Jeremy. You're right and the point is obvious in hindsight. I think the end of your comment should be shared with others; for those that are eager to try, but not fully aware of the consequences of client-side rendered apps. I&
27.
by mrjoelkemp 13y ago
You're right about not mentioning why I didn't use it. Thanks for bringing this up. I had the rare opportunity to re-imagine the profile app in the context of another app that was being built from scratch and went with the server-
28.
Learnings from Client-side and Server-side rendering in Backbone.js(mrjoelkemp.com)
17 points by mrjoelkemp 13y ago|10 comments
29.
by mrjoelkemp 13y ago
Macbook air. Beautiful tools create beautiful products.
30.
The state of the consumer web(mrjoelkemp.com)
1 points by mrjoelkemp 13y ago|0 comments

More ›