Ruberto Paulo

@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

Cape Town's dam levels have dropped to 50.4% due to high water usage and the heatwave. Remember, water is essential only for necessary purposes. Let's work together to save water and delay restrictions. Every drop counts!

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

🚨Shock at Western Cape School Over "Pie Day" Incident ‼️ A Grade 1 teacher at Thembalethu Primary School in George has been temporarily suspended following a viral video that appeared to show her mocking or publicly highlighting a learner who could not afford to contribute R40 for a school fundraising "pie day" activity. The footage, which circulated widely on social media, depicted classmates eating pies and drinking juice while the young boy, who lives with his grandmother and comes from a disadvantaged background, sat without food, reportedly covering his face in distress. Parents and residents protesting outside the school, emphasizing that no child should be shamed or excluded due to poverty. Parents and community members have called for greater sensitivity in school fundraising activities to avoid disadvantaging vulnerable children. The incident has reignited broader discussions about poverty, inclusion and dignity in South African schools ‼️

@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.

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

Please reply to this post with any difficulties you may have had in trying to buy a Tesla. Our goal is for the purchase and delivery experience to be fast and simple, with accurate answers to your questions. The key test is that you would recommend it to a friend.

🚀 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

@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

VIBE CODERS ARE SOFTWARE ENGINEERS VIBE CODERS ARE SOFTWARE ENGINEERS VIBE CODERS ARE SOFTWARE ENGINEERS VIBE CODERS ARE SOFTWARE ENGINEERS VIBE CODERS ARE SOFTWARE ENGINEERS VIBE CODERS ARE SOFTWARE ENGINEERS VIBE CODERS ARE SOFTWARE ENGINEERS VIBE CODERS ARE SOFTWARE ENGINEERS

@allenholub You clearly haven’t seen my git log 🤣 Every new feature has at least a half dozen fixes folllowing it 😂

I just saw a Wirecutter article waxing poetic about the joys of erasable pens, which got me wondering why anybody would think that an erasable pen is a good thing when compared to the time-honored method of just crossing stuff out. Seems to me that erasability is a way to present ourselves as infallible. We appear to always get it right the first time. We appear to never make mistakes. Crossing things out is an admission of our fallibility, out there in plain sight for anybody to see. That need to appear infallible when applied to software development is a disaster. It forces us into a "get it right the first time" mentality and discourages us from releasing in-progress software into a few customers' hands for feedback and improvement. It also leads to waterfall big-up-front-plan thinking where people imagine that the more detailed the plan, the fewer things need to be crossed out. All that leads to failed products because we never get it right the first time, no matter how hard we try. Best to work in a way that takes that as a given rather than pretending the problem doesn't exist. Any writer will tell you that no matter how much up-front planning you do, the first draft is always cr*p. It's a start, but you arrive at good through editing—incremental improvement. Same for software. Fred Brooks once said, "Build one to throw away." I wouldn't do that on a massive scale, but I do it all the time in very small increments. So, let's go back to crossing things out.

@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.

upgrade-ability isn’t real platforms are generational repair-ability is the only long-term value in modularity

Verifying myself: I am legendary_rob on Keybase.io. rwkHB3_U1Be32f26uQ5k-XNKjBiZMc2yOBQX / keybase.io/legendary_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. 🧡

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 😔

Precisely

@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

As an Engineering Manager, you have one primary responsibility towards your team. 🚧 Removing blockers. Career growth, mentoring, 1:1s, and other duties are crucial for an Engineering Manager, but the first and most important thing your team needs is to be empowered to do their job. Removing any blockers that could arise in their daily job is the best thing you can do to empower them. What does it mean in practice? 🔧 Identifying and helping resolve technical issues that could affect projects. 🤝 Facilitating clear and open communication by resolving any conflicts that could arise among team members. 📚 Providing resources and opportunities for professional development to help team members expand their skills and knowledge to solve blockers. ⚖️ Balancing project efforts with team capacity, ensuring workloads are manageable, and expectations are realistic. 🔄 Using tools and ways of working that make things go smoother and quicker. 🛡️ Creating an environment where everyone feels comfortable raising their hands to report any blockers at any time. What are other ways to remove blockers that I might have missed?

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.

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

Hello Rubyists, After the good holidays, here is a new article for those interested in Webhooks and how it works under the hood. With an implementation in Rails :p dev.to/yet_anotherdev…

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

This is actually insane A new type of device, a pocket companion. They’re not trying to replace your phone It’s AI enabled hardware that understands interfaces & can complete tasks for you You can even teach it through screenshare & it’s only $199 🥵

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

@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

I hear a lot of discussion about how to name Sprints, but my question is: _why_ would you name a Sprint? The practice has always baffled me. What exactly do you do with that name?

What meme made you laugh today? I've run out

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.