|
Lef
@
elefthei
Stamford, CT
|
|
Scala, Haskell, PL, Systems. Works at a hedgefund. He/him.
|
|
|
387
Tweetovi
|
489
Pratim
|
929
Osobe koje vas prate
|
| Tweetovi |
|
Lef
@elefthei
|
4. velj |
|
Will you be recording lectures?
|
||
|
|
||
|
Lef
@elefthei
|
30. sij |
|
That’s so cool that you read it!😳 yes I would be working in the same problems in my PhD
|
||
|
|
||
|
Lef
@elefthei
|
30. sij |
|
Am I too old to do a PhD in PL (29yo)
|
||
|
|
||
| Lef proslijedio/la je tweet | ||
|
Robert Reich
@RBReich
|
23. sij |
|
.@AOC is right.
There are 5 ways to accumulate a billion dollars in America:
1) Profiting from a monopoly
2) Insider-trading
3) Political payoffs
4) Fraud
5) Inheritance
None of these are earned or have anything to do with being successful in the supposed free market. twitter.com/Kanew/status/1…
|
||
|
|
||
|
Lef
@elefthei
|
27. sij |
|
|
||
|
Lef
@elefthei
|
23. sij |
|
Congratulations! 👏👏
|
||
|
|
||
|
Lef
@elefthei
|
22. sij |
|
I logged in on Medium after 6 months and saw my article "Algebraic types in C++17" has 50 claps! link.medium.com/qHG75QNHs3
|
||
|
|
||
|
Lef
@elefthei
|
17. sij |
|
Sums up 2020 #coq club threads. pic.twitter.com/cN14ykDdMN
|
||
|
|
||
|
Lef
@elefthei
|
31. pro |
|
Great post on top 3 security issues of 2019 by my friend Jon from peacemakr.io
medium.com/@mcla0181/top-…
|
||
|
|
||
|
Lef
@elefthei
|
28. pro |
|
This paper pretty much said it all 10 years ago “Fun with type functions” cs.tufts.edu/~nr/cs257/arch…
|
||
|
|
||
|
Lef
@elefthei
|
27. pro |
|
What is “fancy” Haskell? Is it MTL and Generics? What about GADTs? Can we still use Traversable? For sure TH must be fancy. I buy there is a subset of “plain” Haskell, but what is it? twitter.com/mattoflambda/s…
|
||
|
|
||
|
Lef
@elefthei
|
25. pro |
|
Yes please, I took the previous iteration of this course and would love to see how Haskell fits in
|
||
|
|
||
|
Lef
@elefthei
|
20. pro |
|
Algebraic Data Type
|
||
|
|
||
|
Lef
@elefthei
|
19. pro |
|
“I’m a Functor Morty!” twitter.com/haskellhutt/st…
|
||
|
|
||
|
Lef
@elefthei
|
19. pro |
|
|
||
|
Lef
@elefthei
|
18. pro |
|
No unit tests, just properties written ahead of time passed to quickcheck
|
||
|
|
||
|
Lef
@elefthei
|
18. pro |
|
Specification, systems and UI come first, then ML collects data and trains models for stuff which is hard to write in code, at the same time PL designs a DSL for implementing the system, in the end everyone uses the DSL to crank out the final product.
|
||
|
|
||
|
Lef
@elefthei
|
18. pro |
|
I’ve been thinking about this a lot. A software systems shop that pairs engineers like bands; a systems engineer, a PL researcher, a testing and specification engineer, an ML engineer, a UI/Human factors engineer.
|
||
|
|
||
|
Lef
@elefthei
|
15. pro |
|
Would love to know more but I am only familiar with Beer’s experiment in Chile, any similar works?
|
||
|
|
||
|
Lef
@elefthei
|
6. pro |
|
conal.net/papers/essence… and the talks of Eric Meijer in Foo cafe are pretty great
|
||
|
|
||