Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dhorthy
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
61.
▲
by
dhorthy
3mo ago
this is cool tech and i like the use case but I'm always afraid of building against these internal JSONL apis that claude code uses since they change all the time / not a formal product interface
62.
▲
Why Software Factories Fail (or: harness engineering is not enough)
(github.com)
394 points
by
dhorthy
3mo ago
|
272 comments
63.
▲
Proportional-Integral-Derivative (PID) controllers
(en.wikipedia.org)
125 points
by
dhorthy
4mo ago
|
63 comments
64.
▲
by
dhorthy
5mo ago
functional programming taught us this decades ago. State is the root of all evil. If the outcome of my interaction with the interface (e.g. tap a place on the screen) is a function of not just where i tap but the last 2-6 places i recently
65.
▲
by
dhorthy
6mo ago
diabolical
66.
▲
Principal Component Analysis
(en.wikipedia.org)
7 points
by
dhorthy
6mo ago
|
0 comments
67.
▲
The Kleene Star
(en.wikipedia.org)
2 points
by
dhorthy
6mo ago
|
0 comments
68.
▲
by
dhorthy
6mo ago
I think one of the main examples that i saw in a swyx article a while back is that using the sort of ALL CAPS and *IMPORTANT* language that works decently with claude will actually detune the codex models and make them perform worse. I will
69.
▲
by
dhorthy
7mo ago
it is very hard for me to take seriously any system that is not proven for shipping production code in complex codebases that have been around for a while. I've been down the "don't read the code" path and I can say it l
70.
▲
Plugtest
(en.wikipedia.org)
37 points
by
dhorthy
7mo ago
|
10 comments
71.
▲
by
dhorthy
7mo ago
software engineering is still software engineering. just because you don't type out the characters doesn't mean you're not designing systems and thinking critically and leveraging your experience. also: do we think this is wr
72.
▲
by
dhorthy
9mo ago
there is the theoretical "how the world should be" and there is the practical "what's working today" - decry the latter and wait around for the former at your peril
73.
▲
by
dhorthy
9mo ago
I don’t think anyone serious would recommend it for serious production systems. I respect the Ralph technique as a fascinating learning exercise in understanding llm context windows and how to squeeze more performance (read: quality) from t
74.
▲
by
dhorthy
9mo ago
there are hundreds of useful resources, including many linked in the article itself
75.
▲
by
dhorthy
9mo ago
the note about the crypto token was intended to “okay this is now hype slop and it’s time to move on”
76.
▲
A Brief History of Ralph
(humanlayer.dev)
73 points
by
dhorthy
9mo ago
|
40 comments
77.
▲
The space and motion of communicating agents (2008) [pdf]
(cl.cam.ac.uk)
49 points
by
dhorthy
9mo ago
|
7 comments
78.
▲
by
dhorthy
9mo ago
I read it. i agree this is out of touch. Not because the things its saying are wrong, but because the things its saying have been true for almost a year now. They are not "getting worse" they "have been bad". I am stagge
79.
▲
by
dhorthy
9mo ago
engineers always want to re write from scratch and it never works. a tale as old as time - my second job out of college back in like 2016, I landed at the tail end of a 3-month feature-freeze refactor project. was pitched to the CEO as 1-mo
80.
▲
by
dhorthy
9mo ago
i had the privilege of working w/ some incredible eng leaders at my previous gig - they were very good at working both upwards and downwards to execute against the "50/50" rule - half of any given sprint's work is f
81.
▲
by
dhorthy
9mo ago
the people yearn for refactoring
82.
▲
Refactoring – Not on the backlog (2014)
(ronjeffries.com)
44 points
by
dhorthy
9mo ago
|
20 comments
83.
▲
5 Years, 12 Pivots
(boundaryml.com)
16 points
by
dhorthy
9mo ago
|
5 comments
84.
▲
by
dhorthy
10mo ago
I think the key here is “if X then Y syntax” - this seems to be quite effective at piercing through the “probably ignore this” system message by highlighting WHEN a given instruction is “highly relevant”
85.
▲
by
dhorthy
10mo ago
agree - i've had claude one-shot this for me at least 10 times at this point cause i'm too lazy to lug whatever code around. literally made a new one this morning
86.
▲
by
dhorthy
10mo ago
For the record I do think the AI community tries to unnecessarily reinvent the wheel on crap all the time. sure, readme.md is a great place to put content. But there's things I'd put in a readme that I'd never put in a claude
87.
▲
HumanLayer (YC F24) Is Hiring Founding Engineers
(ycombinator.com)
1 points
by
dhorthy
11mo ago
88.
▲
by
dhorthy
1y ago
> If I tell them exactly how to build something the work needed to review the resulting changes is a whole lot less taxing. Totally matches my experience- the act of planning the work, defining what you want and what you don’t, ordering
89.
▲
by
dhorthy
1y ago
would "wrote" be more appropriate than "shipped"?
90.
▲
by
dhorthy
1y ago
there is a portion in the article where I talk about how our hadoop refactor completely failed
More ›