Michael Esch

@mark_k @xai the question is, when are we getting grok build? and can we replace with it claude code/codex?

Grok 4.20 is criminally underrated. Don't let the haters distract you, try it for yourself. @xai was seriously cooking with this model. And it's just the beginning, a stronger version is coming soon.

@rierikawaii since you mention them now... it will probably change ^^

何か最近はめちゃくちゃアメリカ大陸の方々と交流しているけど、 イギリス人とかフランス人とかドイツ人はあまりいないな😂

I think this is a signal to make my own CRM.

I started testing a CRM on sunday. Monday, I got the first call. Tuesday, I got a second call. Wednesday (now), I got the third call. Every time the same questions... This is a high indicator that their CRM isn't good. Can you guess, what CRM I am talking about?

@AvieDev i expect it to be true, because for US, it wasn't april yet.

Wait, I forgot it’s April Fool’s Day!!! The Oracle layoff news is not true right?

@miguelgbandeira yes and no. yes if you need to work in a team and the team has already decided. no, if you just work for clients and they want solutions to their problems.

does the tech stack even matter nowadays?

@techdevnotes Do you believe it will come? Do you believe it will be good?

Are we expecting Grok Build in April ...

April Fools Day is the worst. Every changelog every announcement and every client email suddenly turns into something you cannot trust. Why does this day even exist.

@ryanels no risk, no fun ^^

@FirozCodes For daily work I still find Claude strongest in 2026. I am experimenting since some weeks with cowork and let claude do other work around coding ^^

In 2026 , which AI is best for coding ?

🚨 The axios npm package was hit by a serious supply chain attack today (March 31, 2026).The primary maintainer's npm account (jasonsaayman) was compromised — attackers changed the associated email to a ProtonMail address and used those credentials to publish two malicious versions directly to npm:axios@1.14.1 (mailto:axios@1.14.1) (newest 1.x line) axios@0.30.4 (mailto:axios@0.30.4) (legacy 0.x line) These versions sneaked in a hidden new dependency called plain-crypto-js@4.2.1 (mailto:plain-crypto-js@4.2.1), which isn't imported or used anywhere in axios's actual code. Its only job was to run a postinstall script that acts as a dropper for a cross-platform Remote Access Trojan (RAT) targeting Windows, macOS, and Linux.The malware:Connects to a command-and-control server (reported IOCs include sfrclak[.]com:8000 and IP 142.11.206.73) Downloads and executes platform-specific payloads Deletes itself and overwrites files (like package.json) to cover its tracks Axios is one of the most popular packages on npm (100 million weekly downloads depending on the source), so even projects that don't directly depend on axios could be affected if any transitive dependency pulls it in via a loose version range like ^1.14.0.Timeline highlights (UTC times, March 31, 2026):Malicious plain-crypto-js@4.2.1 published shortly before axios@1.14.1 (mailto:axios@1.14.1) published ~00:21 axios@0.30.4 (mailto:axios@0.30.4) published ~01:00 npm/security teams yanked both versions within a few hours (~03:15 UTC) Latest safe version re-pointed to 1.14.0 / 0.30.3 The malicious versions are already removed from the registry, but anyone who ran npm install or deployed during that ~3-hour window (especially in CI/CD) may have been exposed.What to do right now if you use axios (or might indirectly):Check your package.json and lockfile (package-lock.json / yarn.lock / pnpm-lock.yaml) for axios versions Pin to a known-safe version: "axios": "1.14.0" or "axios": "0.30.3" (remove ^ or ~) Delete node_modules + lockfile → run npm ci (or equivalent) to reinstall If you think you installed during the window: scan your machine, rotate any credentials/secrets that might have been on affected systems, and review for suspicious processes/network connections Consider adding --ignore-scripts in CI or using tools like Socket, StepSecurity, or similar for supply-chain monitoring going forward This is yet another reminder that maintainer account security (especially 2FA + not reusing passwords) and tight version pinning matter a lot in the npm ecosystem.Stay safe out there!

@TheAgentPlay @1Umairshaikh Vibe coding gets you started fast but shipping for paying customers requires solid error handling, performance tests and user feedback loops. As self employed developer I learned that the hard way on my first SaaS project. Execution depth is everything.

Vibe coding gives you a starting line. Shipping a real product that doesn’t break under real users is an entirely different sport. The gap most people ignore is execution depth: taste, edge cases, reliability, and iteration under pressure. Anyone can generate code. Few can ship something that actually survives contact with paying customers. That’s where the real alpha lives.

Vibe coding gave everyone a starting line. It didn't give everyone a finish line. Shipping a working MVP and shipping a working product are two completely different games.

@ForwardEditor I have seen the short. Am I allowed to guess?

You won't guess what this is a list of

@sandislonjsak Great question. Yes, i have the same issue. My plan is now to improve my workflow to gain more control, which means everything will be a ticket.

@AdrianDittmann @nikitabier Why do I have to click on the post to be able to see the translation?

あなたは私の人生のとても日本的な時期に出会った

@ForwardEditor to be fair, I didn't mean i have a scheduled task that says hello to claude ^^ I just have normal early tasks.

@_michael_esch OH that's next level!

I've adopted the practice of saying "hello" to Haiku early in order to start my Claude session timer Is this crazy or correct

@theo Yes, but what alt being a successful founder?

Technically speaking, being a founder is easier than getting a job

As a freelancer, sometimes the smartest move is knowing when to walk away from a project. You can already see it’ll turn into trouble, and the pay just isn’t worth the headache.

added a bulk download for the photoshooting feature. zip files in zip files.