AWS Builder Center
TaxSaathi, Day 1: Building on AWS for the first time, what I learned.

TaxSaathi, Day 1: Building on AWS for the first time, what I learned.

Quick context: it's a tax calculator for people like me, first-time earners who've never filed and don't know what 80C means. Building it for First Commit, all on AWS.

Series: First Commit Hackathon By WeMakeDevs (2 articles)

  1. 1
    TaxSaathi, Day 1: Building on AWS for the first time, what I learned. This article
I made a new AWS account yesterday morning and immediately almost shot myself in the foot by working as root instead of making a separate IAM user. Small thing, caught it early, moved on. But it set the tone for the day, which was basically: catch the mistake before it becomes a problem, over and over.
The one that actually annoyed me was my .gitignore. Pushed it, checked GitHub, saw it sitting there as a file literally named "gitignore" no dot. Which means it was doing absolutely nothing. I'd built out this whole folder structure, felt good about it, and then found out the one file meant to stop me from accidentally leaking secrets to a public repo wasn't even being read by git. Fixed it, but that was a genuinely dumb near-miss and I don't love that I made it.
Then the caching thing. I fixed the repo structure, checked GitHub, and it looked exactly like before I fixed it. Checked again. Same. I started genuinely doubting whether my push had worked at all, second-guessing commands I'd already run three times. Turned out it was just a stale cache on the fetch side, nothing wrong on my end, but for about ten minutes I was convinced I'd broken something.
The thing I'm actually proud of: I built a feature yesterday that I ended up deleting. It was supposed to tell you "invest this much more in 80C and it'll flip you from New regime to Old regime." Built it, tested it, felt good. Then I actually ran the numbers across a spread of incomes and realized it basically never fires New regime's rates are just too much better once you're past its rebate threshold, no realistic deduction closes that gap. So the whole feature was quietly dead on arrival for almost every real user. Would've been easy to just... not check that carefully and ship it anyway. Glad I didn't.
Also learned that if you set up your Lambda functions through AWS SAM instead of clicking around in the console, and you don't explicitly ask for extra permissions, you get the locked-down version by default. I didn't know that going in and it made the whole "don't give things more access than they need" thing feel less like a chore and more like just... how it works if you don't get lazy about it.
Bedrock access for my region is still stuck in approval, which is out of my hands and mildly frustrating because it's the one piece I actually can't test for real yet. Built it anyway, tested everything except the actual model call using a fake response standing in for the real one. Feels a bit like building a car and testing everything except whether the engine turns on. I'll know tomorrow.
Today's frontend. I want the tax slabs to look like actual terrain, with a real visible drop where the rebate cliff hits, so it's something you see instead of something you have to read a warning about. No idea yet if that's going to work or if I'm overscoping on day 2 of a weekend project. We'll see.
#BharatBuilds

Series: First Commit Hackathon By WeMakeDevs (2 articles)

  1. 1
    TaxSaathi, Day 1: Building on AWS for the first time, what I learned. This article
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article