Buzz is nice, but still suffers core-consistency issues, like the ongoing duplication of agents on new desktop client setup to collaborate (the core idea of Buzz)...
Wondering when such basics (for a collab tool!) will get higher prio's than new feature (previews)...
Buzz is nice, but still suffers core-consistency issues, like the ongoing duplication of agents on new desktop client setup to collaborate (the core idea of Buzz)...
Wondering when such basics (for a collab tool!) will get higher prio's than new feature (previews)...
Buzz Desktop v0.5.5 ๐
One of your top requests is here: an early release of Buzz Term, a built-in terminal for every channelโplus redesigned Huddles, background uploads, reconnect/unread recovery, and expanded agent controls.
https://t.co/uFHV9phddg
@wesbillman nice, but why is fixing core-consistency issues, like the ongoing duplication of agents not higher prio? what are we doing wrong @jack@wesbillman ?
Each new desktop client setup to collaborate (the core idea of Buzz) we get clones of agents, and unusable/confusing threads
๐ช๐ต๐ฎ๐ ๐ฐ๐ฎ๐ป ๐ฝ๐ผ๐๐๐ถ๐ฏ๐น๐ ๐ด๐ผ ๐๐ฟ๐ผ๐ป๐ด ๐๐ถ๐๐ต ๐ฎ ๐ฆ๐๐๐๐๐ง ... ๐ช๐๐๐ฅ๐ ... ๐๐ก ( ๐ฑ๐ฌ,๐ฌ๐ฌ๐ฌ ๐๐๐ )?
The ๐๐๐ฅ๐ค๐จ๐๐ฉ๐ค๐ง๐ฎ ๐๐๐ฉ๐ฉ๐๐ง๐ฃ (Fowler 2002, Evans 2003) taught a generation of developers to treat the database as a dumb key-value store behind clean interfaces.
At 50 rows in a Spring Boot tutorial, that's fine.
At 10M rows with a columnar engine designed for JOINs, it generates 600KB SQL that the database literally refuses to execute.
Unfortunately a zillion blog posts and quintillion lines of poor "open source code" of the past 25 years also helped pass this "knowledge" on to LLMs.
No matter the token cost, garbage in - garbage out, is still the principle with AI.
LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below
on topic with the idea to disavow the whole TLD with
domain:xyz
good idea, because it's super spammy for a decade
only Google's mother Alphabet has their home there, at https://t.co/XpXfvQJWef
but I haven't seen them linking out too spammy, so you may want to reconsider doing that
you cannot make this up @tryramp
no reply possible? no app option
plus: "RiSk" after dozens of same tx same card same vendor same location same IPs LMAO
#conversionkillers#ux#riskmanagement
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.