greenden Profile Banner
Denys Zadorozhnyi Profile
Denys Zadorozhnyi

@greenden

Followers
483
Following
1K
Media
89
Statuses
2K

Software engineer.

Joined August 2008
Don't wanna be here? Send us removal request.
@Ukraine
Ukraine / Україна
4 years
Dear friend, your actions matter. Your voice can be decisive to strengthen Western resolve and protect the security of Ukraine, Europe and the democratic world. Act NOW! See thread with a few simple steps to support Ukraine 👇
1K
32K
92K
@tikhonjelvis
Tikhon Jelvis
5 years
This is great advice. I've started using GitHub's search to look for definitions and usage examples. Made my life much easier. It took some practice—GitHub search isn't always great—but now it's my go-to option when Stack Overflow and the official docs don't cut it.
2
3
17
@mfeathers
Michael Feathers
5 years
Nice capsule description of Technical Debt for non-technical stakeholders.
32
1K
3K
@alastair_d_reid
Alastair Reid
6 years
Verifying vs testing? Why not both? New blog post about our work on Rust verification based on reimplementing the proptest library for formal verification tools so you can use the same test harness with both proptest and with “propverify”. @rustlang #KLEE https://t.co/rAzAvW6MCI
7
50
168
@stevemblackburn
Steve Blackburn (@[email protected])
6 years
This is special. Once in a decade stuff. Detailed histories of APL, C++, Clojure, D, ELisp, F#, Fortran, Groovy, JavaScript, LabVIEW, Logo, Lisp hygienic macros, MATLAN, Objective-C, Oz, S, R, Smalltalk, SML, and Verilog. All written by key players. All open access.
@fancytypes
Stephanie Weirich
6 years
HOPL IV proceedings have been published!
5
248
600
@greenden
Denys Zadorozhnyi
6 years
Make incorrect states unrepresentable.
@ProgrammerDude
Arian van Putten
6 years
Love these moments where you suddenly realise your code is a lot easier to read when you describe the state machine as sum types
0
0
2
@owickstrom
Oskar Wickström
6 years
Determinism and generative testing, a neat combo! 👏
@copyconstruct
Cindy Sridharan
6 years
Dropbox blogged about rewriting the core sync engine from Python to Rust. - Rust has been a force multiplier for our team - betting on Rust was one of the best decisions we made - ergonomics + correctness + encoding complex invariants in type system helped tame sync’s complexity
0
9
24
@greenden
Denys Zadorozhnyi
6 years
More fold intuitions https://t.co/y669MlDt3l
@debasishg
Debasish (দেবাশিস্) Ghosh 🇮🇳
6 years
@Iceland_jack 2 intuitions that I use when explaining folds. Olin Shivers explains ( https://t.co/Gl1sATwtzN) foldl as the fundamental list iterator and foldr as the fundamental list recursion operator. And Tony explains how foldr is used to do constructor replacement
1
0
5
@greenden
Denys Zadorozhnyi
6 years
I’ll never be able to write such amazing PR review note as @lexi_lambda. It’s all you need to know about folds! https://t.co/umBNErdiZa
1
14
51
@hmemcpy
Igal Tabachnik
6 years
This includes @haskellhutt's Programming in Haskell and many others!!
@MiShee54
Michelle Sheehan
6 years
Cambridge University Press has just made all 700 textbooks currently available in HTML format on Cambridge Core free to access until the end of May to assist readers during the Covid-19 outbreak. This also includes 58 textbooks in Language and Linguistics.
0
20
59
@jnymnz
Janey Muñoz
6 years
stuck home and social distancing... perfect time to watch some of the Programming with Categories lectures https://t.co/xvXjdaRdzq
1
4
15
@kamrify
Kamran Ahmed
6 years
Big-O Notation in One Picture
15
191
570
@etorreborre
Eric Torreborre
6 years
How laziness in #haskell makes `minimum = head . sort` efficient (O(n)):
2
2
17
@etorreborre
Eric Torreborre
6 years
Step-by-step explanation of how lazy evaluation works in #haskell
0
3
9
@wasmerio
Wasmer
6 years
Happy Tuesday! We just got Clang running in the browser (no server needed!) You can now compile C to WASI online in the #WebAssembly shell 🤯 https://t.co/NPPhCnhdGs
10
275
861
@greenden
Denys Zadorozhnyi
6 years
Golden testing. WANT. “... which it will serialize to a JSON string and write to a test resource file. The next time we run the test, it will find that file and will confirm that the current decoder can decode it, as well as that the current encoder will produce the same result.”
@guizmaii
Jules Ivanic
6 years
The auto derivation mode of Circe was a bad idea. To remove that once it's in your project, good luck.. 😕 Use the semi-auto mode with some golden tests, folks! (See https://t.co/dPWh1OzmJG)
0
0
2
@guizmaii
Jules Ivanic
6 years
This is maybe one of the best examples of what I call "separation of the what and the how". In the first version, the "what" is not (explicitly) expressed. Only the how is. That's one reason why I love inner functions and Scala ❤
1
1
6
@greenden
Denys Zadorozhnyi
6 years
“// TODO:” and “// FIX ME:” are kind of okay in feature branches (although I prefer a todo list in PR description), but should be moved to issues when it’s time to merge. It’d nice to see a CI check for this.
@danielpunkass
Daniel Jalkut
6 years
It's common for programmers to write something like "// FIX ME: ..." in code, where an expedient but distasteful solution is used in a pinch. I propose we start writing "// FORGIVE ME" instead, acknowledging that it will likely never be fixed.
0
0
0
@greenden
Denys Zadorozhnyi
6 years
Can confirm! Scalafmt on file save is a savior. Thanks @scalameta !
@taylorfausak
Taylor Fausak
6 years
I'm amazed at how freeing it is to avoid formatting code manually. I don't care which formatter you use, but try one out!
0
0
1
@greenden
Denys Zadorozhnyi
6 years
Hot Path™️ 😍
@csaba_hruska
Csaba Hruska
6 years
VSCode plugin: Haskell profiling information as source code highlight. Try out the prototype: https://t.co/n8rZ9zk2M4
0
0
0