Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vrnvu
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
What happened to nerds?
(mrmarket.lol)
755 points
by
vrnvu
3mo ago
|
512 comments
2.
▲
by
vrnvu
5mo ago
Jujutsu is immutable for public changes by default. You can force changes with a ‘—ignore-inmutable’ flag.
3.
▲
The Third Hard Problem
(mmapped.blog)
2 points
by
vrnvu
7mo ago
|
0 comments
4.
▲
How Dada enables internal references
(smallcultfollowing.com)
24 points
by
vrnvu
7mo ago
|
5 comments
5.
▲
by
vrnvu
7mo ago
Brings memories of when I did some chapters of HTDP2 to learn Lisp. https://htdp.org/2024-11-6/Book/index.html More accesible than SICP, highly recommended
6.
▲
Does Syntax Matter?
(gingerbill.org)
3 points
by
vrnvu
7mo ago
|
0 comments
7.
▲
by
vrnvu
7mo ago
Related https://www.romaglushko.com/blog/whats-aouth2/
8.
▲
by
vrnvu
8mo ago
Ditched git for jj a year ago. Never going back. If anybody is hesitant give it a try!
9.
▲
by
vrnvu
8mo ago
I really liked the example in OP. I will give Deno and Dax a shot.
10.
▲
by
vrnvu
8mo ago
It's a cycle, design patterns, TDD, the latest framework or language. We keep chasing the next silver bullet, but there isn't one. There's no easy road.
11.
▲
by
vrnvu
8mo ago
Made me think. Every time I see a “Postman collection” or similar artifacts, my heart skips a bit. Use curl. Run it interactively in the terminal. When it works, move it into a shell script where you can simply check the status code. Voilà,
12.
▲
by
vrnvu
8mo ago
Love this version. I quoted the chapter about Leadership plenty of times at work. `True leaders are hardly known to their followers.`
13.
▲
by
vrnvu
8mo ago
First. Love that more tools like Honeycomb (amazing) are popping up in the space. I agree with the post. But. IMO, statistics and probability can’t be replaced with tooling. As software engineering can’t be replaced with no-code services to
14.
▲
Software Acceleration and Desynchronization
(ferd.ca)
5 points
by
vrnvu
9mo ago
|
0 comments
15.
▲
by
vrnvu
9mo ago
> On the one hand, at lower-levels you want to exhaustively enumerate errors... > On the other hand, at higher-levels, you want to string together widely different functionality from many separate subsystems without worrying about spe
16.
▲
Programming vs. Coding vs. Software Engineering (2019)
(rakhim.exotext.com)
2 points
by
vrnvu
9mo ago
|
0 comments
17.
▲
by
vrnvu
9mo ago
> Metrics are simple, extremely cheap You clearly haven’t seen our Datadog invoice :) Jokes aside, I liked the idea of listing things by level of detail. One related issue I run into all the time is how context gets lost when moving betw
18.
▲
by
vrnvu
9mo ago
My first thought: Controlling allocations and minding constraints... honestly, that's engineering stuff all services should care about. Not only "high-volume" services.
19.
▲
Social Architecture – The Toolbox
(hintjens.gitbooks.io)
2 points
by
vrnvu
9mo ago
|
0 comments
20.
▲
by
vrnvu
9mo ago
Sort of related. Jepsen and Antithesis recently released a glossary of common terms which is a fantastic reference. https://jepsen.io/blog/2025-10-20-distsys-glossary
21.
▲
Why PyTorch is an amazing place to work and Why I'm Joining Thinking Machines
(thonking.ai)
1 points
by
vrnvu
10mo ago
|
0 comments
22.
▲
Ghostty is now non-profit
(mitchellh.com)
1343 points
by
vrnvu
10mo ago
|
289 comments
23.
▲
by
vrnvu
10mo ago
Everyone can talk and give opinions. The real question is if you can actually make a difference. I tell people there's a gap between knowing how to do something and actually doing it. And that gap is a big part of our engineering skill
24.
▲
Artificial Computation
(cultureandcommunication.org)
11 points
by
vrnvu
10mo ago
|
2 comments
25.
▲
George Hotz: Outwit, Outplay, Outlast [video]
(youtube.com)
5 points
by
vrnvu
10mo ago
|
0 comments
26.
▲
Game design is simple
(raphkoster.com)
560 points
by
vrnvu
10mo ago
|
173 comments
27.
▲
by
vrnvu
11mo ago
>> Why is it not more popular? Property, fuzzy, snapshot testing. Great tools that make software more correct and reliable. The challenge for most developers is that they need to change how they design code and think about testing. I’
28.
▲
JVM exceptions are weird: a decompiler perspective
(purplesyringa.moe)
166 points
by
vrnvu
11mo ago
|
69 comments
29.
▲
by
vrnvu
11mo ago
> Any time you are making decisions based on information that you know at compile time, you could apply this technique I’d go further. Most business requirements are known at compile time. Take the simplest example, dispatching a functio
30.
▲
Programming Modern Systems Like It Was 1984 (2014)
(prog21.dadgum.com)
6 points
by
vrnvu
11mo ago
|
0 comments
More ›