home.social

Search

1000 results for “e_nomem”

  1. Grande parte do tempo dos médicos do SNS não se gasta a decidir: gasta-se a reconstruir e registar o caso clínico. Falta um botão de IA e um microcurso que dá acesso aos médicos que o quiserem. Opinião de Pedro Reis Pereira

    publico.pt/2026/10/26/opiniao/

  2. Minha mãe disse que tá tendo festa no Parque Atheneu. Isso é lindo. Pra quem não sabe, é um bairro onde moram milhares de policiais civis e militares, então comemorar eleição do Lula lá é uma ousadia da minoria. 😂 🤣

  3. europesays.com/pt/566160/ Liverpool está louco com um intocável do Sporting e há um dado que ajuda a perceber porquê #Desporto #Liverpool #Portugal #PT #Sporting #Sports

  4. Ei, fediverso, tenha compaixão e ajude minha amiga. Hoje é o aniversário da mãe dela!

    Sabi é uma mulher indígena, PcD, cuidando da mãe idosa que sofre de demência. Elas tão se recuperando de uma estadia no hospital.

    Se você puder ajudar, manda um pix pra mim (obs. “Sabi”)

    [email protected]

    Mas se puder mandar qualquer valor direto pra ela em dólar, é melhor

    paypal.me/SabiLewSounds

    13 pessoas mandando 50 reais mantém as duas abrigadas hoje dia 27. E dêem buste nesse post. Obrigade!

    #Fediverso #FediBR #MastodonBR #mastodonAjuda #Apoio #ApoioMutuo #AjudaMutua #SuporteMutuo #Suporte #Doacoes #PcD #PessoaComDeficiencia #Indigena #Ajuda

  5. AGAIN!!!

    !!! LULA WON !!!! 🇧🇷

    É TETRA!!!!!!!!!!!!!!

  6. TikTok, Instagram et Facebook : 18 comptes à suivre à Strasbourg quand on est étudiant(e)

    Pour s’intégrer complètement dans la vie strasbourgeoise et en connaître toutes les réf’, rien de mieux que de…
    #Strasbourg #FR #France #Actu #News #Europe #EU #actu #Actualités #étudiants #europe #Facebook #GrandEst #Guideétudiant #Guideétudiant2026 #Instagram #Républiquefrançaise #Réseauxsociaux #TikTok
    europesays.com/fr/1265600/

  7. NUNCA ESQUEÇAM A FORÇA DA MOVIMENTAÇÃO POPULAR. O QUE SALVA A DEMOCRACIA É GENTE NA RUA. ✊🏻!!!

  8. Korea retail investors boost ETF buying past 8 trillion won despite volatility

    Illustration = ChatGPT DALL·E /Courtesy of Although the domestic stock market has shown high volatility and continued an…
    #EuropeSays #Korea #KR #KoreaExchange #KOSDAQ #KOSPI #KRX #securities
    europesays.com/korea/201893/

  9. News 📌

    👤 The Cure 📈 80 👥 7,8M

    🔗 “ha cambiato le regole dell’industria”

    Robert Smith e Jordan Rakei saranno tra i protagonisti degli Artist & Manager Awards 2026, i riconoscimenti organizzati dalla Featured Artists [...]

    a cura di Claudio Fabretti

    #Ondarock #MusicianSky #MusicSky #Music

    The Cure

  10. News 📌

    👤 The Cure 📈 80 👥 7,8M

    🔗 “ha cambiato le regole dell’industria”

    Robert Smith e Jordan Rakei saranno tra i protagonisti degli Artist & Manager Awards 2026, i riconoscimenti organizzati dalla Featured Artists [...]

    a cura di Claudio Fabretti

    #Ondarock #MusicianSky #MusicSky #Music

    The Cure

  11. The First Siege of Missolonghi began OTD in 1822 during the Greek War of Independence cromwell-intl.com/travel/greec

  12. Korea retail investors shift to S&P 500 ETFs as KOSPI volatility surges

    Illustration = ChatGPT DALL·E 3 Competition is intensifying between “TIGER U.S. S&P 500” and “KODEX 200” for the…
    #EuropeSays #Korea #KR #KoreaExchange #KOSDAQ #KOSPI #KRX #securities
    europesays.com/korea/201805/

  13. 🇧🇷Este foi meu primeiro teste em pintar algo mais complexo em aquarela. Este é um farol localizado em Skagen no extremo norte da Dinamarca. Pintura feita a partir de uma foto feita por mim.

    🇬🇧This was my first attempt at painting something more complex in watercolor. This is a lighthouse located in Skagen, at the northern tip of Denmark. Based on a picture I took


    #aquarela #watercolors #farol #lighthouse #study #denmark #art

  14. The reported bug was a carrier lookup returning 404 because an international phone number never reached E.164 normalization. The traceback pointed at normalizePhone. The agent searched the repo for "normalize", got back normalizeEmail, normalizePhone, and normalizeAddress, picked the first match, and spent the pass rewriting normalizeEmail into a prettier helper. It wrote a few unit tests against that helper, went green, and reported done. The original phone path never changed.

    A keyword search returns a naming family, not a call graph. The agent matched tokens, not the failing symbol, and "I edited a function called normalize" became "I fixed the bug."

    Why it lands on the lookalike


    A broad search ranks by token overlap. Every normalize* function scores well on the same word, and nothing in the loop asks which symbol appears in the failing stack frame. The agent sees three interchangeable helpers and treats the first as the obvious target, because the traceback's exact function name was never pinned to the task as an anchor.

    Naming families invite the slip. When normalizeEmail, normalizePhone, and normalizeAddress live near each other and share a similar signature, they read as one generic utility even though their callers, inputs, and failure modes differ. The agent refactors the shared-looking helper rather than the one on the failing path, and its own new tests cover whatever it touched, so green confirms the edited code, not the reported bug.

    The human review helps it through: we skim the diff for a sensible-looking cleanup, see tests pass, and miss that the edited function never appears in the original traceback.

    The tells that the wrong function got fixed


    • The edited symbol is absent from the failing stack trace. Compare the function in the diff against the frame in the original report; if they differ, the edit never sat on the failing path.
    • The failing test references a different symbol. A green suite built around normalizeEmail says nothing about normalizePhone; the new tests target the helper the agent chose, not the failure someone filed.
    • The original repro still fails on the exact input. Feed the reported phone number back after the fix; a silent 404 that still appears means the untouched path stayed untouched.
    • The diff touches a happy path that already worked. A cleanup of an unrelated normalization function reads as polish, not a carrier-lookup fix.
    • The agent describes the change generically ("improved normalization") instead of naming the failing endpoint or stack frame.


    Anchor the failing symbol before editing


    The cheap guard is to pin the exact symbol from the traceback into the task before the agent touches anything: the module, function, and file the stack names are the only legitimate targets. A broad keyword search may surface neighbors, but none of them may be edited until the failing one is resolved.

    • Require a before/after repro run on the original input. The agent must run the failing case before the edit and again after, and the second run has to pass on the same reported input. A clean helper with no connection to the repro fails this gate.
    • Check callers against the failing request. After choosing a symbol, grep its call sites and confirm one matches the reported request path; if none lines up, the match is a near miss.
    • Search from the stack frame, not the keyword. Start from the frame the traceback names, then walk outward to siblings; do not let a generic token list pick the target for you.
    • Attach the minimal failing case to the agent. When the repro stays visible through the session, done means that specific input behaves, not that an adjacent helper got cleaner.


    Edited is not fixed


    Green after a near-match cleanup proves only that the touched function passed its own new tests. Pin the symbol from the traceback, run the original repro before and after, and make sure the edited call site matches the failing request. When the agent patches the first lookalike it finds, the bug did not move; the agent just worked on the wrong page.#aiagents #aicode #contextengineering #codereview #software #coding #development #engineering #inclusive #community
    The agent patched the lookalike function from a keyword search, so the failing symbol stayed broken

  15. @space @jonas

    And a little extra tip for your posts in the fediverse. Add some hashtags (e.g. #fieldrecording) so people who don't follow you find your stuff easier based on their interests/ preferences they have set up here. (Cause no algorithm actualy means no algorithm)
    I discovered a lot of interesting people/ stuff on here searching through these hashtags.

Share on Mastodon

Enter the server where you have an account.