Heykuki News

TopNewBestAskShowJobs
TopNewBestAskShowJobs
391.
JavaScript concepts every developer should know (github.com/leonardomso)
2 points
kiyanwang
2 years ago
discuss
392.
Typing "Nix-env -I" should not try to install every single package (2014) (github.com/NixOS)
2 points
todsacerdoti
2 years ago
discuss
393.
697 Clichés you should avoid to keep your writing fresh (github.com/errata-ai)
2 points
loughnane
3 years ago
discuss
394.
Should Golang have a built-in 'zero' function? (github.com/golang)
2 points
gus_leonel
3 years ago
discuss
395.
Should Rye Exist? (github.com/mitsuhiko)
2 points
ryannevius
3 years ago
discuss
396.
VSCode should ask user consent before sending any telemetry (ugh-issue) (github.com/microsoft)
2 points
gbraad
3 years ago
discuss
397.
Libeatmydata – because fsync() should be a no-op (github.com/stewartsmith)
2 points
eatonphil
3 years ago
discuss
398.
Ask HN: Should HN officially experiment with improving its ranking algorithms?
2 points
manx
3 years ago
discuss
399.
Show HN: Embedding a camera experience within your app shouldn't be that hard (github.com/Apparence-io)
2 points
macfleid
3 years ago
discuss
400.
Should we be avoiding passing Vector2/3/4 by ref then? (github.com/SixLabors)
2 points
ghuntley
4 years ago
discuss
401.
ClassicTreeview: The WPF Treeview that should have been (github.com/NWoodsman)
2 points
NWoodsman-
4 years ago
discuss
402.
Why you should be careful about commit messages (github.com/divio)
2 points
rhizome31
15 years ago
discuss
403.
Libeatmydata – because fsync() should be a no-op (github.com/stewartsmith)
2 points
harporoeder
5 years ago
discuss
404.
Show HN: What should scrypt's N be? [Rust] (github.com/slightknack)
2 points
slightknack
6 years ago
discuss
405.
Should X (github.com/Perl)
2 points
todsacerdoti
6 years ago
discuss
406.
Ask HN: Should I create several small projects or one medium-size project?
2 points
Memosyne
6 years ago
discuss
407.
Google Engineering Practices: Code Reviews Should Be Fast (github.com/google)
2 points
hharnisch
6 years ago
discuss
408.
Electron security best-practices should allow us to work with Webpack (github.com/electron)
2 points
bobblywobbles
6 years ago
discuss
409.
Latency Numbers Every Programmer Should Know by Year (gist.github.com)
2 points
simonpure
6 years ago
discuss
410.
BDD-like asserts “X should Y”, “A equals to B” for Go (github.com/fogfish)
2 points
fogfish
7 years ago
discuss
411.
Crates that don't exist, but should (github.com/dtolnay)
2 points
crunchiebones
7 years ago
discuss
412.
What you should ask when talking over a code base (gist.github.com)
2 points
tosh
7 years ago
discuss
413.
Proposal: Bake cancellation into Go 2 and Context should go away (github.com/golang)
2 points
nnx
8 years ago
discuss
414.
Ask HN: How should open-source projects written in Java be structured?
2 points
calebhwinston
8 years ago
discuss
415.
Latency Numbers Every Programmer Should Know (2012) (gist.github.com)
2 points
tosh
8 years ago
discuss
416.
Find who you should follow on Twitter based on who the people you follow follows (github.com/karpathy)
2 points
kumaranvpl
8 years ago
discuss
417.
Why We Should Not Return to Monolithic Repositories (gist.github.com)
2 points
rajathagasthya
8 years ago
discuss
418.
A Curated List of Checklists you should keep in your toolbox (github.com/huyingjie)
2 points
yingjie
8 years ago
discuss
419.
Should Crytal consider Immix GC? (github.com/crystal-lang)
2 points
007lva
9 years ago
discuss
420.
Show HN: TVS (Tabs vs. Spaces) – Because identifying the enemy should be easy! (github.com/jtanza)
2 points
jtanza
9 years ago
discuss
More