Hacker News: abhashanand1501

New comment by abhashanand1501 in "Incident with Pull Requests, Issues, Git Operations and API Requests"

abhashanand1501 — Wed, 27 May 2026 12:56:36 +0000

as a github user, we are paying for the slow git operations through our github action minutes, if someone from GH is here, will you be compensating for it?

New comment by abhashanand1501 in "Why frozen test fixtures are a problem on large projects and how to avoid them"

abhashanand1501 — Tue, 09 Dec 2025 14:53:17 +0000

You should look into factory boy (in django). Been using it for 10 years. It helps with this situation.

Foofactory() will automatically setup all the foreign key dependencies.

It can also generate fuzzy data, although having fuzzy data has its own issues in terms of brittle tests (if not done correctly).

New comment by abhashanand1501 in "Latency Profiling in Python: From Code Bottlenecks to Observability"

abhashanand1501 — Tue, 09 Dec 2025 04:37:11 +0000

> The trading system reports an average latency of 10ms

Python is a bad choice for a system with such latency requirements. Isn't C++/Rust preferred language for algorithmic trading shops?

New comment by abhashanand1501 in "Catala – Law to Code"

abhashanand1501 — Sun, 07 Dec 2025 03:20:43 +0000

We really need this in India. There are 53 million cases which are pending in courts, with over 180k cases open for more than 30 years (see https://en.wikipedia.org/wiki/Pendency_of_court_cases_in_Ind...). It is estimated that more than 300 years will be taken to dispose of all cases.

If law code is a repository: 1. Each trial should be encoded into a law. 2. If the trial is already covered sufficiently in the codebase, and both parties agree to it result. Then case is solved. 3. If not, the new judgement leads to a "pull request" into the codebase.

New comment by abhashanand1501 in "Acme, a brief history of one of the protocols which has changed the Internet"

abhashanand1501 — Thu, 04 Dec 2025 02:32:47 +0000

Can someone explain why letsencrypt certificates have to be 90 days expiry? I know there is automation available, but what is the rationale for 90 days?

New comment by abhashanand1501 in "Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025"

abhashanand1501 — Tue, 02 Dec 2025 15:42:54 +0000

In different regions the price difference is different. In us-east there is a 20% difference, in ap-south it is 50%. You can check for fargate ecs pricing for example.

New comment by abhashanand1501 in "Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025"

abhashanand1501 — Tue, 02 Dec 2025 12:48:14 +0000

One of the easiest hack to reduce your AWS bills is to migrate from x86 to arm64 CPU. Performance difference is negligible, and cost can be upto 50% lower for arm machines. This is for both RDS and general compute (EC2, ECS). Would recommend to all.

New comment by abhashanand1501 in "So you wanna build a local RAG?"

abhashanand1501 — Sat, 29 Nov 2025 17:13:56 +0000

My advice - use same rigor as other software development for a RAG application. Have a test suite (of say 100 cases) which says for this question correct response is this. Use an LLM judge to score each of the outputs of the RAG system. Now iterate till you get a score of 85 or so. And every change of prompts and strategy triggers this check, and ensures that output of 85 is always maintained.

New comment by abhashanand1501 in "Confessions of a Software Developer: No More Self-Censorship"

abhashanand1501 — Sat, 29 Nov 2025 12:52:30 +0000

There are two possibilities

1. The getters and setters are not called anywhere in application logic. In that case, delete the getters / setters and get to 100%.

2. The getters and setters are called somewhere in the application logic. In that case, they should have already been covered in the test for the application.

There is really no excuse to not write tests to get to 100%.

New comment by abhashanand1501 in "Confessions of a Software Developer: No More Self-Censorship"

abhashanand1501 — Sat, 29 Nov 2025 10:17:37 +0000

> Am I suggesting 100% test coverage? No, I’m not suggesting it. I’m demanding it. Every single line of code that you write should be tested. Period.

This is from uncle bob. I hate the argument by people that 100% leads to "bad quality tests". Not doing it leads to bad quality code, people who don't care about quality of code, and hence dont write tests, suddenly start to care about quality of tests.

New comment by abhashanand1501 in "A triangle whose interior angles sum to zero"

abhashanand1501 — Sat, 29 Nov 2025 03:14:58 +0000

>In spherical geometry, the interior angles of a triangle add up to more than π. And in fact you can determine the area of a spherical triangle by how much the angle sum exceeds π. On a sphere of radius 1, the area equals the triangle excess

To all the flat earthers out there, this property can be used to find out earth is not flat, just by drawing a giant triangle on the surface, without leaving the earth. Historically, to prove the earth is round, people have relied on the sun shining directly overhead on wells in different cities. But this approach proves it without the need to refer the sun.

New comment by abhashanand1501 in "Tiger Style: Coding philosophy (2024)"

abhashanand1501 — Fri, 28 Nov 2025 16:56:52 +0000

I like the 100% philosophy for coding:

1. 100% code coverage 2. 100% branch coverage 3. 100% lint (without noqa) 4. 100% type check pass(for python/js) 5. 100% documentation coverage 6. All functions with complexity less than 5. All functions with no of lines less than 70. All files with number of lines less than 1000.

These make code high quality, and quality of life is directly proportional to qualify of your code.

New comment by abhashanand1501 in "SQLite as an Application File Format"

abhashanand1501 — Fri, 28 Nov 2025 16:44:38 +0000

We are developing using sqlite to transfer configurations from uat to production environment. Since the configurations are already saved in a postgres table in uat, moving some configs from uat to production an sqlite file is very easy. since it's a binary format, we are also saved from any inadvertent edits by people doing production deployment.

Also, another usecase is to export data from production to uat for testing some scenarios, it can be easily encoded in a sqlite file.

Enforcing 100% code coverage is a bad idea, but you should do it anyway

abhashanand1501 — Mon, 24 Nov 2025 16:20:45 +0000

Article URL: https://substack.com/home/post/p-179830435

Comments URL: https://news.ycombinator.com/item?id=46035748

Points: 1

# Comments: 0

New comment by abhashanand1501 in "How we decreased GitLab repo backup times from 48 hours to 41 minutes"

abhashanand1501 — Sun, 08 Jun 2025 15:35:14 +0000

In fact O(n^2) is exponentially more than O(log n).

New comment by abhashanand1501 in "How we decreased GitLab repo backup times from 48 hours to 41 minutes"

abhashanand1501 — Sun, 08 Jun 2025 15:33:55 +0000

Lot of comments complaining that going from O(n^2) to O(log n) is not an exponential improvement, but it is indeed an exponential improvement. In fact O(n) is exponentially more than O(log n).