Peterwa

Enginner, 23, DeFi, Crypto

[Telegram Messenger @telegram]

@WhatsApp stuff that happened in 2014
» this meme
» iPhone 6
» usernames on Telegram

[WhatsApp @WhatsApp]

your phone number is personal and sometimes you want to connect without handing it over. that's why we're introducing usernames for WhatsApp.

starting this week, you can reserve a username to use later this year when we launch the feature. It takes just a few seconds, make sure you have the latest version of WhatsApp and then go to Settings > Account > Username.

[AdnaanJnr @AdnaanJnr]

Vhagar’s size compared to the other dragons’ sizes

[Arpit Bhayani @arpit_bhayani]

AI has made it easier to write optimized code on day 0, but it is creating a new problem...

Ask an LLM to write some code, and it will often reach for the most "correct" version - caching, batching, async, configurable strategies. Code that looks staff-level from the first commit.

If you keep probing it to optimize further, it will come up with such absurd optimizations that you may not have even heard of.

Most of these optimizations solve a problem you do not have yet. A function handling 50 records a day does not need a connection pool, a retry queue, and a pluggable backend. It needs to work and be readable.

To be honest, we engineers have always over-engineered, but AI has lowered the cost of writing the complex version to nearly zero, so the lazy default (write the simple thing first) no longer feels lazy. It feels like leaving performance on the table.

The result is codebases full of abstractions nobody asked for. Interfaces with a single implementation. Generic configs for cases that will never change. Vector operations and macros no one asked for.

The skill that matters now is not writing optimized code. It is knowing when to stop optimizing. Premature optimization used to be expensive enough that most people avoided it by default. Now it is one prompt away.

Good engineering judgement is about knowing which optimizations the problem in front of you actually needs.

Hope this helps.

[vignesh @619ssvignesh]

What if train tracking is fun to use ✨

Built with typescript + cursor

[Peterwa @PeterGriffins07]

@anurag__kochar What's that keyboard?

[ibo @ibocodes]

my entire 2026 stack runs on cloudflare and I pay $5/month for it

- workers (compute)
- d1 (sql db) + better auth
- kv (cache)
- r2 (object storage)
- queues (background jobs)
- hyperdrive (db acceleration)
- email routing (sending)
- + waf & ddos built-in

[Peterwa @PeterGriffins07]

@vidit_odedra Hmm

[Peterwa @PeterGriffins07]

@zuhaitz_dev You thought people will pay for this ..

[Peterwa @PeterGriffins07]

@kmeanskaran @Ayushihihaha

[Asmit @coolcoder56]

Amazon SDE-1 Interview Experience for 46 LPA

Timeline

28 Jan – OA
5 Feb – Hiring Interest Form
25 Mar – Recruiter call for interview scheduling
27 Mar – Technical Round 1 & Technical Round 2
15 Apr – Hiring Manager Round
30 May – Bar Raiser Round
Final Result – Rejected!

Someone shared his interview experience with Amazon for SDE - 1 position online.

Online Assessment :

Solved both coding questions.
Completed the Work Style and Behavioral Assessment.

Technical Round 1
Questions

Number of Islands
Median of Data Stream
Solved both optimally with discussion on time/space complexity and follow-ups.

Technical Round 2
Questions

Minimum Cost to Connect Ropes
Divide students into 2 groups such that enemies are not in the same group (Bipartite Graph / Graph Coloring)
Solved and coded both.
One mistake

Initially said graph coloring complexity was O(V × E), then corrected it to O(V + E) after the interviewer challenged me.
After 12 days I received the invite for the Hiring Manager round.

Hiring Manager Round

HM joined about 5 minutes late.
Questions
Variation of Find All Anagrams
Minimum Cost to Combine Garlands (same concept as ropes)
Reached optimized solutions for both.

Mistakes
Couldn't properly derive the brute-force complexity for the first problem.
Code for the first problem became a little messy.
Missed an overflow edge case in the second problem until the interviewer hinted about maximum values, after which I realized long should be used instead of int.

Then came the longest wait.
I sent 6 follow-up emails without any response. Eventually I assumed my journey had ended because I didn't feel my HM round was perfect.
But after exactly 40 days, I unexpectedly received the invitation for the final Bar Raiser round.

Bar Raiser Round (1 Hour)

This round was almost entirely focused on Leadership Principles.
Topics discussed:
A challenge I solved
Missing a deadline
A problem I identified myself
Simplifying a process
The interviewer challenged me heavily on:

Whether my first story was actually challenging
Rate limiting decisions
Geofencing approach
Trade-offs and decision making
The first 15–20 minutes felt quite intense because of continuous probing, but the discussion became much smoother afterward and lasted the full hour.
Looking back
Things that may have gone against me:

My first BR story may not have demonstrated enough complexity.
My stories didn't have massive scale or business impact.
I had a few minor technical mistakes during the interview loop.
Things I'm happy about:
Solved every coding question.
Reached optimal approaches on my own.
Didn't require coding hints.

Answered BR follow-up questions throughout the interview.
Owned my mistakes instead of trying to defend them.
Biggest learnings
Keep talking through your thought process—interviewers evaluate reasoning, not just answers.
Avoid long silences—even partial ideas are better than saying nothing.

Show confidence in your decisions, backed by reasoning.
Own mistakes immediately—it builds credibility.
Clearly establish the challenge before explaining your solution.

Understand the "why" behind every metric or impact you mention.
Prepare Leadership Principles as seriously as DSA.
One imperfect round rarely decides the outcome—the overall pattern matters.

Don't judge your performance based on your own feelings after the interview.
Control what you can: preparation, communication, attitude, and consistency.

Although I didn't receive an offer, reaching the final Bar Raiser round at Amazon was an experience.

[𝑝𝑢𝑟𝑒 @purelivn]

parrot's raincoat

[Peterwa @PeterGriffins07]

@JasgunChandnani @shravlmao It's get compiled time out , sometimes with bigger pages

[Peterwa @PeterGriffins07]

@JasgunChandnani Yeah been there , done that..

[Peterwa @PeterGriffins07]

@VittoStack Would love to join and connect with like minded and learn from best security reseachers 👋

[Peterwa @PeterGriffins07]

@abhijitwt Yes share workflow

[Peterwa @PeterGriffins07]

@dpratyush02 @vidit_odedra Thanks mate , got new shopping shop

[Peterwa @PeterGriffins07]

@vidit_odedra Not bad but so so much discount here and there? Is this home setup?

[movie tweets @lauren_w67]

The Good Dinosaur