Suzanne Daniel Thomas retweeted
giving away 2 courses today on children's day!
1. Plus Core (12m) by TakeUForward, worth ₹5,700
2. TLE Prime PRO (36m) by TLE Eliminators, worth ₹5,400
i've solved the A2Z sheet twice and 100-200 problems from CP31. both played a huge role in helping me land my current job.
this is my small way of giving back to @Priyansh_31Dec , @striver_79 , and the community.
to participate:
- follow me and retweet so this reaches more people!
- reply "TUF" or "TLE" depending on which course you want (choose only one).
winners announced at 9 PM IST today. will try to purchase both tonight before the children's day sale ends! good luck!
spent two days fixing a bug that didn't exist.
most of my computed scores were zero; not because scoring broke, but because the open data never tagged that attribute in my region.
hence the lesson: verify the data sets before auditing the code that reads it.
10
201
AbridgeAI began from here :)
Thank you to @agent_wrapper and the entire team for this hack that lead us to this idea 🙌🏼
Built AbridgeAI with Agent Orchestrator
It turns rough project ideas + GitHub signals into feasibility insights, a builder scaffold, and a scoped first PR task for AO.
Thanks @aoagents @agent_wrapper and huge thanks to @ruchirajags for building this with me!
#agentorchestrator
5
402
2 hours to built at HacktoberFest; any one idea and use every sponsor’s tools... We built upon AbridgeAI and won Best Open Source Project 🏆
A win, lovely merch, and a very tired brain. It was worth every one of those 2 hours.
3
27
588
Exploring Jarvislabs Token Factory at Hacktoberfest Hack Day Pune! Tested DeepSeek V4.1 Flash for code explainers, debugging & SQL. Key lesson: the prompt shapes response quality as much as the model. #Jarvislabs #TokenFactory
@TrainWitShubham @CNCGPune @temporalio
1
3
207
Getting ready for Hacktoberfest's Hack Day Pune on 25th October with Cloud Native Pune and Major League Hacking. Trying Kepler by RubixKube, an AI IDE; runs the commands, reads the logs and asks before it touches anything.
#Hacktoberfest #HackDayPune #CloudNativePune #MLH
1
10
236
your authenticator app and google’s server never talk to each other, they just agree on what time it is. that’s the whole trick behind those 6 digit codes, and it’s why NTP quietly holds a lot of trust together.
cookies, tokens, certs and otp codes all expire on a clock, and the clock is the one thing we never really think about
1
7
237
git Things I Wish I Knew #12: 𝗮𝗱𝗱𝗲𝗱 𝘁𝗼 .𝗴𝗶𝘁𝗶𝗴𝗻𝗼𝗿𝗲, 𝘀𝘁𝗶𝗹𝗹 𝘁𝗿𝗮𝗰𝗸𝗲𝗱
.gitignore only works on files Git hasn’t seen yet. 'Tracking' means Git already knows about a file and is watching for changes. A file becomes tracked when you git add and commit it.
Replying to @Suzanne__e
use .gitignore for things the whole project should skip, like node_modules, .env and build output. use exclude for things only you have, like personal notes or your own editor files. neither stops git from tracking a file that’s already committed.
4
195
continuing this after a while :)
git things I wish I knew #11: 𝗴𝗶𝘁𝗶𝗴𝗻𝗼𝗿𝗲 𝘃𝘀 𝗲𝘅𝗰𝗹𝘂𝗱𝗲
.gitignore is committed, so your whole team gets the same rules.
.git/info/exclude stays on your machine only and is never pushed. Good for editor configs and scratch files.
Git Things I Wish I Knew #10: 𝗪𝗼𝗿𝗸𝗶𝗻𝗴 𝗗𝗶𝗿𝗲𝗰𝘁𝗼𝗿𝘆, 𝗦𝘁𝗮𝗴𝗶𝗻𝗴 𝗔𝗿𝗲𝗮, 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆
Working Directory: Where you edit files.
Staging Area: Where git places puts changes before commit.
Repository: Where git commit saves changes in history.
1
7
307
reading more on cookies to understand that they are a browser specific mechanism. The whole system of Set-Cookie from the server, the browser automatically storing it, the browser attaching it on future requests; that automatic behavior is something browsers were built to do.
Replying to @Suzanne__e
the catch is that HTTP was never built to remember anyone. every request arrives as a stranger and never changes no matter. the thing keeping you logged in is a cookie the server handed your browser once and re-sent it on every request since.
2
4
278
Mobile apps and non browser clients don't have this. If you're building a mobile app that calls a backend API, there's no browser sitting in the middle automatically storing and re sending cookies for you. You can still use cookies in these contexts but it gets clunky..
1
1
116
a set-cookie isn't the session side of this, it's just the delivery method. what actually decides session based vs JWT is the type of id sitting inside that cookie.
that cookie only proves you're logged in, it says nothing about how strong your login is once it's gone. picking the wrong one means either you can't kick out a compromised account fast enough, or you overbuilt for a problem you never had.
1
4
247
a random id like session_id=abc123 that the server looks up in a database, that's session based auth riding on a cookie. a full JWT sitting inside that same cookie instead, that's JWT based auth using the identical delivery mechanism. same envelope, different things it can carry.
1
1
147












