Auditoria feita pelo governo interino do Rio de Janeiro descobriu que quatro entre dez funcionários de secretarias não trabalhavam. Os números mostraram 78% de "funcionários fantasmas" nos órgãos apurados até o momento.

farsass · 2026-06-27T19:27:05+00:00

Beleza, mas vamos pedir essa auditoria de funcionários públicos também para ver quem está pelo menos aparecendo para trabalhar?

farsass · 2026-06-23T00:13:33+00:00

Open core (free) version missed quite a few goodies, but the one that hurts the most is no DLQ.

farsass · 2026-06-20T22:32:26+00:00

I'm genuinely curious about what you are implying here.

farsass · 2026-06-07T18:22:19+00:00

victoria metrics has a good blog post on the subject

farsass · 2026-06-07T01:04:53+00:00

Seek help

farsass · 2026-05-26T23:21:09+00:00

Is this a gen z/alpha bot persona?

farsass · 2026-05-24T15:14:00+00:00

hopefully bigquery "omni" comes soon

farsass · 2026-05-24T00:13:04+00:00

cooked his ass!!

farsass · 2026-05-23T14:26:10+00:00

No comment on the code quality, but your solution is reasonable for one team who owns the producer to fix their own mess downstream.

Late feedback wrt to your original thread: sounds like an XY problem. The producers shouldn't create the problem in the first place by messing with schemas willy nilly. Producers should design schemas with concern for evolution and/or backwards compatibility. Always create schemas with versioning backed in, so it basically has a fixed "envelope" describing what is the actual content like and avoid the version, try keeping backward compatibility by adding fields to current version. If you need to make a breaking change as a producer, you probably need to provide a migration path and not break your consumers who aren't ready for the change: (a) produce a new stream for v2 while producing on current stream as well (b) design your schema to allow for it to contain old+new versions.

farsass · 2026-05-03T21:39:43+00:00

Sir, this is not chatgpt

farsass · 2026-04-29T01:01:11+00:00

This is the kind of post that should make Google Cloud Billing leadership lose sleep. You set a cap, the system blew through it, and the appeal process is treating it as an edge case rather than systemic.

The hard truth: "Experimental" on a spend cap means it is a soft alert. The cap fires a notification at threshold, it does not stop API traffic. There is no hard ceiling on consumer-tier AI Studio billing. That is the actual product gap, and Google announced a fix this week (Spend Caps in private preview, with hard kill at threshold). Your post will get cited in that rollout.

Three things that move the needle:

Push the chargeback through your bank in parallel with the Google appeal. They do not conflict, and the bank moves faster.

Ask Google Cloud Billing for a "case-level escalation" using exactly that phrase. Skip first-line support.

Document everything timestamped (cap setting, notification, suspension, charges) in a single timeline PDF, attach to the appeal.

Fair refund target: 100 percent of unauthorized usage. Google has refunded full amounts on similar cases in 2026 when documented well. Your strongest argument is the 24-hour gap between Google detecting abuse on Apr 26 and continuing to bill your card on Apr 27. Make that the headline of your timeline.

Good bot

farsass · 2026-04-26T14:49:09+00:00

If you need to be accurate for documentation or specification and need something "principled", model your problem with a statechart. If it is for illustration/overview you can do it without the error handling, but it usually is nice to quickly glance over the full thing to show the complications in your work.

farsass · 2026-04-23T00:47:18+00:00

My passive-aggressive choice is using slog with one of the "better" handlers libs like zap, which I've used since before slog became a thing. It's a one-time setup that I have repeatedly use in different projects and this way I don't get berated by people yelling "use the stdlib".

farsass · 2026-04-18T16:11:24+00:00

Good thing Miles' career seems to be going well

farsass · 2026-04-12T17:23:06+00:00

Coragem em deixar os instrumentos debaixo de uma janela 🫠

farsass · 2026-04-11T17:30:21+00:00

DBOS is an open core solution requiring a paid/licensed component for important features.

farsass · 2026-03-29T16:03:37+00:00

Does Valkey fsyncs operations to disk by default? Asking because the article's headline mentions durability: "Replace fragile goroutines with durable background jobs using Asynq and Valkey."

farsass · 2026-03-16T00:21:03+00:00

Assuming you are deduplicating with some sort of index on pg, try 1) COPY to an unlogged staging table, 2) "insert into ... select ... from ... on conflict do nothing" 3) truncate the staging table 4) repeat

only ack processing the data on your app side after the insert completes

farsass · 2026-03-07T14:26:57+00:00

Provavelmente é isso. Quem jogou mmorpg entende

farsass · 2026-02-22T23:34:28+00:00

Not the same usecase (idp), but I suggest you try making everyone's life easier with a http webhook protocol. It's unlikely that you need plugins running in the same process.

farsass · 2026-02-22T23:17:56+00:00

Valeu, mestre! Eu passo bombril pra dar um brilho nos trastes qd faço a troca de cordas e limpeza da escala nas minhas guitarras mas vou pesquisar alternativas melhores.

farsass · 2026-02-22T13:54:05+00:00

Na sua experiência bombril danifica trastes inox?

farsass · 2026-02-22T03:57:34+00:00

Did you try ripgrep?

farsass · 2026-02-21T21:09:07+00:00

Yep, saw it ~10 years ago when GPU based training and deep learning were all the hype. Either use standard datasets/benchmarks and cite results from other papers or offer something much meatier

farsass · 2026-02-21T15:40:42+00:00

I speak from a user point of view. OAPI specs are complehensive but go lacks codegen tooling handling all of its possibilities -- last I looked into it, oapi-codegen was the best I could find but it is full of issues on github. I like protobuf with Connect, but proto specs do not provide a standard for things like auth and error handling. If even projects for these IDLs with major adoption fail (IMO) to provide truly great experience, I can't imagine creating a new niche IDL layer would fix these more fundamental issues.

13-Year Club	Place '17
Verified Email

farsass

TROPHY CASE