Placca

Think tap create

[IT Unprofessional @it_unprofession]

We hired a new VP of Engineering who is obsessed with agile methodology.

He called a meeting on his first day and said we need to transition to 2-week development sprints.

He wanted daily stand-ups, retrospective boards, and continuous deployment pipelines.

He wanted us to actually write new code.

I realized immediately that he was an existential threat to my lifestyle.

I let him finish his impassioned speech about workflow velocity.

Then I stood up, walked to the whiteboard, and drew a single horizontal line.

I told him agile sprints are a localized solution for a localized mindset.

I said our infrastructure operates on a Zenith Release Cycle.

He asked what a Zenith Release Cycle was.

I told him it's a holistic, macro-stabilization framework where we observe the system in a state of prolonged stasis.

By not touching the code for 18 months, we allow the legacy dependencies to organically settle.

I told him that deploying bi-weekly updates creates micro-abrasions in our database architecture.

I used the phrase chronological data scarring.

The CEO was in the room and audibly gasped.

He told the new VP that we can't risk chronological data scarring just to satisfy a trendy tech buzzword.

The VP looked at me like I'd just invented a new color.

He was completely paralyzed by the sheer density of my fabricated jargon.

He quietly agreed to adopt the Zenith Release Cycle.

We're officially scheduled to deploy our next update in the third quarter of 2027.

I spent the rest of the afternoon buying things I don't need on Amazon.

Agile is a disease invented by people who want to be punished for their salary.

I refuse to participate in my own suffering.

[Karen X. Cheng @karenxcheng]

i hooked up a rotary phone from the 1920s to an AI agent, that replies on a mechanical display

it’s like a dumbphone without distracting notifications

here’s how i built this w/ @cursor_ai

[Placca @pyplacca]

@lusionltd Beyond impressive 🔥

[Taylor Otwell @taylorotwell]

Been coding with AI a lot this week and it's wild how much of an edge real architecture knowledge still is.

Seeing frontier models constantly reach for the wrong abstractions. Easy to course-correct, but only if you already know what good looks like.

[Wise @trikcode]

Why are we even calling them "agents" instead of "scripts that use LLMs"?

Because most "agents" I've seen are just:
1. Prompt
2. Call API
3. Parse response
4. Loop

That's... a script.

[Placca @pyplacca]

@xghana_ As an able man dierrr this is a no-no

[Placca @pyplacca]

@DutchKafir How’s that “her experience” if she never experienced it? Sigh!

[Mo @atmoio]

Europe is noping out of AI lmao

[Deedy @deedydas]

Most software engineers are facing an identity crisis bordering on depression.

As CTOs aggressively evangelize tokenmaxxing, a class divide ensues.

The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working.

The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy.

This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.

[Lxyv @wholyv]

Math behind being 10% better every week

[Placca @pyplacca]

Beautiful chaos

[ロアネア@Youtube&TikTok登録お願いします @roaneatan2]

世界がうまく出来ていた場合

[Alex Zajac (🍔,🧠) @itsalexzajac]

A developer posted this on Reddit, and I haven't stopped thinking about it.

[开发者Hailey @IndieDevHailey]

🔥 前端动画界的老大 GSAP，又扔出了一颗炸弹：gsap-skills！

90% 的网页动效只是乏味的淡入淡出，但 Apple 风滚动、数据可视化动画、沉浸式产品页背后的秘密，全在 GSAP。

GSAP 官方直接放出 gsap-skills：
支持 Cursor、Claude Code、Copilot、Google Antigravity、Windsurf 等��乎所有主流 Agent，自动识别。

神亮点：
- 25+ 高级动画实战案例，一键学会 Timeline、ScrollTrigger、Ease 等核心技能
- 让 AI 或开发者都能瞬间生成丝滑、专业、高级感爆棚的动效
- 免费开源，商业项目直接用
- 性能极致流畅，复杂动画也不卡顿
- 跨框架支持：React、Vue、Svelte、原生 JS 全覆盖
- 官方教程 + 实战案例 = 动效学习最快捷径

GSAP 本身已全部免费（原 Club 高级插件全部白送），现在再加上这套官方 skill，装完直接甩需求给 AI，感受 Apple 级动效秒出的爽感！

[Google Gemma @googlegemma]

Introducing the newest Coral board, for efficient, on-device AI!

Check out the demos in the video:
- On-board speech translation
- Natural language controlling hardware
- Vision & sound generating music

[Placca @pyplacca]

@ShoeNeeds @koboateng @kojowestgh Minister of communication that lacks communication skills

[Placca @pyplacca]

@koboateng @koboateng , I think you might have overstepped

[Placca @pyplacca]

@koboateng Does he mean to tell us NITA is lying, cuz I’m sure we all see “Minster’s Instructions” in the second screenshot?

[Placca @pyplacca]

@samgeorgegh @koboateng A lie can travel halfway around the world while the truth is putting on its shoes

- Mark Twain

[Nana B. @koboateng]

A minister went live on national television, visibly excited that he had finally found a “gotcha moment” against ordinary Ghanaians.

Why? Because a draft bill was published on the ministry’s official website, then quietly revised four different times through closed-door meetings without properly communicating any of those changes to the public.

After that, he confidently says:
“The old bill is dead. You people are online criticizing a dead bill. You don’t have the updated bill.” As if secrecy, poor communication, and public confusion are achievements.

You are pushing 15 digital bills that will affect millions of citizens, businesses, creators, and young people, yet the public engagement has been chaotic from the beginning. Instead of transparency, accountability, and respect, citizens are being mocked on live TV for reacting to the only version they were officially given access to.

Leadership is not a game of catching citizens off guard. If people are confused, the failure is in communication, not in the public asking questions. This is not it.

Ghana is failing us.