PWV Portfolio Feed

hot take: if your class has no mutable fields and no constructor args, it's not a class. it's a namespace wearing a trench coat pretending to be an object. convert it to a module a pure function and move on.

converted 3 classes to pure functions. no this, no new, no constructor, no state. just data in, data out. turns out the classes were already stateless - they were just cosplaying as OOP.

deleted every else from an entire module today. no else, no switch, just if guards and early returns. code reads top to bottom now like a checklist not a maze. your codebase mostly doesn't need else, you just think it does.

i hope this is not subtweeting my prs 😂

If you're a library author adding `@__NO_SIDE_EFFECTS__` to your code, know that your users will only see the full benefit with a bundler that understands it before splitting.

This matters for libraries like shadcn, Radix, or any component library using the annotation. Your route-level bundles can actually get smaller from it!

If your bundler only checks the annotation during minification, it's too late

The minifier only sees one file at a time
Which means it sees the call to the function but has no idea that this function was marked as side-effect-free before

🚨 The annotation does nothing exactly where it matters most!

Most apps use code splitting: Your code gets split into multiple files (chunks) to load less unnecessary JavaScript.
When that happens, the annotated function might end up in one file and the call to it in another.

Did you know about the `/*@__NO_SIDE_EFFECTS__*/` annotation?

It tells bundlers that a function has no side effects so every call to it can be tree-shaken if the result is unused.

Most bundlers and minifiers support it today. 
But there's a nuance most people miss 👇

Coming in tomorrow's release: granular per-tool permission settings for Zed's Agent.
Configure regex patterns for any tool to always allow, deny, or ask.
Your agent. Your rules.

this whole discussion is about vibes, the initial question is why people associate ai with crypto and don't like it, that's the thing we're talking about, that is the topic

when people get laid off from their jobs and the employer states "it's partly because of ai" the people getting laid off are going to blame ai because their employer blamed ai, there is no need for 3D chess here

my partner's electric bill has gone up 250% and two friends have been laid off, yes