Ben Meneses-Sosa

1.2K posts

Ben Meneses-Sosa banner
Ben Meneses-Sosa

Ben Meneses-Sosa

@benhas

People developer for love and profit | VP of Engineering at @lendiau | @MCCAustralia co-organiser | Coach @Folklorevc | Former software artisan | he/him

Sydney, New South Wales Se unió Temmuz 2009
1.4K Siguiendo294 Seguidores
Tweet fijado
Ben Meneses-Sosa
Ben Meneses-Sosa@benhas·
Thanks @SydTechLeaders for the opportunity to present. It was a great privilege sharing the mic with @sugendran and Liza Z. Until the next one 👋
Sydney, New South Wales 🇦🇺 English
1
2
5
0
Ben Meneses-Sosa retuiteado
Adam Grant
Adam Grant@AdamMGrant·
Humility isn't a sign of low self-esteem. It's a mark of high self-awareness. The goal isn't to deny your strengths. It's to see your strengths & shortcomings accurately. The first rule of improvement: recognize room for improvement. Narcissism feeds ego. Humility fuels growth.
English
74
1.2K
4.6K
451.3K
Ben Meneses-Sosa retuiteado
George Monbiot
George Monbiot@GeorgeMonbiot·
Horrific crimes against civilians are not redeemed by horrific crimes against civilians.
English
157
1.8K
10.1K
587.5K
Ben Meneses-Sosa retuiteado
Naomi Klein
Naomi Klein@NaomiAKlein·
Since 2.6 million followers isn't nothing, a quick note on the sheer dishonesty at work here: 1. Since v. early days, we were warned that one of the possible short term side-effects of the Covid vaccines (along with soreness, fatigue and flu-like symptoms) could be irregular menstrual bleeding. Many papers have been published on this. Never denied, never hidden. 2. That is NOT the claim that for which Wolf needs vindication. She repeatedly amplified claims that simply being *near* vaccinated ppl (or being in rooms where they had been) caused bleeding and cramping. Lots of people believed her. It's still wrong.
Dr. Drew@drdrew

It's getting harder for them to say @NaomiRWolf is wrong when the science keeps saying she's right. A bombshell study now confirms mRNA shots can cause "unexpected vaginal bleeding" in women. Naomi joins @DrKellyVictory & @joshg99 at 1:30 PT on @AskDrDrew drdrew.com/2023/bombshell…

English
197
550
3.7K
987.4K
Ben Meneses-Sosa
Ben Meneses-Sosa@benhas·
@developerjack @JamesTechRec There was a follow up article that an executive in this dude’s company sent to his employees saying something like “when Tim referred to workers as lazy and entitled, he didn’t mean you”.
English
0
0
2
17
Ben Meneses-Sosa retuiteado
Dan Fangirl 🤓
Dan Fangirl 🤓@ChristyDanFan·
Why do we need a Voice? Still struggling to understand? Maybe this will help. Let’s do a hypothetical:
English
282
443
1.2K
70K
Ben Meneses-Sosa retuiteado
Gary Shteyngart
Gary Shteyngart@Shteyngart·
The woke mind virus is making me get the new Covid vaccine which ramps up my woke mind virus. It’s a vicious circle.
English
15
58
477
32.9K
Ben Meneses-Sosa retuiteado
Sally Rugg
Sally Rugg@sallyrugg·
Deliberately inflammatory & incredibly irresponsible for 7 to spread complete falsehood that “thousands of kids” transition and regret it. An utter lie. Plus, I know one of the people in the trailer. She was a 25yo adult when she chose to transition. No journalistic integrity.
English
2
158
972
73.6K
Dr Milan Milanović
Dr Milan Milanović@milan_milanovic·
𝗗𝗲𝗳𝗶𝗻𝗶𝗻𝗴, 𝗠𝗲𝗮𝘀𝘂𝗿𝗶𝗻𝗴, 𝗮𝗻𝗱 𝗠𝗮𝗻𝗮𝗴𝗶𝗻𝗴 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗗𝗲𝗯𝘁 𝗯𝘆 𝗚𝗼𝗼𝗴𝗹𝗲 In the latest paper by Google Engineers, they researched how to define, measure and manage Technical Debt. They use quarterly engineering satisfaction surveys to analyze the results. 𝟭. 𝗗𝗲𝗳𝗶𝗻𝗶𝘁𝗶𝗼𝗻 𝗼𝗳 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗗𝗲𝗯𝘁 Google took an empirical approach to defining technical debt. They asked engineers about the types of technical debt they encountered and what mitigations would be appropriate to fix this debt. This resulted in a collectively exhaustive and mutually exclusive list of 10 categories of technical debt, including: 🔹 Migration is needed or in progress: This may be motivated by the need for code or systems to be updated, migrated, or maintained. 🔹 Code degradation: The codebase has degraded or not kept up with changing standards over time. The code may be in maintenance mode, needing updates or migrations. 🔹 Documentation on project and application programming interfaces (APIs): Information on how your project works is hard to find, missing, or incomplete. 🔹 Testing: Poor test quality or coverage, such as missing tests or poor test data, results in fragility and flaky tests. 🔹 Code quality: Product architecture or project code must be better designed. It may have been rushed or a prototype/demo. 🔹 Dead and abandoned code: Code/features/projects were replaced or superseded but still need removal. 🔹 Team needs more expertise: This may be due to staffing gaps, turnover, or inherited orphaned code/projects. 🔹 Dependencies: Dependencies are unstable, rapidly changing, or trigger rollbacks. 🔹 Migration could have been better executed or abandoned: This may have resulted in maintaining two versions. 🔹 Release process: The rollout and monitoring of production need to be updated, migrated, or maintained. 𝟮. 𝗠𝗲𝗮𝘀𝘂𝗿𝗶𝗻𝗴 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗗𝗲𝗯𝘁 Google measures technical debt through a quarterly engineering survey. They ask engineers about which of these categories of technical debt have hindered their work. The responses to these surveys help Google identify teams that struggle with managing different types of technical debt. E.g., they found that engineers working on machine learning systems face different types of technical debt compared to engineers who build and maintain back-end services. They focused on code degradation, teams needing more expertise, and migrations being required or in progress. Then, they explored 117 metrics proposed as indicators of one of these forms of technical debt—the results were that no single metric predicted reports of technical debt from engineers. 𝟯. 𝗠𝗮𝗻𝗮𝗴𝗶𝗻𝗴 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗗𝗲𝗯𝘁 Over the last four years, Google has made a concerted effort to define better, measure, and manage technical debt. Some of the steps taken include: 🔸 Creating a technical debt management framework to help teams establish good practices 🔸 Creating a technical debt management maturity model and accompanying technical debt maturity assessment that evaluates and characterizes an organization's technical debt management process 🔸 Organizing classroom instruction and self-guided courses to evangelize best practices and community forums to drive continual engagement and sharing of resources. 🔸 Tooling that supports the identification and management of technical debt (for example, indicators of poor test coverage, stale documentation, and deprecated dependencies) It's important to note that zero technical debt is not the goal at Google. The presence of deliberate, prudent technical debt reflects the practicality of developing systems in the real world. The key is to manage it thoughtfully and responsibly. Check the full link in the comments. _______ If you like my posts, please follow me, @milan_milanovic, and hit the 🔔 on my profile to get a notification for all my new posts. Grow with me 🚀! #technology #softwareengineering #programming #techworldwithmilan #development
Dr Milan Milanović tweet media
English
20
527
2.3K
382.9K
Ben Meneses-Sosa retuiteado
Alexandra Peláez
Alexandra Peláez@allyouneedslove·
Hoy me convierto oficialmente en la madre de una niña de 17 años y, aunque no puedo creer lo rápido qué pasó el tiempo, me da muchísima emoción verla convertirse en un ser humano increíble. ♥️
Español
3
0
4
258
Ben Meneses-Sosa retuiteado
Chris Frantz
Chris Frantz@frantzfries·
when engineering gets invited to a sales call
Chris Frantz tweet media
English
266
2.6K
36K
2.4M