T
3.8K posts


@WhiteHouse Typical USA behaviour !!
First, create a mess and ask others to clean up
English

@nickfuentes100 @0xlelouch_ Yes and, as it stands, seasoned industry professionals don't usually have the time or energy to do all of that or more while also being highly performant at work and also have a bit of a life. The whole hiring/evaluation process if effed. So, they want you to jump to get noticed.
GIF
English

@mistaa_t @0xlelouch_ Fr he is such a clown
He expects a fresh grad to surpass CTO
Peak grindjeetry
English

Reviewed the profile of a final-year engineer graduating in April 2026, positioning himself as a backend/distributed systems engineer with public proof of work in Go, systems programming, and technical writing.
Here is my hiring manager + recruiter view of it:
The good:
This profile has something most student profiles do not have: positioning.
I know what this person wants to be.
Backend engineer.
Systems leaning.
Comfortable with Go, TypeScript, Python, Postgres, Redis, Nginx.
Interested in database and systems internals.
That clarity already puts him ahead of many 2026 grads.
The projects are strong for this stage.
A distributed rate limiter in Go is much better signal than another CRUD dashboard.
A crash-safe key value store built on top of a custom WAL engine is also strong.
Even if these are not production-grade databases, they show the right curiosity.
These are the kinds of projects that make backend and infra teams pause and take a second look.
The blog section is a huge plus.
Writing about building a DHT from scratch using Kademlia tells me two things:
this person learns deeply,
and this person can explain deeply.
That matters a lot for good engineering teams.
The portfolio story is coherent.
Distributed systems.
Rate limiting.
WAL.
DHT.
Go.
Systems internals.
This is not random exploration.
This looks like deliberate taste.
From a recruiter side, this is the kind of candidate who can be pitched well for backend platform, infra-leaning product teams, database-adjacent roles, or strong startup backend roles.
---
The bad:
Right now this is a strong website profile, but not yet enough proof by itself.
Good themes and hard project names create interest.
But hiring decisions still need depth proof.
I would want to see:
benchmarks,
architecture diagrams,
concurrency design,
failure handling,
persistence guarantees,
replication details,
tradeoffs made,
and what exactly was built from scratch vs borrowed from libraries.
The wording is clean, but a little generic in places.
“Comfortable with many different tech stacks” is okay, but weaker than showing exact competence through outcomes.
Strong candidates should make the proof do the talking.
The portfolio seems very systems-heavy, which is good, but I do not yet know whether this person can also ship regular backend product work.
Can he build APIs?
handle auth?
work with queues?
own deployments?
write tests?
debug production issues?
Many teams hire for boring real-world backend first, then reward systems depth later.
There is also no visible work experience in what you shared.
That does not kill the profile for a 2026 grad, but it means the projects must carry a lot more weight.
Internships, freelance work, open source contributions, or even one deployed real-user product would strengthen this a lot.
---
The ugly:
The biggest risk with systems-focused student profiles is this:
they look intellectually impressive, but teams are not sure if the candidate can deliver in messy product environments.
A lot of students build mini databases and rate limiters.
Far fewer can explain production tradeoffs under pressure.
Even fewer can join a team and improve a real service in week one.
So the ugly truth is:
if this person cannot defend the internals deeply in interviews, the whole profile falls apart very fast.
A WAL engine and a distributed limiter sound impressive.
But they also invite very sharp questioning.
Locking strategy.
crash recovery.
fsync decisions.
consistency model.
sharding.
token refill logic.
hot key issues.
Redis coordination.
time drift.
fairness.
benchmarking method.
memory usage.
If those answers are weak, the profile starts looking like branding over depth.
Another ugly part:
this profile may be too niche if applied blindly.
Many recruiters at mass-market companies will not understand why this is strong.
They may prefer React internship plus one SaaS clone over a WAL engine.
That does not mean the profile is bad.
It means the candidate must target the right companies.
If I were hiring:
I would absolutely give this person an interview for backend intern, new grad backend, or systems-leaning roles.
Especially if my team values fundamentals over framework buzzwords.
I would be interested because the taste is rare.
Most grads say “full stack”.
Very few intentionally build around distributed systems.
That itself is a signal.
---
But I would test for two things very hard:
Can this person actually go deep technically?
Can this person also do practical backend engineering in normal production codebases?
If I were recruiting:
I would package this candidate as:
2026 new grad backend engineer with unusually strong distributed systems interest and public technical proof of work in Go.
That is a much better story than generic “software developer”.
I would also tell him to add one or two real-world proof points:
internship,
open source repo contributions,
benchmark numbers,
deployed demos,
or a project used by actual users.
---
Final verdict:
This is a high-signal profile.
Probably stronger than most 2026 graduate portfolios for backend roles.
The taste is good.
The focus is good.
The technical direction is good.
But now it needs one more layer:
proof of execution in real-world environments.
Systems curiosity gets attention.
Production credibility gets offers.
Big lesson from this profile:
Random projects show effort.
Coherent projects show taste.
Defensible depth is what gets strong backend roles.
English

@IamKyros69 Them, group think San Fran'ers never heard of the hot hand fallacy.
youtube.com/watch?v=Pxr_Fz…

YouTube
English

@MeghUpdates There was no humiliation. Quit blowing things out of proportion.
English


🚨BREAKING: Ripple CEO Says “FIVE YEARS FROM NOW YOU’RE GOING TO BE VERY HAPPY” — Reveals XRP ETFs Are Already Being Used as Lending COLLATERAL 😳🔥
During XRP Australia 2026, @bgarlinghouse addressed the recent $XRP price weakness and crypto market sell-off. 👀
“I frankly don’t understand why some of that is happening, because I think that we’re set up to have a REALLY, REALLY STRONG YEAR.” 🚀
@bgarlinghouse said part of the reason $XRP continues to stand out is PENT-UP DEMAND finally being unlocked across the ecosystem.
“You’re starting to see institutions using [XRP ETFs] as lending collateral.” 🤯
That’s a BIG deal. 🤑
Despite Brad's frustration with $XRP price, he pointed out $XRP has still outperformed MAJOR cryptos like $BTC (-22%), $ETH (-31%), and $SOL (-30%). 📈
“FIVE YEARS from now… you’re going to be VERY happy.” 😳🔥
@bgarlinghouse also said more of the crypto industry is starting to realize Ripple was EARLY — and RIGHT.
“Most of crypto has kind of come around and been kind of like, oh, Ripple was right.” 👀
English

XRP: Play the Long Game
Institutional adoption isn't coming it’s here. New financial giants are coming on-chain almost daily.
The Outlook:
• 5-Year Goal: Brad Garlinghouse says investors will be in a "very happy place" in 5 years.
• The Target: He predicts a $5T+ total crypto market cap as real utility takes over.
• The Strategy: Zoom out. Institutional
structural change is a 10-year journey, not a 1-year trade.
English

🚨Researchers just found something in birdwatchers' brains that explains why the rest of us feel perpetually exhausted no matter how much we rest.
Your brain was never designed for the world you're currently living in.
Every notification, every scroll, every open tab, every conversation happening simultaneously across five different apps — your nervous system is processing all of it as low-grade threat. Not dramatically. Not in a way you'd notice moment to moment. But underneath your conscious awareness, your threat-detection architecture is running constantly, scanning for danger in an environment that delivers synthetic urgency at a rate no human nervous system in history has ever had to manage.
The result is a specific kind of exhaustion that sleep doesn't fix. You wake up tired. You finish a vacation and feel like you need another one. You sit down to do one thing and your attention fractures within minutes without you choosing to let it. Willpower isn't the problem. The hardware is genuinely overtaxed.
Birdwatching, of all things, turns out to be one of the most precisely calibrated antidotes to this that exists in the natural world. And understanding why requires understanding something most people have never heard of: Attention Restoration Theory, developed by psychologists Rachel and Stephen Kaplan in the 1980s.
The Kaplans identified two completely different attentional systems in the human brain. The first is directed attention — the kind you use to write emails, solve problems, make decisions, have difficult conversations. It's effortful, voluntary, and finite. It depletes. Use it long enough without rest and you get what the Kaplans called directed attention fatigue: shortened fuse, poor decisions, inability to concentrate, emotional dysregulation. Sound familiar?
The second system is involuntary attention — the kind that activates when something in your environment effortlessly captures your focus without you deciding to pay attention. A flicker of movement in peripheral vision. An unexpected sound. A pattern that doesn't quite fit the background. Your brain orients toward it automatically, below the level of conscious effort, and the directed attention system gets to rest while the involuntary system takes over.
Natural environments are almost uniquely engineered to trigger involuntary attention constantly — and at just the right intensity. A bird moving through branches activates your visual tracking system. Its call pattern engages your auditory cortex in a way that's stimulating without being alarming. The unpredictability of when and where it will appear next keeps your attention engaged without demanding effortful concentration. You're not trying to pay attention. You can't help it. And while that effortless engagement is happening, the cognitive machinery you've been flogging all day quietly restores itself.
This is what researchers call "soft fascination" — engagement that absorbs attention without consuming cognitive resources. It's the precise opposite of doom-scrolling, which delivers constant stimulation while simultaneously demanding rapid processing, comparison, emotional reaction, and decision-making. Social media feels like rest because it requires no physical effort. Neurologically, it's directed attention in a costume.
The autonomic nervous system piece of this study is where it gets genuinely striking. Your autonomic nervous system has two branches that are constantly negotiating control of your body. The sympathetic branch — fight-or-flight — accelerates heart rate, sharpens threat focus, redirects blood to muscles, suppresses digestion and immune function. The parasympathetic branch — rest-and-digest, or calm-and-recover as the study puts it — does the opposite. It slows the heart, deepens breathing, activates digestion, runs cellular repair, consolidates memory, regulates emotion.
Modern life is a sustained sympathetic state. The threats aren't predators. They're deadlines and social comparison and financial uncertainty and information overload — none of which you can sprint away from, but all of which your nervous system treats with the same basic chemistry it evolved to handle lions with. The adrenaline has nowhere to go. The cortisol accumulates. The parasympathetic system never fully takes over because the environment never fully signals safety.
What's different about birdwatching as a parasympathetic activator is the specificity of why it works at a biological level. Human beings co-evolved with birds for millions of years. Before we had weather apps, birds told us whether a storm was coming — their behavior changes hours before pressure drops. Before we had security systems, birds told us whether a predator was nearby — their alarm calls and sudden silence are among the most reliable threat signals in any ecosystem. The phrase "dead silence in the forest" isn't metaphorical. When birds stop, something dangerous is present.
Your nervous system still speaks this language fluently. When birds are present, calling, moving normally, foraging — your brain interprets that as genuine environmental safety information. Not symbolically. Chemically. The parasympathetic system receives a signal that the environment has been cleared by some of the most sensitive threat-detection organisms in it. Your shoulders drop. Your breathing slows. Your heart rate variability — one of the most precise markers of parasympathetic tone and overall health — improves.
A 2022 study out of King's College London found that seeing or hearing birds was associated with improved mental wellbeing that lasted hours beyond the encounter itself.
The effect was present even in people with depression.
Researchers tracking moment-to-moment mood in real time found that bird encounters produced measurable wellbeing improvements regardless of other environmental factors — and crucially, regardless of whether the person considered themselves a "nature person."
The attention network strengthening the new study identifies goes even deeper than restoration. The default mode network — the brain's baseline activity during unfocused rest — is increasingly understood to be critical for creativity, self-reflection, empathy, and long-term planning. Chronic directed attention fatigue suppresses it. You stop daydreaming. You stop having ideas in the shower. Your inner life gets quieter in a way that feels like efficiency but is actually depletion.
Birdwatching, by toggling between soft fascination and genuine rest, allows the default mode network to activate properly. The irregular rhythm of it — moments of alert attention when a bird appears, followed by quiet waiting — mirrors the kind of natural attentional cycling the brain evolved to operate within. You're not forcing focus. You're not forcing rest. You're doing exactly what your brain was built to do in an environment it spent millions of years calibrating to.
The tragedy is that we look at birdwatching and see a hobby for retirees. We see binoculars and field guides and a demographic associated with slowing down.
We don't see what we're actually looking at — one of the most neurologically sophisticated recovery tools available to a species that has constructed an environment almost perfectly designed to destroy its own attention.
The birds were always telling us something.
We just stopped listening.
The Curious Tales@thecurioustales
🚨 NEW STUDY: Birdwatching strengthens attention networks in the brain - strengthening the body’s calm-and-recover state.
English

@aakashgupta All I read was have no life..just build build build, corporate slave.
English

Two opposite movements are happening in tech hiring right now and they're converging on the same point.
Engineers are building portfolios. After mass layoffs in 2023-2024, senior engineers realized that a resume listing "Led architecture for payments platform" doesn't differentiate when 500 other laid-off engineers say the same thing. So they started building personal sites, writing blog posts, and creating case studies. They borrowed the PM playbook: show your thinking, not just your output.
PMs are building GitHubs. After watching AI transform every PM interview from "describe your process" to "show me what you've built," PMs realized that a resume listing "Launched feature that increased retention 15%" doesn't differentiate when the interviewer wants to see you actually ship something technical. So they started building repos, committing code with AI tools, and contributing to open source. They borrowed the engineering playbook: show working output, not just your thinking.
Both groups are converging on the same insight: proof of work beats proof of credentials. A GitHub repo with a working feedback clustering tool tells a hiring manager more about a PM than a bullet point about "leveraging data to drive product decisions." A portfolio case study showing an engineer's architectural reasoning tells a hiring manager more than a line about "designed scalable systems."
The PMs who figure this out fastest have a two-year head start. 24% have a GitHub today. That number will be 60%+ by 2028. The early movers get the differentiation. The late movers get table stakes.
Aakash Gupta@aakashgupta
Only 24% of PM candidates have a GitHub. Every PM I placed at OpenAI, Anthropic, Meta AI last year had one. I wrote the first guide on how to build yours: news.aakashg.com/p/you-should-b…
English

@StealthMedical1 Maybe it was just me but I heard "neck joke" and not "anecdote". Thanks for the clarification. 🤣
English









