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

fullstackwife

113 カルマ登録 7 年前
Currently working on a coding assistant: https://github.com/gtanczyk/genaicode

コメント

fullstackwife
·6 日前·議論
Your take is very interesting, but please do not forget that pirating games is a crime.
fullstackwife
·5 か月前·議論
Why not build it as a web app and play via browser?
fullstackwife
·5 か月前·議論
Your technical skills are shaped by market demand, and they always have been.
fullstackwife
·6 か月前·議論
Should votes get invalidated after major change in the ongoing PR?
fullstackwife
·6 か月前·議論
for example driverless taxis, which is an application of AI that most of us really want
fullstackwife
·6 か月前·議論
Since when "AI" exclusively implies LLMs only?
fullstackwife
·7 か月前·議論
cost of e2e task resolution should be cheaper, even if single inference cost is higher, you need fewer loops to solve a problem now
fullstackwife
·7 か月前·議論
human process is the understanding that the mistakes will make people die
fullstackwife
·7 か月前·議論
yeah, in practice: would you like to onboard a Boeing 747 where some of the bugs were patched by some agents,

what is the percentage risk of malfunction you are going to accept as a passenger?
fullstackwife
·7 か月前·議論
What works: delegating non ambiguous tasks, let them happen in async, while supported by harness of preexisting automated tests, and established project conventions

What does NOT work: I have no idea how to do sth, and I hope agentic coding will solve my problem.

Think "Eisenhower matrix":

- X: Ambigous <-> Trivial

- Y: Can wait <-> Urgent

Urgent&Ambigous => Agentic Coding is useless, and an act of desperation

Can wait and at least non amibogus => Agentic Coding is perfect fit
fullstackwife
·9 か月前·議論
Think chefs at top restaurants for example: washing hands is something obvious, no need to get any customer infected with fecal bacteria in order to convince the restaurant management for investing into soap (hygiene takes time, you could serve additional customer!)

It is one of career progression milestones for a programmer when they can set a bar for their craftsmanship themselves. Successful SWE is someone who got hired at a team which does not require this kind of education. A team where this type of engineering hygiene is obvious like breathing.
fullstackwife
·10 か月前·議論
Argumentum ad hominem - seriously, team! we can do better than that!
fullstackwife
·11 か月前·議論
Text rendering on canvas is currently a huge pain, custom layouting code, lack of accessibility, so I'm happy to see this!
fullstackwife
·昨年·議論
you are right, but please don't forget they were publishing some benchmark results which were great
fullstackwife
·昨年·議論
I was initially enthusiastic about DS3, because of the price, but eventually I learned the following things:

- function calling is broken (responding with excessive number of duplicated FC, halucinated names and parameters)

- response quality is poor (my use case is code generation)

- support is not responding

I will give a try to the reasoning model, but my expectations are low.

ps. the positive side of this is that apparently it removed some traffic from anthropic APIs, and latency for sonnet/haikku improved significantly.