Dave Rob

[Dave Rob @stigmaDave]

@jamalthetenth Fucking morons, why don't just approach when they see their baggage? , I hate them

[Dave Rob @stigmaDave]

Un meme de hace 9 años

[Dave Rob @stigmaDave]

@rochamoya_ "Este ataque no es únicamente a mi persona; sino al movimiento de la Cuarta Transformación, a sus emblemáticos liderazgos"
traducción: todos en el movimiento estamos embarrados, y más, sus emblemáticos líderes

[Daniel Berk @danielcberk]

Spotify needs to release a “kids” setting so I can play all the songs my kids listen to without it affecting my own Discovery algorithm.

Insane that I can’t do this already.

My Discover Weekly is just nursery songs and Moana.

@Spotify please fix this.

[Interesting AF @interesting_aIl]

Programmers were asked to create the worst user experience poossible:

[Dave Rob @stigmaDave]

@astrojoc En México sería hablar como chavoruco:
No macayú
Inguesu
Ya ni la muelan
Ya estuvo suave
No la chifles
Etcétera

[Work Chronicles @_workchronicles]

(comic) The Work-Life Balance Connection

[Dave Rob @stigmaDave]

@acdc @ChristieGoodwin 😎🤘

[Javarevisited @javarevisited]

Manager: We lost our best engineer today.

CEO: The one leading payments?

Manager: Yes.

CEO: Did another company offer more money?

Manager: No.

CEO: Then why leave?

Manager: He said he was tired of fixing the same production issues every week.

CEO: That’s part of the job.

Manager: He didn’t mind fixing issues. He minded that nobody wanted to fix the root cause.

CEO: We prioritized speed.

Manager: He wanted quality.

CEO: So he left over that?

Manager: He left because he felt like a firefighter, not an engineer.

Good engineers don’t just want to solve problems.
They want to eliminate them.

[Katyayani Shukla @aibytekat]

During a job interview, if they ask: "How do you handle it when everything is a priority?"

USE THE GOLDEN RESPONSE:

[Simons @Simon_Ingari]

Corporate Rules for Happy Life

1. Trust nobody.

2. What happens in office, remain in office. Never take office gossips to home and vice versa.

3. Enter office on time, leave on time. Your desktop is not helping improvement in your health.

4. Never make GF/BF and/or brother/sister in office. It will always backfire.

5. Expect nothing. If somebody helps, feel thankful. If not, you will learn to know things on your own.

6. Never rush for position. If you get promoted, congrats. If not, it doesn't matter. You will always be remembered for your knowledge and politeness, not for your designation.

7. Never run behind office stuff. You have better things to do in life.

8. Avoid taking everything on your ego. Your salary matters. You are being paid. Use your assets to get happiness.

9. It doesn't matter how people treat you. Be humble. You are not everyone's cup of tea.

10. In the end nothing matters except family, friends, home, and Inner peace

[Visual Studio @VisualStudio]

🎉 Visual Studio turns 29 today!

From VB in ’97 to AI‑powered coding in 2026, it’s been nearly three decades of shipping apps, debugging at 2 AM, and discovering one more extension that changes everything.

Here’s to 29 years of:
• IntelliSense magic
• Build‑break heartbreak
• Refactors that save the day
• Extensions we can’t live without
• An IDE that keeps evolving with us

Happy birthday, Visual Studio — still the place where great code begins. 💜

[Stefan Đokić | .NET @TheCodeMan__]

If your frontend keeps asking the server every few seconds, you might be solving the wrong problem.

A lot of “real-time” features on the web are implemented like this:

Client → Request → Server → Response
(wait a few seconds)
Client → Request → Server → Response
(wait again)
Client → Request → Server → Response

This is called polling.
The client repeatedly asks:
“Do you have new data?”

And most of the time, the server responds with…
Nothing new.

Which means:
• unnecessary requests
• wasted server resources
• extra latency for users

Now imagine a different model.

Instead of constantly asking the server for updates…

The client opens one connection and waits.

Client → Open connection
Server → pushes events when data changes
Event → Event → Event

That’s exactly how Server-Sent Events (SSE) work.
The browser opens a connection using:

Content-Type: text/event-stream

And the server can stream updates continuously through that same connection.

No repeated requests.
No polling loops.

Just a single open connection where the server pushes updates when something actually happens.

This makes SSE a great fit for things like:
• live notifications
• dashboards
• progress updates
• activity feeds
• monitoring systems

And here’s the interesting part.

When developers think about real-time features, they often jump straight to WebSockets.

But many times, you don’t need the complexity of full duplex communication.

A simple server → client stream is enough.

That’s exactly what SSE provides.
Polling asks the server for updates.

Server-Sent Events stream them when they happen.

I just uploaded a video on how to implement it: https://t.co/CdEIcRXAxX

#Dotnet

[mitsuri @0xmitsurii]

Lucy Liu: Why i wanted to make "f*ck you" money.

[cinesthetic. @TheCinesthetic]

Official trailer for ‘MALCOLM IN THE MIDDLE: LIFE’S STILL UNFAIR��

[El Programador Senior @5eniorDeveloper]

Yo estaría dispuesto a pagar por una herramienta que revise mis PRs y que los comentarios sean como los que hace Linus

[Liberty Pill Memes @LibertyPillMeme]

Dad jokes with Hugh Jackman and Kate Hudson

[Dave Rob @stigmaDave]

@um_gerardo Las ironías de la vida, al repartidor le terminaron repartiendo

[Dave Rob @stigmaDave]

@AdrianaDavilaF Es que solo les dijeron que llevaba acento, no en dónde

[Programmer Humor @PR0GRAMMERHUM0R]

weWillBeLaunchingSoon https://t.co/Xl71yj94YI