Benchmark in Milliseconds(matklad.github.io)
143 points by surprisetalk | 47 comments
A blog post by matklad arguing that micro benchmarks should be sized to run around 300 milliseconds, explaining the reasons for this rule of thumb.
58 stories on the front page, newest first. Scroll down to watch the site change over time.
143 points by surprisetalk | 47 comments
A blog post by matklad arguing that micro benchmarks should be sized to run around 300 milliseconds, explaining the reasons for this rule of thumb.
28 points by surprisetalk | 6 comments
41 points by olexsmir | 19 comments
109 points by surprisetalk | 65 comments
526 points by surprisetalk | 107 comments
Blog post by matklad, written as a reply to a researcher physicist, offering advice on learning software design and architecture skills, mainly by doing.
65 points by surprisetalk | 9 comments
201 points by ingve | 108 comments
113 points by ibobev | 78 comments
91 points by birdculture | 11 comments
22 points by enz | 9 comments
82 points by todsacerdoti | 30 comments
50 points by ingve | 15 comments
55 points by todsacerdoti | 34 comments
8 points by todsacerdoti | 1 comments
20 points by Zen1th | 0 comments
193 points by Bogdanp | 183 comments
128 points by ingve | 85 comments
163 points by Bogdanp | 51 comments
37 points by Bogdanp | 39 comments
156 points by LorenDB | 181 comments
495 points by goranmoomin | 177 comments
A blog post by matklad giving two rules of thumb: move if conditions up to callers and push for loops down into batch-processing functions, with Rust examples.
441 points by JadedBlueEyes | 180 comments
A blog post by matklad explaining the deliberate restrictions of Zig's comptime feature, such as no host leakage, and how it stays expressive despite them.
246 points by OptionOfT | 124 comments
130 points by rrampage | 47 comments
37 points by aiono | 39 comments
3 points by transpute | 0 comments
59 points by todsacerdoti | 21 comments
109 points by nequo | 95 comments
7 points by nalgeon | 2 comments
16 points by ingve | 2 comments
12 points by nalgeon | 0 comments
250 points by mooreds | 42 comments
154 points by nalgeon | 108 comments
49 points by sam_bristow | 11 comments
606 points by celeritascelery | 274 comments
A blog post by matklad giving two rules of thumb: move if conditions up to callers and push for loops down into batch-processing functions, with Rust examples.
271 points by ingve | 144 comments
77 points by ingve | 41 comments
153 points by GlobalFrying | 38 comments
145 points by ingve | 21 comments
62 points by tim_sw | 2 comments