Naga Satya Geeth

CEO of @htmx_org

[Naga Satya Geeth @nagsgeeth1]

@rapidobikeapp please centre the share icon. Also please remove the “Rapido “ sound every time the captain reaches the location and at the drop off. It sounds annoying and crass.

[Sunny R Gupta 🐰 @sunnykgupta]

If you’re making a side project, however tiny, use my account as a booster.

Post a snapshot of your project, heck, it could be a screen-grab of your code editor.

Sample tweet you can post:
———————————

I am working on a project that will enable Metro users in major cities to congregate and have a peer network to learn during those usually boring commutes.
<attach a screenshot of anything relevant, tag @sunnykgupta and @teamshiksha>

I’m looking for a frontend/backend/db/generic buddy to code this alongside with.

———————————

Quote this tweet with your best projects, be discovered, meet hack-buddies!!
I will retweet all quotes. All the best 🤞

(Also, if you’re in Bengaluru, do join the BLR Impromptu Meet-ups group to meet other high-energy individuals from various walks of life, link pinned to my profile.)

[Naga Satya Geeth @nagsgeeth1]

@Helldivers_NOW Only wallbouncing got that schmovement

[Cheng Lou @_chenglou]

My dear front-end developers (and anyone who’s interested in the future of interfaces):

I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept):
Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow

[Truth Enforcer Silly Goober @Truth_Officer]

Legit this is peak. Go check out the full video by them it's over 9 minutes

[KINGDOM LABORATORIES¹ | LORE | GAMES | SERVIDORES @KLaboratories]

CUTE!🤏

https://t.co/RYNMcD6XuB

[Praise @tufpraise]

oh to be a duck gliding through cherry blossom water and not having a care in the world.

[IronS1ghts @Iron_S1ghts]

Basic Helldivers 2 Private Server with Pandora's Auto-Responder ✨
@0xPandoraProxy

[Ankush Dharkar wants you on tier3.college @ankushdharkar]

@VazeKshitij Don't lose your spark. The world will try very hard to make you conform to the way of the average. Don't align towards it. Walk far away from it, walk fast. Keep your spark alive.

[Dr. Dominic Ng @DrDominicNg]

i regret to inform you that personal growth rarely comes from acquiring new knowledge and almost always from:
- getting humiliated
- showing up terrified and doing it anyway
- admitting you might be the problem

[NO CONTEXT HUMANS @HumansNoContext]

The funniest thing I've seen in a while 😂

[Naga Satya Geeth @nagsgeeth1]

@Bhavani_00007 https://t.co/K9xm6C9TLl

[Matthew Prince 🌥 @eastdakota]

Yesterday a quasi-judicial body in Italy fined @Cloudflare $17 million for failing to go along with their scheme to censor the Internet. The scheme, which even the EU has called concerning, required us within a mere 30 minutes of notification to fully censor from the Internet any sites a shadowy cabal of European media elites deemed against their interests. No judicial oversight. No due process. No appeal. No transparency. It required us to not just remove customers, but also censor our 1.1.1.1 DNS resolver meaning it risked blacking out any site on the Internet. And it required us not just to censor the content in Italy but globally. In other words, Italy insists a shadowy, European media cabal should be able to dictate what is and is not allowed online.

That, of course, is DISGUSTING and even before yesterday’s fine we had multiple legal challenges pending against the underlying scheme. We, of course, will now fight the unjust fine. Not just because it’s wrong for us but because it is wrong for democratic values.

In addition, we are considering the following actions: 1) discontinuing the millions of dollars in pro bono cyber security services we are providing the upcoming Milano-Cortina Olympics; 2) discontinuing Cloudflare’s Free cyber security services for any Italy-based users; 3) removing all servers from Italian cities; and 4) terminating all plans to build an Italian Cloudflare office or make any investments in the country.

Play stupid games, win stupid prizes. While there are things I would handle differently than the current U.S. administration, I appreciate @JDVance taking a leadership role in recognizing this type of regulation is a fundamental unfair trade issue that also threatens democratic values. And in this case @ElonMusk is right: #FreeSpeech is critical and under attack from an out-of-touch cabal of very disturbed European policy makers.

I will be in DC first thing next week to discuss this with U.S. administration officials and I’ll be meeting with the IOC in Lausanne shortly after to outline the risk to the Olympic Games if @Cloudflare withdraws our cyber security protection.

In the meantime, we remain happy to discuss this with Italian government officials who, so far, have been unwilling to engage beyond issuing fines. We believe Italy, like all countries, has a right to regulate the content on networks inside its borders. But they must do so following the Rule of Law and principles of Due Process. And Italy certainly has no right to regulate what is and is not allowed on the Internet in the United States, the United Kingdom, Canada, China, Brazil, India or anywhere outside its borders.

THIS IS AN IMPORTANT FIGHT AND WE WILL WIN!!!

[BONESAW 🕊️ @BonesawMD]

Frugality is a disease.

How much money a person has is largely irrelevant.

What's vital is that you avoid spending time with the stingy.

The scarcity mindset they have with money is the material manifestation of their intrinsic state. They block the healthy flow of energy, they hoard and hold on to expired states that should be discarded.

And so they are slowest to evolve and adapt.

They can rarely grasp new opportunities because their hands are always full.

Notice how the frugal are never lucky. They struggle and toil through all of their days. Everything is difficult. Entire lives are impacted.

You can always make more money. But I've seldom seen someone recover from spiritual poverty: stinginess.

The more you give to life the more you get from life.

Inviolable law.

[ahmadaccino @ahmadaccino]

@prasenx dont listen to the people talking about amplitude. the actual answer is they create sound waves that break the space time continuum and shoot it out of your speakers

[NeetCode @neetcode1]

This is a blunt, but very true take.

I think most (but not all) people trying to get an entry-level role have a lot of misconceptions of what they're trying to accomplish.

Most really don't want to take the initiative. They might not like coding, or even hate it.

They just learn how to do random YT tutorial apps and try to check as many boxes on their resume.

They want someone else to tell them exactly what to do, exactly what to build

They assume that's what being a developer is. They just need to be "trained", or go through the perfect "training", (i.e. university, certification, DSA sheets), and then everything will take care of itself.

Learning things yourself, is less about the things that you learn, but more about the person you become.

You want to be the person who can answer your own questions, and even have opinions of your own about which direction a product should take, or which tools would be best for a project.

[BONESAW 🕊️ @BonesawMD]

When you finally reclaim your health after years of chronic stress you can feel the calm radiance that warms your pores

Unmistakable.

physically, you're buoyant, bountiful, flourishingly light.

your aura is so dense because it carries the weight of your previous burdens

[Arpit Bhayani @arpit_bhayani]

you don't need to watch my videos to become a better engineer. to be honest, it has never been easier to become better. here's what you should do

1. pick an engineering blog
2. download it into text or pdf
3. upload it to your favorite LLM tool
4. keep asking questions until you think you have fully understood it.

please do not ask it to summarize. that's naive and bs. use LLMs to dig deeper into practicalities, implementation details, and challenges that you might run into when you hit production. go into absurd extremes and see what it spits out.

If you were curious, LLMs just gave you a high bias for action.

[Ashutosh Maheshwari @asmah2107]

I love asking how to handle two users trying to edit the same data at the same time.

The first answer is almost always "I'd lock the record in the database."

This is where the real discussion begins. It’s not about stopping a conflict.

It's about the price you're willing to pay for consistency.

The magic keyword is Concurrency Control.

Most engineers think their job is to prevent conflicts. It's not.

Your job is to choose a strategy that matches the reality of your application's workload and user experience.

A classic example:
Two support agents, Alice and Bob, are editing the same customer ticket.

Alice opens the ticket and starts writing a detailed response.

A minute later, Bob opens the same ticket, quickly fixes a typo in the title, and hits "Save."

A minute after that, Alice finishes her long response and hits "Save."

Alice's save just overwrote Bob's typo fix without her even knowing.

The system is now in an inconsistent state.

Pessimistic Locking ?

When Alice opens the ticket, the system places a lock on that database row.

When Bob tries to open it, he either gets an error ("This ticket is currently being edited by Alice") or is forced into a read-only mode.

The bug is gone, but the user experience is terrible. You've created a bottleneck and assumed conflicts are common.

Fix ? Optimistic Locking.

>Add a version column to the tickets table.
>When Alice loads the ticket, it's at version: 1.
>When Bob loads the ticket, it's also at version: 1.
>Bob saves his typo fix.

The UPDATE query specifically says:

WHERE ticket_id = 123 AND version = 1.

The update succeeds, and it increments the version to 2.

Alice finishes her long response and tries to save.

Her UPDATE query also says:
WHERE ticket_id = 123 AND version = 1.

The database runs the query.
How many rows match? Zero.

The update fails.
The application code catches this failure and tells Alice: "This ticket was modified while you were editing. Please review the changes and submit again."

The conflict is detected, not prevented.

So, the real design question isn't: "How do I prevent conflicts?"

It's: "What is the actual business cost of a conflict, and is it cheaper to prevent them or just detect them?"

When designing an update operation, if conflicts are rare, don't punish every user with a lock.

Let them work freely and handle the 1% case where a conflict occurs.

That's thinking in trade-offs.

[Nithin Kamath @Nithin0dha]

More here: https://t.co/ZmaQdQilHA

And btw