mononcqc

11 ms·

31.
Complexity Has to Live Somewhere(ferd.ca)
324 points by mononcqc 6y ago|171 comments
32.
by mononcqc 7y ago
I'm obviously biased since I'm one of the Rebar3 maintainers but: I prefer a declarative approach to config files and whatnot; composable profiles are really neat; the plugin system for reusable tasks; dialyzer "just works&qu
33.
by mononcqc 7y ago
Mostly I just like it better. But otherwise in my day-to-day off the top of my head: Less “magic” (fewer macros that may change semantics, straightforward config handling), focus on declarativeness, no variable re-binding, more powerful tes
34.
by mononcqc 7y ago
The Docker chapter does mention similar things, and José Valim recently wrote the following blog post on this: http://blog.plataformatec.com.br/2019/10/kubernetes-and-the-... In a nutshell, docker and k8s are to O
35.
by mononcqc 7y ago
This is ultimately not very different than what you would get with any firewall or network rules in any business, and it's an issue shared by most deployments regardless of whether you get containerized or not.
36.
by mononcqc 7y ago
Erlang's tooling has vastly improved in the last few years to the point it's not as much of a concern anymore (a formatter is the big missing thing), and I just happen to prefer its syntax to Elixir's in the first place. Whil
37.
by mononcqc 7y ago
Yes and no. Some of the struggles are fresher than others, and in some cases you do internalize things to the point they feel like a second nature. The effort mentioned here of getting newer people to read the content and/or produce it
38.
by mononcqc 7y ago
If both, we would certainly appreciate the feedback about which areas are considered unclear, in order to improve things further.
39.
by mononcqc 7y ago
Is this a general tip you're giving, or is there specifically pieces of information you feel are being too opaque in the text at this point?
40.
by mononcqc 7y ago
Well this is technically the fourth one I'm working on. All are available for free online because I want these resources to be accessible first and foremost. I've got: Learn You Some Erlang, which has been published with No Starch
41.
by mononcqc 7y ago
Erlang first. There is a large overlap with Elixir stuff, mostly at a higher level; whatever covers OTP, handling supervision, releases, docker image practices, approaches to testing, production practices, etc. will very likely be useful to
42.
by mononcqc 7y ago
One of the authors here. This website is still a work in progress. It's an ongoing effort to gather all the resources that will help you use Erlang in a business. The booksite is divided in three sections focusing particularly on Erlan
43.
by mononcqc 7y ago
You do your part, other countries try to do the same, and various means and strategies are implemented and shared globally. This “but we can’t fix it all alone, it’s a global issue” thinking mode has to go. All contributions are important i
44.
by mononcqc 7y ago
I'm the author. I'm not really disappointed Erlang didn't catch on more. As I said in the post, I wanted to take a bit of time to reflect over most of that decade, the ladder of ideas, and things that changed.
45.
by mononcqc 7y ago
The blog post is not actually about making FP accessible to the masses nor a how to guide about it, and if you read through the post, it’s even stated in there that it’s not important for the language to gain widespread use. That’s why I d
46.
by mononcqc 7y ago
As one of its maintainers I’m partial to rebar3 ( http://www.rebar3.org/ ) It’s become near-official for OSS Erlang work and the OTP team has moved the repo under their GitHub organisation ( https://github.com/
47.
by mononcqc 7y ago
Ejabberd runs with a lot of legacy. Essentially the first build tool that could pull deps in Erlang dates from 2007-2009, and it took another few years before more modern tools came to be in what their current form is. All these bigger proj
48.
by mononcqc 7y ago
We probably had our discussions about this before, tooling definitions diverge at times, and I have a vested interest in some of them, but I will just state my disagreement on the better tooling side of things ;)
49.
Goodbye Joe(ferd.ca)
875 points by mononcqc 7y ago|22 comments
50.
by mononcqc 8y ago
I've looked a bit for it and it appears nobody has put it anywhere. I personally do not have a copy either. I thought CodeMesh in 2017 had it, but it was never published.
51.
by mononcqc 8y ago
Hi, I'm the presenter in the video. If like me you prefer text formats, I have a blog post which partially covers the same content: https://ferd.ca/operable-software.html
52.
by mononcqc 8y ago
they do. I'm a paying user in the specific region mentioned. The thing they do not offer is the first month free. Quebec law forbids companies from "offering one month free" and then auto-billing you whether you consent or no
53.
Property-Based Testing with PropEr, Erlang, and Elixir(ferd.ca)
116 points by mononcqc 8y ago|8 comments
54.
by mononcqc 8y ago
Yeah. They're malicious caricatures, but as mentioned in the text, they're all different sub-personalities I've at least had at some point in my career. Also do note that the text is heavily copying The Little Prince, to the
55.
by mononcqc 8y ago
because Le Petit Prince is one of the most translated and sold books ever, and that the title was a very direct reference, I just didn't feel it would be necessary to include a note saying it's based on the little prince story sin
56.
by mononcqc 8y ago
yeah, Erlang-wise, most loggers have done these checks for years. There's always a big concern in terms of avoiding the most work possible as early as possible so all that filtering takes place early on. The handler and filter structur
57.
by mononcqc 8y ago
This is mostly fixed. First, the loggers tend to use unicode-aware pretty-printing, which lets you have rarer instances of a binary getting blown to its integer bytes representation. Then there's also ways to prevent just printing huge
58.
by mononcqc 8y ago
Yeah. One thing I'm wary about though is developing blind spots due to a) knowing Erlang and OTP very well and b) knowing rebar3 itself very well. I'm sure there are plenty of tricky traps that regulars have learned to work around
59.
by mononcqc 8y ago
I'd love to get your feedback on rebar3; I've heard that opinion repeated often, but not really often have I heard specifics that we could address directly.
60.
by mononcqc 8y ago
Elixir already has those rebindable variable, which can be "turned off" by using the ^ prefix on a match variable. Wouldn't that make the |> less useful to you already?

More ›