Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dirtbag__dad
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
1.
▲
by
dirtbag__dad
14d ago
I’m a full time SWE and AI has been a boon for my career and software in my personal life. I’m plowing through huge projects at work I never dreamed possible before agentic development. And now I can write side projects with the limited tim
2.
▲
by
dirtbag__dad
16d ago
If you ask any model to write as tables to enumerate points, and BDD for logical flows, it’s like 50x less strain on you
3.
▲
by
dirtbag__dad
18d ago
[for companies with idk 100 or less headcount] Good culture boils down to: 1. Predictability. Flavors of it: deliver features on time, roadmap stays mostly stable, on demand requests are known about ahead of time, business struggling or doi
4.
▲
by
dirtbag__dad
25d ago
For non-engineering teams my playbook is: 1. Get in all their support or public slack channels, watch for acute moments of freak out or consistent schlep blindness. 2. Meet with the head of the team once a month for 45 mins and get them to
5.
▲
by
dirtbag__dad
25d ago
This has been my experience until the past 6-9 months, when AI got good enough that I can build rails to prevent more bugs while also hammering through critical issues, redesigns, etc. It’s never been better to be a staff+ engineer, where y
6.
▲
by
dirtbag__dad
1mo ago
> just bringing back random knowledge from previous jobs or self study, and being able to apply it to the problem at hand. Being smart, at least in the context of the workplace, is about being checked in to whatever you’re doing, and dra
7.
▲
by
dirtbag__dad
1mo ago
New claude models, at least in the context of Claude code, are broadly lobotomized. Move extra slow, write loads tooling scripts you didnt’t ask for, and don’t actually complete the task at hand. They’re like rain man. Idk though it ebbs an
8.
▲
by
dirtbag__dad
1mo ago
I think you’ve missed the point of clean code if this is your gripe with it. Every time you over scope a function signature, because you want to handle that other case, you add mental tax to the next person. This accumulates, burns time, an
9.
▲
by
dirtbag__dad
2mo ago
> The actual problems in the code I work with are not the spaces at the end of line or imports in non-alphabetic order, it's the 10-line list comprehensions that are so long that they're impossible for me to parse. 100%. Almost
10.
▲
by
dirtbag__dad
2mo ago
If you can lock down a test suite that ensures parity, then who cares what shape the lift ultimately looks like. A full rewrite in different language that fails to be idiomatic is a step backward operationally, even if you stand to gain on
11.
▲
by
dirtbag__dad
2mo ago
Golf courses don’t have backup generators running 24/7, with humming you can hear from a meaningful distance away. They also don’t pollute the air. This is a poor comparison, but I do get what you’re attempting here. It’s also absurd t
12.
▲
by
dirtbag__dad
2mo ago
> My main project right now is to establish a framework for large-scale, unsupervised code generation in our codebase Anyone else working on something like this or know of any projects attempting it?
13.
▲
by
dirtbag__dad
3mo ago
Yes, same, between the two of them I feel like results are just better because they have different priorities. At the same time, I’ve invested in tooling that prints and lints architecture I want, so which model is less of an interesting de
14.
▲
by
dirtbag__dad
3mo ago
> in some areas, especially customer-facing sales, we expect to keep adding to our teams to support future growth Can someone help me understand why sales is immune to this strategy and still is employing the “more bodies” approach. I th
15.
▲
by
dirtbag__dad
3mo ago
> the code it produces is slop, but that’s more the fault of the model than the harness not being a good judge on if a step in the workflow resulted in a net improvement or completion. I don’t know. I’ve invested heavily in building inte
16.
▲
by
dirtbag__dad
4mo ago
You can get really far with the 20x Claude Code and Codex plans. They are many orders of magnitude cheaper than api calls.
17.
▲
by
dirtbag__dad
4mo ago
Is anyone else troublingly addicted to your code agents? I’m constantly thinking about work because work is “just wrapping up” always now. I go to see one thing is done, outside of work hours, then find myself kicking the next thing off. Wh
18.
▲
by
dirtbag__dad
4mo ago
I guess what I’m saying is that there is no “primary” goal, but rather a mix of things to consider, where it working at all as expected is just table stakes.
19.
▲
by
dirtbag__dad
4mo ago
> I don’t like senior developers who like trying new technology. I like ones that avoid more complexity. I guess the author has never worked on a dog shit system with no tests at all and constant downtime. I have worked with “complexity
20.
▲
by
dirtbag__dad
4mo ago
Good architecture is not about the patterns you pick. It’s about having a team dev cohesively on any pattern(s) - programmatically enforce your style with in-house linters and scaffolders. Be highly opinionated - if you # ignore anything, l
21.
▲
by
dirtbag__dad
4mo ago
> The ultimate goal of software is to solve the immediate problem at hand. The secondary goal of software is to solve likely future problems with as little work as possible. Not really. Today I learned of a story where a vibe coding PM
22.
▲
by
dirtbag__dad
4mo ago
> Also, when did we stop liking to learn? Says who? One of the most enriching things about coding with agents is I have them provide new information, tools, patterns, whatever as a follow up to every feature I work on. I’m learning a ton
23.
▲
by
dirtbag__dad
4mo ago
Build CLIs your agents call, that scaffold what you want, and lint so it actually does achieves your intended design. Markdown files are a good reference but they are a weak enforcement tool and go stale easily. Avoid burying yourself in mo
24.
▲
by
dirtbag__dad
5mo ago
There’s too much in this article to comment on it all, but if we zoom into the first claim: > An increase in the complexity of the surrounding systems to mitigate the increased ambiguity of AI's non-determinism. My question is why i
25.
▲
by
dirtbag__dad
5mo ago
I guess this is the case for new installs, but for existing dependencies can’t you simply pin them to a patch release, and point at the sha?
26.
▲
by
dirtbag__dad
5mo ago
Has anyone used this for debugging? Like an error in datadog triggers an agent sandbox and branched database?
27.
▲
by
dirtbag__dad
5mo ago
I watched the demo video on the git butler home page and agree with the premises that: 1. git is not going away 2. git UX is not great So i appreciate their effort to manage development better as agents make it possible to churn out multipl
28.
▲
by
dirtbag__dad
6mo ago
> Tests created a similar false comfort. Having 500+ tests felt reassuring, and AI made it easy to generate more. But neither humans nor AI are creative enough to foresee every edge case you’ll hit in the future; there are several times
29.
▲
by
dirtbag__dad
6mo ago
Yes. This seemed to be more cost effective.
30.
▲
by
dirtbag__dad
6mo ago
This. I have effectively used multiple agents to do large refactors. I have not used them for greenfield development. How are folks leveraging the agentic swarm, and how are you managing code quality and governance? Does anyone know of a si
More ›