Ruberto Paulo

Code Warlock l Manager & Student of Humans | Husband to Perfection | Father of sons | Maker of brûlée | Planeswalker | Protagonist by day, Antagonist at night.

[Ruberto Paulo @legend_rob]

@CityofCT It’s great that you have done so much to the water delivery network.

However without building new large dams and water catchment areas our water inventory is fixed to service a certain number of people, with so many coming to the cape we will surpass thresholds

[Ruberto Paulo @legend_rob]

@landbourainier Any fundraising for the kid to never need to worry about another pie again. I’d give

[Ruberto Paulo @legend_rob]

@TechLeadershipX is coming to my old stomping grounds - JHB get ready for a great evening, you'll get to rub shoulders with some really cool people and come away with something worth thinking about.

If you can you should free up the evening and attend - it'll be worth it.

[Ruberto Paulo @legend_rob]

@elonmusk The biggest difficulty here in South Africa is that they are not available 😅

[Martin Tobias (Pre-Seed VC) @MartinGTobias]

🚀 Just invested in TurnStay! This African fintech is slashing travel payment costs by up to 70% & boosting conversions 25-50%. Here’s why I’m betting big on them: 🧵 #Fintech #TravelTech #Africa

[Ruberto Paulo @legend_rob]

@RhysSullivan Vibe coders are software developers. We need to create the distinction between those who can produce software and those who can write, read, debug, design software systems(engineers)

Cause when the 💩 hits the 🪭. “Who you gonna call?” Probably not vibe coders

[Ruberto Paulo @legend_rob]

@allenholub You clearly haven’t seen my git log 🤣

Every new feature has at least a half dozen fixes folllowing it 😂

[Ruberto Paulo @legend_rob]

@chantastic Totally agree, repairability is critical. But also: our systems must reflect our evolving understanding. Gaps between models and reality, if left unaddressed, cripple systems. Extensibility and loose coupling matter just as much for long-term resilience.

[Ruberto Paulo @legend_rob]

Verifying myself: I am legendary_rob on https://t.co/yReczal368. rwkHB3_U1Be32f26uQ5k-XNKjBiZMc2yOBQX / https://t.co/kVt3phUwjb

[Ruberto Paulo @legend_rob]

#ThinkBigger @PeachPayments - this event has been so good so far - so many merchants coming to see all the cool stuff we are building for them. 🧡

[Rubyfuza & Friends🤞 @rubyfuza]

Dear Rubyfuza Friends, As you may know, Rubyfuza has been a cherished event within our community. However, due to a lack of sponsorships, we are currently facing the risk of not having Rubyfuza 2024 😔

[Elon Musk @elonmusk]

Precisely

[Ruberto Paulo @legend_rob]

@nicolaballotta How about managers are there to help the team unblock themselves? If the team become dependent on a manager to resolve technical issues, communicate, guide on growth, manage workloads and report issues then what you’ll end up with a whole lot of risk. Teams should be autonomous

[Raul Junco @RaulJuncoV]

I learned a new acronym: JED!

It feels so tired of these extreme viewpoints about Monolithic Vs. Microservices.

On one side, "Microservices is the solution to your bad architecture."

Saying that microservices are always the solution to lousy architecture oversimplifies the matter.

Microservices can offer many benefits but also introduce complexity.

On the other side, "I'm back to Monoliticts; Microservices is overhead."

Claiming that monolithic architecture is the only way could also be an oversimplification.

In reality, the best architectural choice depends on:
- The specific context
- Performance Requirements
- Constraints of each project
- Team Expertise
- Cost Constraints
- Reliability and Fault Tolerance
- Time to Market

Why can't the industry meet in the middle and accept there is no silver bullet when building software?

The best approach for me is a middle-ground approach.

Starting with a monolithic and breaking down specific functionalities into microservices is fine.

That's why I loved the term JED: Just Enough Distribution.

[Ruberto Paulo @legend_rob]

@yet_anotherDev Thanks for putting some time into writing and sharing this 🙇🏼‍♂️

[Ruberto Paulo @legend_rob]

@nickfloats First thing I’ll teach it is to get threw those “I’m not a bot tests”

[fks @FredKSchott]

passing core web vitals is about to get a lot harder, especially in the JS ecosystem. (see thread for details)

[Ruberto Paulo @legend_rob]

@allenholub We theme the sprints after different things. One year was super hero’s, we have also done different Greek and Roman gods.

Why? Why name months? time is a construct just to know a chunk of time has passed

[Ruberto Paulo @legend_rob]

@SynStalker

[Jason Fried @jasonfried]

I've consulted. I've advised. I've served on boards. I've done client work. I've written books. I've spoken on the circuit. I've blogged for years.

I have to say, I've found no greater professional joy than working with a tight group of people to ship and support our own products. And for those products to find people willing to trade their own hard earned treasure for a little bit of ours.

Betting on an idea — and seeing it through — is enormously fulfilling. The creative and intellectual stimulation is beyond compare. Especially when you're the first customer for anything you make.

When I was a consultant doing work for hire I thought it was the peak. I got to bounce from client to client, sign big contracts, do a lot of work, cash large checks, etc. But then you realize most of what you do is never implemented. Yes, you got paid for it, but it was just advice, recommendations, and suggestions. Words on pages that were received, but not really read. Designs in files that were delivered, but never really deployed. There was nothing there in the end. You didn't get to make any bets, you just played with someone else's chips.

You thought you were changing things. Changing them. But it wasn't change, it was an exchange. You handed it over, they handed you something in return, and that was that.

I'm glad I went through it, otherwise I wouldn't have known it.

Been giving other people advice for years? Give yourself the advice and see if it's any good. Meet the market.

Go make something. Join a team that's making something. Put your fingerprint on something that won't just sit on the shelf somewhere.