Helio

Isto, em Portugal, tinha atingido 2/3 do banco do Porto!

O Sporting não fala de arbitragens nem entra por esses caminhos, é legítimo, por isso teremos de falar nós. Aquilo que andam a fazer ao Zicky nas competições internas é vergonhoso. É a roçar o desumano. Estamos a falar dum jogador que é super correcto dentro de quadra, que não cria problemas com ninguém e respeita todos os seus adversários e marcadores directos, não há ninguém que não goste dele, e que continua a ser perseguido pelos árbitros como se fosse um rufia ou um jogador maldoso (é o total contraste disto). Neste momento, pode-se fazer tudo quanto se quer a Zicky. Agarrar, puxar, andar às cavalitas, empurrar, tudo. Não são averbadas quaisquer faltas, por mais evidentes que sejam. E pior ainda, faltas averbadas só ao jogador em si. Nestes últimos 3 jogos, se Zicky teve 1 falta assinalada sobre si foi muito. E ainda ontem “sofreu” 0 faltas, “cometeu” 3 faltas e até levou amarelo. E depois temos de ouvir os comentários sonsos dos pseudo-entendidos do Canal 11 que “Zicky faz muita falta ao futsal português” quando o pivot está lesionado e a ser gerido, quando nem se protege o jogador ou os atletas da sua posição. A continuarem a fazer tudo quanto querem sobre ele sem sanções, nenhum jogador dura muito tempo. Por fim, outros critérios e outras decisões. O primeiro golo do Braga no jogo 2 vem duma falta sobre Merlim no início da jogada, árbitros foram ao Video e disseram que não havia nada. Ontem, o segundo golo do Braga, à vista desarmada, não parece falta. Mas na repetição há um empurrão claro de Luís Fernandes nas costas de Wesley para ganhar posição (“não há qualquer infração”). Os mesmos árbitros que conseguiram vislumbrar uma falta de Wesley no seu golo anulado por uma “abordagem negligente” do jogador leonino, quando a agressividade média do Braga nos 3 jogos foi superior. Que as Finais tenham melhor arbitragem e que haja a coragem que não houve no ano passado, sobretudo no jogo 4.

Os outros é que espalharam os detergentes mas nós é que limpámos os títulos.

Nunca a expressão “roubar o segundo lugar” fez tanto sentido!

Há séculos de distância entre a @ligaportugal e a civilização do futebol

Só nos esquecemos de esconder bolas :(

🌋 𝐎𝐁𝐉𝐄𝐂𝐓𝐈𝐕𝐎: Pintar o Jamor de 🟢⚪️ #TaçaDePortugal

Caro @Educacao_PT, há alguma razão para o Portal das Matrículas limitar as inscrições ao Ensino Público nesta fase?

João Pinheiro não é uma pessoa séria. Qualquer Sportinguista, que um dia lhe aperte a mão, não merece nada. Não podemos ser amigos desta gente!

O treinador falhado, pago a peso de ouro, não pode acabar o campeonato atrás do tipo de Mirandela. João Pinheiro cumpriu a sua parte.

Tudo aquilo que eles reclamam que beneficia o Sporting já os beneficiou esta época.

Now that we've 100%ed code analysis, we are proud to embark on a new journey. Today, we’re applying our linting and scanning expertise to the tangible world. Introducing Codacy Lint ‘n’ Scan Hardware: A curated line of premium linters, scanners, and detection tools designed to solve real-world problems with the same precision we brought to your codebase. Check out our new collection: shop.codacy.com

Comunicado #SportingCP sobre as sucessivas ações que o FC Porto tem vindo a protagonizar nos últimos tempos. 👉 bit.ly/4tgctki

O crime não compensou! Contra tácticas bafientas, uma exibição sólida feita por gente séria!

É cada vez mais claro que não podemos ser amigos desta gente! As federações são as maiores culpadas desta impunidade. Portugal nunca foi um país muito sério mas o Porto definiu um novo mínimo para o nojo!

⚙️ VS Code started as a 10-person team building an editor. Ten years later, it’s used by millions of developers, supports 90K+ extensions, and has become a foundation many AI tools build on. In this behind-the-scenes conversation with @codacy, we talk about the early pivots between web and desktop, the bet on open source, why performance and core editing still matter as much as AI, and how agents are starting to shape what comes next. 📖 Read the full interview: blog.codacy.com/how-vs-code-qu…

The biggest takeaways/nuggets from my interview with @GeoffreyHuntley on AI-native software engineering and the Ralph loop: 1. Software development and software engineering are now two different professions, and one of them is over. Software development, the work of translating tickets into code, can now be done by anyone for $10-42/hour while they sleep. Software engineering, architecture, security, requirements breakdown, understanding failure modes, is where humans still matter. If you identify as a "software developer," you're competing against a bash loop. If you identify as a "software engineer," your job is to orchestrate the loops. 2. The moat you think protects your software product doesn't exist anymore. Geoffrey argues you can clone any SaaS product, even those with BSL licenses or proprietary enterprise code, using AI. He ran Ralph in reverse on HashiCorp Nomad's source code to generate clean-room specifications. When he hit gaps from missing enterprise features, he ran Ralph over their marketing materials and product docs to fill them in. Any company relying on licensing or code secrecy as a competitive moat needs to rethink their strategy. 3. Cursor, Windsurf, and every other AI coding tool are essentially the same thing: a loop that automatically copies and pastes. Geoffrey built these tools professionally and says the harness does almost nothing; the model does all the work. There's no real moat in the harness business when you're reselling tokens. The only differentiator is taste and UX. Stop evaluating tools and start learning the underlying patterns. 4. Ralph is not a product. It's an orchestrator pattern for running thousands of AI loops. The simplest version is a bash loop that deterministically allocates memory, lets the LLM pick one task, executes it, then starts fresh. The key insight: every loop gets a brand new context window. You avoid compaction (where the AI gets dumber as context fills up) by never letting the context window accumulate competing goals. Your institutional knowledge lives in specification files, not in the context window. 5. Specifications are the new source code. Geoffrey's workflow: spend 30 minutes in conversation with AI, drilling into requirements, making engineering decisions, building up specs. Then throw those specs to Ralph and get weeks worth of work in hours. The specs act as a "pin" that reframes every fresh loop with your domain knowledge. He doesn't hand-write specs. He code-generates them through structured conversation. Prototypes are now free. Refactoring is cheap. 6. The entry-level path into software engineering is closing fast. Geoffrey's company stopped hiring juniors for a year until they figured out how to interview for AI-native skills. There's already a cohort of juniors who've been practicing these techniques for six months. They'll work at a quarter of senior wages and outship them. If you're just picking up these tools today, you're behind. The new interview question: can you explain how to build a coding agent on a whiteboard? 7. Senior engineers who refuse to adapt are in more danger than juniors who embrace it. Geoffrey sees respected engineers taking hardline stances against AI ("it's installing fascism in your codebase"). Meanwhile, leadership teams are discovering Ralph and realizing three people can run the output of an entire org. When commit velocity and product velocity diverge that dramatically between adopters and non-adopters, founders notice. The hard line is coming. 8. AI is an amplifier of operator skill, not a replacement for it. If you're great at security and you get good at AI, you become a weapon. If you're mediocre and you use AI, you're still mediocre, just faster. The skill gap comes from "discoveries": learning the tricks, the loop-backs, the ways to close the automation loop. These techniques don't have standardized language yet. We're inventing the terms for the new computer every day. 9. Open source may no longer make sense for most use cases. Geoffrey, a former prominent open source maintainer whose land was funded by Open Collective, no longer uses open source libraries. His reasoning: every dependency injects a human into the loop. If there's a bug, you open a PR, chase a maintainer, wait. That's not automation. Instead, code-generate what you need. The exception: don't generate cryptography or security-critical code unless you have the domain expertise to verify it. 10. Programming languages now have a tier list based on how well AI agents can work with them. S-tier: Rust, TypeScript (especially with Effect.js), Python with Pydantic. These are source-based with strong type systems that reject invalid generations and work well with ripgrep for code discovery. F-tier: Java and .NET. Their DLL-based dependency systems don't work natively with the search tools AI agents use. The tradeoff with Rust: compilation is slow, so bad generations cost more time. 11. Corporate AI transformation programs are dangerously slow. Three-to-four-year rollouts with coaches and committees won't cut it when three founders in Bali can Ralph your entire product and undercut your pricing by 99%. Smaller teams ship faster. By the time the transformation is done, the market has moved. Geoffrey calls this the "Titanic moment": the boat is full, get the next boat. 12. We have a new computer, and that's why the legends are coming out of retirement. The last 40 years of computing decisions were designed for humans: TTYs, environment variables, slow language evolution to avoid breaking mental models. Now we have robots. What's the bare minimum a robot needs? Geoffrey sees this as the most exciting time in computing. If you're not excited about what you can now build, you haven't truly picked up the new computer yet.

Bem, se o Santa Clara nos oferecesse golos destes, nós não tínhamos de gastar dinheiro nos árbitros!!

É comparar este lance com o do Gonçalo Inácio. É a @ligaportugal que escolhe o campeão.

Ainda não li nem ouvi os que estavam preocupados com a arbitragem portuguesa, com cantos mal marcados e toques na cara. O jogo em Barcelos não foi da liga portuguesa?