HackerTrans
トップ新着トレンドコメント過去質問紹介求人

py4

no profile record

投稿

Ask HN: What do you do at work while the coding agent is working?

5 ポイント·投稿者 py4·2 か月前·7 コメント

Google Antigravity Built an OS from a single prompt

antigravity.google
8 ポイント·投稿者 py4·2 か月前·9 コメント

I Asked 3 AI Agents to "Make It Better" Until They Refused. Only One Did

pooyam.dev
1 ポイント·投稿者 py4·4 か月前·0 コメント

The Priesthood of System Design

pooyam.dev
1 ポイント·投稿者 py4·4 か月前·0 コメント

I Miss Coding

pooyam.dev
2 ポイント·投稿者 py4·4 か月前·0 コメント

Browser Sessions Are All-or-Nothing

pooyam.dev
1 ポイント·投稿者 py4·4 か月前·0 コメント

Ironies of Automation

en.wikipedia.org
4 ポイント·投稿者 py4·4 か月前·0 コメント

Ask HN: How to avoid skill atrophy in LLM-assisted programming era?

18 ポイント·投稿者 py4·5 か月前·45 コメント

Vibe Coding as 2025 word of the year in Collins dictionary

en.wikipedia.org
1 ポイント·投稿者 py4·7 か月前·1 コメント

コメント

py4
·2 か月前·議論
I understand the negative sentiment toward Altman, but just to be fair, how do we define 'lying'? How does his behavior compare to that of the average executive, or even the average human?

I don't particularly like the guy; I'm just curious to see if he is objectively a liar in a way that most engineers, executives, or humans are not, or if this perception is simply a bias stemming from the general negative sentiment toward him.
py4
·2 か月前·議論
you wait for it to finish then review or give feedback in the meanwhile? if it's the former, i'm curious about what you still do in the meanwhile
py4
·2 か月前·議論
sounds like a plan haha. How is OpenCode vs Claude Code orchestration? have you ever needed to modify the orchestration since it's open source? do you mind sharing more about your experience?
py4
·4 か月前·議論
I wrote my experience here: https://pooyam.dev/i-miss-coding
py4
·5 か月前·議論
I was saying it was not commoditized a decade ago, but i feel it's getting commoditized *now*. So you seem to be basically saying SWE is over and it's time to move on to something that is primarily based on human-human interaction?
py4
·5 か月前·議論
I honestly think a better title would be "how to stay relevant in LLM era"
py4
·5 か月前·議論
simple example: Claude Cowork was written entirely with claude code
py4
·5 か月前·議論
1. No, implementing well defined requirements were not commoditized a decade ago. You still have to come up with the design and proper (efficient,correct,...) solution that respects the requirements. it was and still is the skill set of a L4/L5 SWE.

2. If you think LLMs cannot help with navigating ambiguity and requirements, you are wrong. it might not be able to 100% crack it (due to not having all the necessary context), but still help a lot.
py4
·5 か月前·議論
i'm trying to see what i can do to stay relevant
py4
·5 か月前·議論
llm training/inference stack
py4
·5 か月前·議論
LLM is not hype. it has made and my colleagues who are NOT working on CRUD, way more productive
py4
·5 か月前·議論
Let's say you want to make an architectural change. There are two options:

1. Ask AI to come up with the different options and let you review it

2. You think about the options and ask AI for feedback

#1 is much faster but results in atrophy (you are not critically coming up with the architecture changes)

#2 uses your and AI skills but it's gonna be slower.

which one will you choose? currently i'm doing #1
py4
·5 か月前·議論
if it's able to do the interesting/engaging part faster than me, i don't see why i should not outsource to it (The same argument as why use LLM-assisted programming at all, you don't want to miss the productivity boost)