Jon Haider

BESS, gigafactory, and datacenter EPC design management.
Ex. Tesla | Northvolt | McKinsey | Redwood Materials

[Jon Haider @jonrhaider]

@DaveShapi I think he’s very wrong with regards to projects and unexpected occurrences requiring human oversight. 1- knowledge representation/ reasoning and cognitive architectures are being developed to address this exact problem. 2- what’s true today isn’t necessarily true tomorrow.

[Jon Haider @jonrhaider]

@theodorebeers The raw "Bahr Al-Raml" feels rhythmically awkward to me, but the word play and meaning here are very well crafted.
Thanks for sharing. Following for more.

[Jon Haider @jonrhaider]

@SteveParis1 @elonmusk We need policy makers to act, to regulate, to safeguard. We do not need them to stall domestic AI research in order to hide their failure to act thus far.

[Jon Haider @jonrhaider]

@Ivybest666 An odd number of nodes (3) have an odd number of edges connecting to them (1 or 3) => impossible. If there was an even number of nodes that have odd number of edges, it would be solvable. Test it.

[Jon Haider @jonrhaider]

@femiitan The illusion of choice

[Jon Haider @jonrhaider]

@DaveShapi I’ve always thought of narcissism as the inability or unwillingness to process or confront one’s shame / guilt / fault due to an insecurity of being seen as inadequate. So I think it’s really rooted in both.

[Jon Haider @jonrhaider]

@MarioNawfal Bro, I can’t even get olive oil through that airport security, what was he thinking?

[Jon Haider @jonrhaider]

@MatthewBerman Just curious, what features or functionality do you have in the Acrobat alternative you built that you wouldn’t get with like an InkLayer or EmbedPDF (both open source JS pdf editor tools)?

[Jon Haider @jonrhaider]

@DaveShapi If the argument were more geared towards “these are the dangers”, I’d listen, but “what about my job” is not good enough.

[Jon Haider @jonrhaider]

@yasalebanon Mafias

[Jon Haider @jonrhaider]

@EthanDriskill Where can I make a down payment, take my money

[Jon Haider @jonrhaider]

@anah_sahh Domain expertise and a clear picture of the problem statement. That and good UI taste

[Jon Haider @jonrhaider]

@alpaysh A nutshell

[Prajwal Tomar @PrajwalTomar_]

Vibe coders are getting sued.

People are shipping apps with real users and skipping the boring stuff that kills them.

A 20+ year dev shared the pre-launch checklist every AI builder needs.

I added what I learned after shipping 60+ apps at the agency.

Don't skip this:

1. Protect yourself, not just your app. The moment you collect user data you're in legal territory (GDPR, CCPA). Have a privacy policy. Know where user data lives.

2. Row Level Security. Without RLS, anyone can open DevTools and read your entire database. Supabase → Auth → Policies. Zero policies means your app is naked. 5 min to fix.

3. Test the failure path, not just the happy path. Wrong password 5x. Reset for an email that doesn't exist. Verification link clicked twice. Signup with an existing email. Catches 80% of auth bugs.

4. Security baseline in 2 min. Prompt your AI: "Review my app as a security specialist and make sure I have strong security headers and a solid baseline security posture."

5. OWASP. Prompt: "Review my app against OWASP standards and highlight vulnerabilities." This is where SQL injection, XSS and auth bugs actually get caught.

6. Client-side validation is UX, not security. Attackers disable JS and hit your API directly. Validate again on the server. Every time.

7. AI code leaks data in 3 spots: .env values in the frontend, API responses returning too much, secrets in logs. Prompt: "Check my app for credential or sensitive data leaks in frontend or API routes."

8. API keys in the frontend means game over. If it's in the browser, assume it's already taken. Move it server-side or proxy it.

9. Rate limits before someone burns your API bill. Cap every endpoint hitting a paid API. I've watched a Supabase bill jump from $20 to $200 in a day.

10. CAPTCHA on public forms (Cloudflare Turnstile is free) plus CORS locked to your domain. 10 min, kills bot floods.

11. Error messages that don't leak. "User not found", not "SELECT * FROM users failed". Log full errors server-side, show users generic messages.

Build fast. Just don't ship naked.

(full breakdown in my article below)

[Jon Haider @jonrhaider]

@ramonpriet_o @DaveShapi That would be great, but what makes you say this? Any trends or white papers you’re seeing that would lead to this conclusion?

[Jon Haider @jonrhaider]

@huskirl He’s the first person on AI’s eventual hit list

[Jon Haider @jonrhaider]

@svpino Isn’t there still a ratio limit to how many agents a single SWE can manage at once?

[Jon Haider @jonrhaider]

@DaveShapi Most of my app feature ideas, I start by voice dumping to ChatGPT for that parroting back that you mention. Then after my brain dump, I have it structured into a spec I use as instruction to my coding agent.

[Jon Haider @jonrhaider]

@Ric_RTP (2/2) Maybe it's more profitable to sell tokens to the 99% who will fail to build profitable operating systems and harnesses than it is to exchange tokens to everyone for 30 equity in the 1% who will succeed in creating that $1B value.

[Jon Haider @jonrhaider]

@Ric_RTP LLM models don't make you $1B, the proprietary agentic patterns / harness that companies build is what makes it. Every enterprise has to build their own OS / harness, and not all will know how. (1/2)