lucasmreis

5 ms·

1.
Fast Cloudfront Log Queries Using AWS Athena and Serverless(medium.com)
6 points by lucasmreis 7y ago|0 comments
2.
Adopting Optimizely at Compass(medium.com)
8 points by lucasmreis 7y ago|0 comments
3.
Learning ReasonML, Part 3 – Implementing Side Effects(lucasmreis.github.io)
8 points by lucasmreis 9y ago|0 comments
4.
Learning ReasonML, Part 2 – Integrating ReasonML into a React Application(lucasmreis.github.io)
1 points by lucasmreis 9y ago|0 comments
5.
Learning ReasonML, Part 1 – Lucas Reis' Blog(lucasmreis.github.io)
4 points by lucasmreis 9y ago|0 comments
6.
Making Sense of Insurance Cards Using Deep Learning(zocdoc.com)
6 points by lucasmreis 9y ago|0 comments
7.
Simple React Patterns – Dealing with Side-Effects in React – Lucas Reis' Blog(lucasmreis.github.io)
5 points by lucasmreis 9y ago|0 comments
8.
The Single Most Important Driver of Software Quality(dev.to)
2 points by lucasmreis 9y ago|0 comments
9.
Type Driven Domain Modelling, Part 3: One More Spec Change with F#(lucasmreis.github.io)
4 points by lucasmreis 10y ago|0 comments
10.
by lucasmreis 10y ago
Really good, amazing example
11.
by lucasmreis 10y ago
It's ok! :) So, if we only want to call a couple of animations and submit a form, I agree that a small script with three jQuery-style functions can do the job. But that's rarely the case nowadays, in my experience. Almost every fr
12.
by lucasmreis 10y ago
From my research and experiments, I think that ML languages help a lot "getting the specs right". That means that you have more confidence that the code does what you want it to do. I can see a lot of value for that in non-tech co
13.
by lucasmreis 10y ago
Thank you! I actually just removed createQty from the code. not only it had a typo, it was not being used anywhere beside the tests. And, as some commenter on Disqus said, probably the right thing to do would be returning an Qty option from
14.
by lucasmreis 10y ago
Amazing - I'm gonna use this in the future :)
15.
by lucasmreis 10y ago
I disagree too. Frontend is getting more complex each day, and I find that functional programming languages help a lot with large projects. Frontend SPA's are crying for help with the exploding complexity :)
16.
Type Driven Domain Modelling, Part 2: Evolving Models with F#(lucasmreis.github.io)
86 points by lucasmreis 10y ago|65 comments
17.
by lucasmreis 10y ago
I only heard about it after researching F#. Not only Domain modelling, I also started hearing about Event Sourcing and CQR after learning F#.
18.
by lucasmreis 10y ago
Thank you! I'm getting into F# from a non-dotnet background: JS > Clojure > Elm > F# :)
19.
Type Driven Domain Modelling – Evolving Models with F# – Lucas Reis' Blog(lucasmreis.github.io)
4 points by lucasmreis 10y ago|5 comments
20.
From Elm to Fable – Trying F# in the Front End – Lucas Reis' Blog(lucasmreis.github.io)
1 points by lucasmreis 10y ago|0 comments
21.
Learning Elm Part 4 – Property Based Testing and Better Modelling(lucasmreis.github.io)
1 points by lucasmreis 10y ago|0 comments
22.
Does Elm Harmonize with F#?(lucasmreis.github.io)
5 points by lucasmreis 10y ago|0 comments
23.
Centralized State Design Patterns(lucasmreis.github.io)
3 points by lucasmreis 11y ago|0 comments
24.
by lucasmreis 11y ago
Thanks for the compliment! :) I agree that Clojure and Clojurescript are superior languages than Javascript. In fact, I had my first contact with CSP through those languages. I like the React wrappers more than React itself, but I prefer Qu
25.
Using Communicating Sequential Processes as Front-End App Architecture(lucasmreis.github.io)
19 points by lucasmreis 11y ago|2 comments
26.
Using Communicating Sequential Processes as Front-End App Architecture(lucasmreis.github.io)
1 points by lucasmreis 11y ago|0 comments
27.
Quick Introduction to Communicating Sequential Processes in JavaScript(lucasmreis.github.io)
2 points by lucasmreis 11y ago|0 comments