M_G

[dax @thdxr]

we got hit with a crazy scam attempt

someone signed up for our inference and did a video call with our sales person confirming intent to spend $400,000 over the next year and asked for increased rate limits

our sales person felt like something was off so he looked up the company - found a bunch of videos of the CEO and it looked and sounded like the same person he talked to

so he figured it was real but we started looking deeper

the email they had been talking to us from was a lookalike domain that was registered 4 days ago. all the traffic they were sending looked bizarre and came from foreign IPs

emailed them for more info to see what they'd say. of course they hit us with the "i'm about to get on a plane, can't do anything right now, please move forward"

messaged the real CEO on instagram and yeah he had no idea what we were talking about, the scammer was deepfaking him

be careful out there, things are getting crazy

[Who Is Kenbruz @whoiskenbruz]

Matthew 7:24–25 says:
“Anyone who listens to my teaching and follows it is wise, like a person who builds a house on solid rock.”
“Though the rain comes in torrents and the floodwaters rise and the winds beat against that house, it won’t collapse because it is built on bedrock.”

Another visual footage from Nepal

[Matteo Collina @matteocollina]

.@nodejs has always been about I/O. Streams, buffers, sockets, files. But there's a gap that has bugged me for years: you can't virtualize the filesystem.

You can't import a module that only exists in memory. You can't bundle assets into a Single Executable without patching half the standard library.

That changes now 👇

[M_G @manishgowardipe]

Using redis mcp server as a tool for agent in Agent Camp #Feb26MTP #AiAgent

[M_G @manishgowardipe]

@SumitM_X Great timing. Thanks for sharing this list.
I am preparing for DSA.
I have build visualisation for each problem to understand them better. Ex: Rain water trapping is not so easy to understand just by looking at the code.
Link : https://t.co/W4AV2lDw9O

[Josh @joshmanders]

Open source isn't dying because of AI.

It's dying because we all fucking suck.

Users. Maintainers. The whole ecosystem. All of us.

We fucking suck as users.

We use OSS to do our jobs. To build products. To make money. Our employers depend on it. Our startups run on it.

But the second a maintainer mentions compensation? We lose our fucking minds. "It should be free." "That's not the open source way."

Meanwhile we're extracting value from someone's unpaid labor every single day.

We file issues like we paid for a support contract. We demand timelines. We get snippy when our bug isn't the priority.

We're not customers. We're guests. Start acting like it.

We fucking suck as maintainers.

We wanted the GitHub stars. The conference talks. The Twitter followers. We wanted to be the person who "owns" that thing everyone depends on.

But now people actually depend on it and we're annoyed.

"Talk is cheap, show me the code."

So someone does. They spend hours on a PR. We ignore it for months. Close it with no explanation. Or we screenshot their issue and mock them publicly for not reading our minds about what we actually wanted.

We invited contributions then punished people for contributing.

We don't want to maintain projects. We want to be admired for maintaining them. Not the same thing.

We suck at this together.

Both sides want the benefits without the responsibilities.

As users we want free, maintained, high quality software but won't contribute a damn thing. Not money. Not code. Not even basic respect.

As maintainers we want the status of running critical infrastructure but won't communicate, won't collaborate, won't treat people like humans.

We all know this shit doesn't work. And yet here we are.

Okay Josh, what do you suggest then?

If we use OSS and profit from it, we contribute something. Anything. Money, docs, triage, kindness. We stop expecting infinite free labor.

If we maintain OSS and we're burnt out, we say so. Archive it. Hand it off. Ghosting is worse than walking away.

And if we can't treat each other with basic respect? We don't get to participate. Full stop.

Open source runs on people. On us.

None of us owe each other a god damn thing. But we could choose to stop being assholes and do better anyway.

[daz @MetamateDaz]

HOT TAKE: IF BUSINESSES ONLY HAVE TO PAY TAXES ON PROFIT, NOT REVENUE, THEN I SHOULD ONLY HAVE TO PAY TAXES AFTER I'VE PAID ALL MY BILLS AND RENT.

[Wonder of Science @wonderofscience]

A notebook that connects to your phone via bluetooth.

[Malte Ubl @cramforce]

12 minutes from shitpost to completed project https://t.co/CnLMuOYPRi

[Peter Girnus 🦅 @gothburz]

The company hired me to lead their "Agile Transformation."
I don't know what Agile means.
Nobody does.
That's why it works.

I make $425,000 a year.
To move sticky notes.
From left to right.
On a board.
The board is digital now.
The sticky notes cost $80,000 in Jira licenses.
Progress.

Day one, I said "we need to break down silos."
Everyone nodded.
Silos are bad.
I don't know why.
But destroying them is a career.
My career.

I introduced "squads."
Squads are teams.
But disrupted.
We disrupted the teams into teams.
Different names.
Same people.
Same problems.
But Agile problems now.
Agile problems are strategic.

A senior engineer asked what we're actually changing.
I said, "The mindset."
He asked what that means.
I said, "It's a journey."
He asked where we're going.
I said, "Toward agility."
He asked what agility means.
I pointed at the sticky notes.
They were moving left to right.
That's velocity.
We have velocity now.

The VP of Engineering said two-week sprints don't fit their work.
I said, "That's waterfall thinking."
Waterfall is bad.
Like silos.
I don't know what waterfall is.
But I know it's bad.
She stopped talking.
Waterfall accusations end conversations.

We had a retrospective.
In the retro, we discussed what went wrong.
Everything went wrong.
We put it on sticky notes.
Then we moved the sticky notes.
Into a column called "Parking Lot."
The Parking Lot is where problems go to die.
It's full.
We don't look at it.
That's agile.

Velocity is up 40%.
I defined velocity.
I also defined the points.
I also defined the stories.
We're crushing it.
At the things I made up.
To measure.
Ourselves.

The CEO asked for ROI.
I showed a chart.
The chart went up.
Charts should go up.
This one did.
I didn't label the Y-axis.
Nobody asked.
Leadership is confidence.

We do standups now.
Every day.
We stand.
For 45 minutes.
Standing is agile.
Sitting is waterfall.
My legs hurt.
But we're transforming.

The transformation is now "Phase 3."
Phase 1 was assessment.
Phase 2 was implementation.
Phase 3 is "continuous improvement."
Continuous means forever.
Forever means job security.
I'm very secure.

My contract was extended.
Three more years.
For "cultural impact."
The culture is confused.
But impacted.

Agile transformation isn't about being agile.
It's about transforming.
Continuously.
Toward more transformation.
The destination is the journey.
The journey is billable.

[M_G @manishgowardipe]

We don’t just help you reach users — we help you build the systems behind the growth.
Targeted outreach + custom software for product based companies.

[M_G @manishgowardipe]

Stop marketing to “everyone”.
We help products reach exactly who they want — by geography, job role, seniority & company revenue.
Precision > volume.

DM's open / reply reach

[M_G @manishgowardipe]

@ScholarshipfPhd Hi

[M_G @manishgowardipe]

@levelsio I like mine.

[NO CONTEXT HUMANS @HumansNoContext]

Task failed successfully

[Tanner Linsley @tannerlinsley]

Something that's been on my mind for the last few days:

Proactive marketing/sales for devtools (especially free and open source ones) is hard, and way more important than people think. I often call it sales/marketing, but really, it's education/connection at heart. It's easy to forget that you can't just build something new and expect people to "get it" and want it. You have to meet them where they stand, build bridges of understanding, kindness, open discourse... especially when those individuals are coming from a place you fundamentally disagree with or think is "wrong", which is often the cas. You have to teach by example, convince with care, show how it works/doesn't work, where it's good and where it's not.

I'd tried to quickly list out the things I have been trying to help me build bridges with devs over the years:

- Be kind
- Seek to understand your audience by living in their shoes frequently
- Be practical/realistic
- Show and tell as early as possible
- Iterate on feedback quickly
- Every complaint is valid, even if the proposed solution isn't
- Admit/embrace imperfection with humility
- Generally avoid sarcasm and tongue-in-cheek humor
- White-glove onboard every single new user as if they're your highest paying customer

I believe that if anyone does this consistently their efforts will eventually flywheel beyond organic reach.

[Ville Saukkonen @SaukkonenVille]

I haven't even migrated to @tan_stack start yet and I should already be migrating to @remix_run 3?

[Bemba Nation @BembaNation]

ODI world cup 2027 playing XI 😭🫠😂

1. Shubman Gill (c)
2.
3.
4.
5.
6.
7.
8.
9.
10.
11. Harshit Rana

[ア @yuruyurau]

a=(x,y,o=mag(k=x/4-12.5,e=y/9+9)/9)=>point((q=x+39+y+1/k+o*k*(cos(y)/4+cos(e))*sin(o*4-t))*.7*sin(c=o+e/99-t/8+i%2*3)+200,200+y/2*cos(c*4-o)-q/2*cos(c))
t=0,draw=$=>{t||createCanvas(w=400,w);background(6).stroke(w,46);for(t+=PI/60,i=4e4;i--;)a(i/2%100,i/350)}//#つぶやきProcessing

[Paul Copplestone - e/postgres @kiwicopple]

congrats to the @PostgreSQL contributors 🐘

◆ asynchronous I/O
◆ UUIDv7
◆ virtual generated columns
◆ temporal constraints
◆ oauth authentication
◆ improved text search
◆ parallel streaming in replication
◆ new wire protocol (first new protocol version since 2003)