the token from the Authorization header, verifies the signature using the secret key, and only then forwards the request to the right microservice. If the token is invalid it never reaches the service at all. I wrote this code months ago but I was thinking of it as "authentication middleware" — today I understood it's actually a bouncer at the door, not a check inside the room. The decision to verify at the gateway level instead of each service was the right one — because if each service verified tokens independently, a bug in one service's auth logic could expose all the others. One gate is easier to secure than six. I just didn't know why until now over each service checking its own token because one gate is easier to secure than six
◆ Why Proof picked this
Joshna named what they left on the table: token expiry mid-session, refresh tokens untested. The entry shows a mind returning to old code and finding the reasoning it was missing. That is how engineers grow.
thought they were alternatives — pick one. Today I realised they solve different problems. Docker because I needed all 6 services to run identically on my machine without "works on my laptop" issues. Render because I didn't want to manage servers in production. The decision was always there — I just never named it while buildin
◆ Why Proof picked this
She had two config files and thought she had to pick one. Today she saw they answer different questions. Docker so the six services run the same on every machine. Render so she does not manage servers in production. Both, for different reasons. Then her own line: the decision was always there, she just never named it while building. That is what logging does. It turns a choice made by reflex into one you can see. And she did not stop at the win. She wrote what she skipped: she copied the docker patterns without reading them, tomorrow she reads them properly. The reasoning and the honesty, one entry.
used to manage all the cyber security threats and remediations to terminate them(under developmentGit hub: https://github.com/MITHULESH07/AI-powered-cyber-security-thread-intelligence-systemWeb app link: https://ai-powered-cyber-security-thread-in.vercel.app/
◆ Why Proof picked this
A good reference point for how to write a built log
The site seems to be broken UX wise. And wouldn't it be more efficient to do your semantic indexing via Tree Sitter and Chunking, or something akin to cAST?
over proper JSON true because that's sloppy API design that I don't want me or future colleagues to support.
◆ Why Proof picked this
Most decisions are about what to add. The hard ones are about what to refuse. every future colleague inherits the decisions you make. these choices as what not do do make you zero maintenance.
messy things this morning, four clear plans by evening. Best part: something I thought was a whole build turned out to be two lines — the fieldalready existed, I just wasn't searching the right name. Classic.Also made myself not jump into coding before the requirements were confirmed. Felt slow, but right.Quiet day. But the unknowns are gone. Tomorrow I build.
◆ Why Proof picked this
No code today and this is one of the best logs... A build he expected collapsed into two lines, because priya searched before she wrote. Great instinct to check before writing code. this Zero maintenance behavior.
moving fast because I'd like us to move fast and be correct rather than moving fast and breaking things.
◆ Why Proof picked this
Anyone can disagree. Few disagree knowing exactly what it costs them. This engineer named the cost, seeming resistant to change, and spoke anyway. Courage without awareness is recklessness. Courage with awareness is Zero Maintenance behavio
told me - Before touching figma, understand the problem context and then suggest me to work on UI part next. The exact mistake, I repeated a lot because of deadlines and being in some complex situations. Unfortunately, in the end - the mistake addressed sharply by my boss. Today, I realized and corrected my mistake, work for the value & the impact I create - not for the submission or working like you don't like the work.
◆ Why Proof picked this
Repeated mistake, named honestly. The shift from submission
to value is an engineer moving up the ladder in real time.
brainstorming, and practical discussions rather than only watching videos or reading blogs from friends who are already working in the content and branding field.
◆ Why Proof picked this
Action creates data that internalizes learning like nothing else. even failutres, infact failures helps us internalize lot more knowledge than simply studying/watching a subject.
a couple of solutions that we can try but for that I need to understand and verify how exactly deploys work and replace running code in production.
◆ Why Proof picked this
Animesh Ghosh , I would love to get this highlighted one day: just because it describes the psychological safety, But sending this request knowing you can choose not to.
experience made me go deeper into marketing and helped me gain more confidence and exposure.It also made me think more independently, take ownership, and understand how real work actually happens.Because of this journey, I’m learning skills and experiences that I believe will help me build my own company in the future.
◆ Why Proof picked this
This is gold. this is the bridge to growth for every individual. Express gratitude and grow with others.
if condition. "=" assigns a value, but "==" compares values.2. I wrote "digitalwrite()" instead of "digitalWrite()". Arduino is case-sensitive, so the capital "W" is important.
◆ Why Proof picked this
For an engineering student, explaining they are stuck at a fundamentals is a good sign. Articulation is an important skill. she has done it well.
placement prep over Continuing full placement-focused Java/corporate prep path... because I realized my natural strengths align more with communication, positioning, storytelling, and working with founders than pure repetitive coding roles
◆ Why Proof picked this
A college student thinking about positioning and founder branding instead of defaulting to placement prep. this is rare and we need more people like this mindset. they will thrive in the AI native era.
them where they are from Seth Godin's blog titled "In defense of popups"
◆ Why Proof picked this
Engineers reading Seth Godin is rare.
Most stay in their stack. You're reading about customers and attention.
That's the breadth that makes founding engineers.
Keep logging what you're reading outside code.
with the developer team, I will face a lot of good questions & points, I missed out. I learned this - Collaborating with founders & dev folks - would open a door for more clarity on the process. Improves the quality of the outcome. Importantly, the burnout decreases. Expectations matched perfectly.
◆ Why Proof picked this
Good reflection post. This is the journey in to collaboration at work
to stakeholders and founders. from What I’ve learned from my failures.
◆ Why Proof picked this
Learning extracted from failure with reasoning visible. Explains the mechanism: annotations prevent stakeholder misunderstanding and bias. Shadow shows attempted application and honest gap. This is how engineers turn mistakes into knowledge