Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
avikalp
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
Is it better to have fewer components?
(alokit.substack.com)
2 points
by
avikalp
4mo ago
|
1 comments
2.
▲
by
avikalp
4mo ago
The AI applications that I build have a core loop that does most of the work, and then most of the other components are designed to make sure that the output is actually correct and helpful. The components that I use for that -- are they al
3.
▲
AI Evaluation Is Biased – By Design
(alokit.substack.com)
2 points
by
avikalp
4mo ago
|
0 comments
4.
▲
Does anyone in your organisation own "correctness" in your AI products?
(alokit.substack.com)
4 points
by
avikalp
4mo ago
|
0 comments
5.
▲
by
avikalp
4mo ago
I have always felt that my orchestration is supposed to increase the reliability because that is what the pipeline is doing. Checking the work of the main agent and giving feedback. But this article seems to be arguing otherwise. That addin
6.
▲
Simpler Agent Orchestration WTF
(alokit.substack.com)
1 points
by
avikalp
4mo ago
|
1 comments
7.
▲
Expansion on DORA report's observation on individual vs. team productivity
(alokit.substack.com)
1 points
by
avikalp
4mo ago
|
0 comments
8.
▲
Show HN: Byok-relay – self-hosted proxy for BYOK LLM apps without CORS issues
(github.com)
1 points
by
avikalp
5mo ago
|
0 comments
9.
▲
AI made writing code fast. Understanding it is still slow
(vibinex.com)
3 points
by
avikalp
5mo ago
|
0 comments
10.
▲
Why reviewing code doesn't mean understanding it
(vibinex.com)
5 points
by
avikalp
5mo ago
|
0 comments
11.
▲
Move faster, wait less: Improving code review time at Meta
(engineering.fb.com)
6 points
by
avikalp
1y ago
|
0 comments
12.
▲
by
avikalp
2y ago
This is only true for "development branch" CRs/pull requests. The whole is greater than the sum of the parts. Every small change in the feature that you are building might make complete sense, so every dev-to-feature branch p
13.
▲
by
avikalp
2y ago
I agree with you 100%. In the maker-checker process, if we are imagining a future where AI will be writing/editing most of the code, the AI-code-review tools will need to integrate within its agentic process. And the job of a better co
14.
▲
by
avikalp
2y ago
What you are saying is true, and this is the feedback I hear every time I talk to a small team of developers (generally fewer than 15 developers). At this stage, you don't need "another set of eyes" because it is not that big
15.
▲
by
avikalp
2y ago
I have had a similar discussion with a fellow On-Deck Founder, and here is where we reached: - More than being "good enough", it is about taking responsibility. - A human can make more mistakes than an AI, and they are still the m
16.
▲
by
avikalp
2y ago
I'm sorry, I didn't mean it to be an ad. I have been interviewing engineering leaders for months, and my startup idea is born out of it. I don't have the product ready yet - it is evolving based on what I am learning. I just
17.
▲
The AI Code Review Disconnect: Why Your Tools Aren't Solving Your Real Problem
(avikalpg.github.io)
43 points
by
avikalp
2y ago
|
33 comments
18.
▲
by
avikalp
2y ago
This is an open-source project. Link to the source code: https://github.com/avikalpg/typing-analyst
19.
▲
Show HN: Typing Analyst – Constantly shows typing speed and accuracy on macOS
(avikalpg.gumroad.com)
1 points
by
avikalp
2y ago
|
1 comments
20.
▲
by
avikalp
2y ago
Wow, this is a very well-written article. I have experienced a lot of this in my own experience as a software developer. This makes me wonder, the concept of pair programming has been around for a very long time. And yet, pull requests have
21.
▲
by
avikalp
2y ago
I have heard the same as well. These days, I am thinking about how AI code gen can be affecting this. When AI is writing code, you can't assume yourself to be the pair programmer, because your speed is not even close to the AI's.
22.
▲
by
avikalp
2y ago
In the "Knowledge Sharing" section of the article, the author says that "Distributed Practice" is one of the most effective ways to learn, and yet says that code reviews are not effective ways of knowledge sharing. Isn&#
23.
▲
by
avikalp
2y ago
If 42% of the comments on a pull request are related to increasing the understandability of the code, can we assume that just understanding the proposed code changes consumes the majority of the time spent on reviewing a pull request?
24.
▲
Understanding Code Understandability Improvements in Code Reviews
(arxiv.org)
4 points
by
avikalp
2y ago
|
1 comments
25.
▲
by
avikalp
2y ago
I found this article today and thought it was very interesting.
26.
▲
by
avikalp
2y ago
Wow, this looks very interesting. I saw the diagram of your own application and it looks more dynamic than the ones that I am generally used to at work. I am curious about the motivation behind this project. What experiences triggered you t
27.
▲
by
avikalp
2y ago
It is good that you are already thinking about it. My wife and I have separate bank accounts but we operate as a single entity. We are both completely aware of each other's incomes and expenses (we maintain a common expense manager).
28.
▲
by
avikalp
2y ago
Piano (keyboard) and Guitar. (Western classical training + pop songs) I have also learned an Indian keyboard instrument called Harmonium. (Hindustani classical training) And I love trying out new instruments :)
29.
▲
by
avikalp
2y ago
I am a bit confused about your stage as a product. When you say "get people to try out your product", I feel that you are building a new product and looking for early feedback - your first design partner. But then you say "of
30.
▲
by
avikalp
2y ago
Nice observation. I still use Google Pub/Sub in my application - I recently also gave a talk on how we use Pub/Sub for our use case in a GCDG event (GCDG stands for Google Cloud Developer Group). But now that I think about it, we
More ›