Elekto Produtos Financeiros

A Elekto produz sistemas para o mercado financeiro: pricing, risco, compliance. Software de alta performance, confiabilidade e rigor.

[Elekto Produtos Financeiros @Elekto_Software]

Especialmente em Data Marts, onde há muita informação não-normalizada, e texto, os ganhos de espaço podem ser significativos.

Onde I/O é mais custoso, também ganha-se em performance.

E o custo adicional de CPU é mínimo em ambientes modernos.

[Elekto Produtos Financeiros @Elekto_Software]

Precisando otimizar espaço e performance no SQL Server?

Aqui uma proc que (des)comprime tabelas(s) e índices de forma prática e segura: suporte a PAGE/ROW, filtros, dry-run e controle de tempo.

Script completo:
https://t.co/EmmiQbiFo3

#SQLServer #Performance

[Proton VPN @ProtonVPN]

01000011 01100101 01101110 01110011 01101111 01110010 01110011 01101000 01101001 01110000 00100000 01101001 01110011 01101110 00100111 01110100 00100000 01101110 01101111 01110010 01101101 01100001 01101100 00101110

[Elekto Produtos Financeiros @Elekto_Software]

@jerryjliu0 Nice to have you around.

But, on a fundamental level, we have to improve PDF for easy machine reading, or replacing the format.

PDFs are already massive, including the machine readable text, maybe a Markdown embedded.

But this introduces other issues, injection, hidden text...

[Elekto Produtos Financeiros @Elekto_Software]

@azamsharp Yes, but they move. Slowly as a glacier, but even a glacier reaches the sea, eventually.

But you have a point: corporate developers on old school corporations have more time to adapt.

[Elekto Produtos Financeiros @Elekto_Software]

@cortez8624 @TheHackersNews "Communist" China.

One of their sponsored groups.

[Elekto Produtos Financeiros @Elekto_Software]

@guisousalo1 @RicardoCappelli O Brasil não sabe sequer colocar um, apenas um, bem pequeno, satélite em órbita.

[Elekto Produtos Financeiros @Elekto_Software]

@andreeliasdev Gerenciamento de contexto.

Janelas menores, como instruções para um estagiário movido a cocaína, mas genial, porém com tendência a esquecer o que estava fazendo.

[Branko @brankopetric00]

You have 12 monitoring dashboards, 47 alerts, and 3 observability platforms.

You still found out about the outage from Twitter.

Your observability stack:
- Datadog: $5,000/month for metrics no one looks at
- New Relic: $3,000/month for traces that confuse everyone
- PagerDuty: $1,000/month for alerts everyone ignores
- Grafana: Because pretty dashboards solve everything

Real observability: knowing your system is broken before your customers do.
You have expensive noise, not signal.

[DHH @dhh]

Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table.

Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication.

Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.”

Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it.

The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks.

Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.

[Elekto Produtos Financeiros @Elekto_Software]

@ayubio Um erro é um erro, mas o candor deles é louvável.

[Elekto Produtos Financeiros @Elekto_Software]

Embora lamentável, afinal um erro é um erro, é um erro... O candor da Cloudfare é absolutamente louvável.

[Dane Knecht 🦭 @dok2001]

You can read the details of what went wrong this morning in the post below. We let the Internet down again today; We’re locking down all changes in order to ensure we have better mitigation and rollback systems before we begin any again.

https://t.co/oo1xJ2NsOK

[Elekto Produtos Financeiros @Elekto_Software]

@awesomekling As the copyright owner you can do better: dual license, GPL, and "ask for a custom commercial license".

Why"prevent" if you can PROFIT?

As for "bad actors"... Indeed, one must clearly state what this means.

[Elekto Produtos Financeiros @Elekto_Software]

Feature muito bacana agora é possível no
.Net 10: Um pipe operator!

Mas ao abrir um codebase novo, encontrar isso...

Parece perigoso... Amei!

https://t.co/oRAwQsXClB

[Elekto Produtos Financeiros @Elekto_Software]

@gunnarmorling It's not only in Brazilian politics that people do Freestyle Charting...

[Elekto Produtos Financeiros @Elekto_Software]

@unixterminal Indeed!

I just saw that the very old Notepad can do formatting now, by virtue of markedown and I found it awesome!

Typora still is my preferred markdown editor, as it's packed with features, but for casual editing, works just fine.

Great upgrade.

[Elekto Produtos Financeiros @Elekto_Software]

Resumo: .NET 10 transformou C# em uma linguagem ótima para pequenos utilitários. NetTestDrive é um exemplo real, simples e funcional. Fica o repositório, para quem quiser testar o “512 GB por R$ 29”:

https://t.co/pL7zAWnEmP

[Elekto Produtos Financeiros @Elekto_Software]

O .Net 10, recém lançado, trouxe algo que deveria ter sido feito fazem pelo menos 10 anos: rodar um arquivo C# como se fosse um script, sem projeto, sem cerimônia.

dotnet run NetTestDrive.cs

Simples, elegante, rápido. Sem bash, bat ou PowerShell... 🧶

[Elekto Produtos Financeiros @Elekto_Software]

O NetTestDrive faz justamente o que ferramentas como F3 (Fight Flash Fraud) fazem no Linux:

- preenche o dispositivo com arquivos de dados aleatórios
- calcula SHA512 durante a escrita
- grava um manifesto
- relê tudo e verifica se o que você escreveu é o que você leu 🧶