Reddy G

Engineering and much more.

[Reddy G @guvvala39]

That’s it…

[Reddy G @guvvala39]

@YouTube is this a bug?
Toyota channel showing @TheStudio profile image? @MKBHD

[Reddy G @guvvala39]

Works for me

[GitHub @github]

👀 Most devs use Copilot like autocomplete. But senior devs use it like a delegated engineer. Here’s your 1-week workflow to stress test Copilot where it actually matters ⬇️

[Nithya Shri @Nithya_Shrii]

RESIST the urge to teach anything to anyone unless you’re asked.

[Reddy G @guvvala39]

https://t.co/cwj0w1ywdx

[Reddy G @guvvala39]

Reasoning is unmatched with any other models https://t.co/n35uSFe3rU

[Reddy G @guvvala39]

Every word here 💯 correct. My team is in exact same situation. Coding 40% synchronizing and maintaining a barrage of pipelines 60%.

[DHH @dhh]

Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table.

Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication.

Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.”

Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it.

The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks.

Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.

[Reddy G @guvvala39]

@grok https://t.co/JJhPWVjIzJ

[Reddy G @guvvala39]

This is a response from grok which says it has its own pi cluster. I am curious

[Reddy G @guvvala39]

@grok seems to be more assertive in its responses. Still I see it as a 🦜 doesn’t know anything, answers anything

[Reddy G @guvvala39]

This is a response from grok which says it has its own pi cluster. I am curious

[Reddy G @guvvala39]

CRA agents have no idea what they are speaking.

I tried setting up a pre-auth debit to pay taxes for my business. It failed giving an error code back.

Cuz i am over due I want to pay it asap. So I turned to my bank provided option to pay taxes.

While the money is debited and inflight i get an email in my account saying pre-auth scheduled.

Obviously I don’t have enough funds to cover to pay my taxes twice I called upon CRA to cancel scheduled payment that was never successfully setup.

Agent said its the technology. And she can’t cancel it. On top she said i will get a charge back for insufficient funds which I have to pay to cra.

I asked will it be refunded cuz its their technology caused this mess. She said no.

Just to make sense I asked again “For a technology error by CRA i have to pay a charge back on top of my taxes?” She very confidently said yes.

I can’t believe this is happening.

[Reddy G @guvvala39]

@Sammy_canada2 😆

[Reddy G @guvvala39]

🥲

[None @newbie_567]

😭😭😭😭😭😭😭

[Reddy G @guvvala39]

💯

[Ethan Evans @EthanEvansVP]

Negative behaviors in your career are like chili peppers in food: Used carefully, they can spice your career and advance it. To maximize success, you need to learn to be difficult and disagreeable in specific ways.

[Reddy G @guvvala39]

#fujifilmxm5

[Reddy G @guvvala39]

Can say been there.. done that

[Harveen Singh Chadha @HarveenChadha]

last night was unable to solve a bug. tried claude, gemini, deepseek all failed. slept thinking will debug tomorrow.

had a weird dream. In my dream, was debugging the code and finally was able to find the bug, it was just a one line fix.

Finally woke up tired thinking did I really solve the bug or not. opened my codebase, changed that very line and the code worked.

how is this possible? what do I call this type of coding? dream-fix coding?

[Reddy G @guvvala39]

MUST WATCH
How One Company Secretly Poisoned The Planet https://t.co/Sl4SQrxONL via @YouTube