A void

My first VS code extension css-color-collector collect all color from a css file and assign into css variables Please have a look and provide feedback. marketplace.visualstudio.com/items?itemName… @code

Aapka handle bahut khojna pada . Koi badhia easy handle rakhiye 😄

Porter helped in the crisis. Thank you! @porterit_ The best thing is that it is such a simplified and fast login process. It's the essence of this field.

हर शहर की एक तासीर होती है । कोई शहर आपको जाते ही अच्छा लगने लगता है कोई शहर बहुत दिन बाद अच्छा लगता है कोई हमेशा ही problematic सा होता है हर शहर का अलग मिजाज है हैदराबाद अलग नवाब है बैंगलोर बदमिजाज है जयपुर जान है पुणे प्यारा है अहमदाबाद अपना है चंडीगढ़ चमत्कार है

11:11

bro was right. Atlassian down 75%. HubSpot down 69%. Figma down 86%. Almost all of them down 30–70% from their 52-week highs. AI is literally eating software alive and repricing every company in real time. SaaS is cooked fr 😭

Bengaluru JPMC campus is more beautiful than Hyderabad campus

Sala Hyderabad flight se aaya ki isme ticket confirmation hoega because of my attendance but is baar ticket hi nahin aaya I miss #githubConstilation become

11:11

"Just use Vercel." "Just use Supabase." "Just use Clerk." Cool. Now your auth, database, and deployment are owned by 3 different companies who can change pricing whenever they want. And the rest of your product is wrapping OpenAI. At some point you have to ask yourself: what do I actually own here?

@hellonehha @tapasadhikary how can we check/verify weather code has a memory leaks ? just react code ( angular , we have to unsubscribe all observables) , clear timeout intervals, what else?

@tapasadhikary memory leaks, perf, Edge cases miss out.

What are the top 3 items in your code review checklist?

Bengaluru cab driver keeps talking over phone while driving, it seems like a culture 😄

@atmoio I like the way you express things but sadly can't see all as you have a pay wall on YouTube

Claude Mythos is Delusional

The mystery of Satoshi Nakamoto, the pseudonymous inventor of Bitcoin, has remained unsolved for 17 years. Not anymore. Read my 18-month investigation to find out who Satoshi really is. nytimes.com/2026/04/08/bus…

Our CEO just posted a video. 1.4 million views. He said we grew too fast. He said we fell short of our own standard. Our standard was keyboard mash. Seven days ago, he said we did not fabricate compliance evidence. Today, he deeply apologizes for the inconveniences caused. The inconveniences were 493 identical audit reports certifying that unrelated companies had identical security. The inconvenience was that someone noticed. He said we take these allegations seriously. We do. We hired a cybersecurity forensics team. Their first public statement was about the whistleblower. Not the audits. They are examining the person who examined our audits. We investigated the person who read it. He was caught on tape asking if the auditor actually looks at the platform. The answer was no. That was the product working correctly. He said the evidence points to a targeted cyberattack from a malicious actor, not a whistleblower. The malicious act was purchasing our product. The cyberattack was using it. The exfiltration was downloading their own audit report. The attacker purchased Delve under false pretenses. That is the first accurate thing in the statement. Every purchase of Delve was under false pretenses. The pretense was that compliance was being performed. We agree completely with this characterization. Where we differ is the direction. He said the posts rely on fabricated claims. The claims were screenshots of our own software. He said cherry-picked screenshots. You do not need to cherry-pick when the orchard is one tree. He said stolen data taken out of context. The context is 493 other identical reports. He said he could not share his side of the story until now, due to ongoing cybersecurity and forensics investigations. We needed three weeks and a crisis communications firm to draft a response to our own reports. The apology took longer to write than the audits. He said we fell short of our own standard. We grew too fast. "We grew too fast" is the startup version of "mistakes were made." It means: the velocity of the fraud exceeded our capacity to conceal it. That is a scaling problem. We are a scaling company. He announced changes. A new auditor network. The previous auditor's license number was pre-filled in the template before the audit began. We are replacing them with auditors who will also receive pre-filled templates. That is the change. Free re-audits for all customers. We offered the same thing last week. The re-audit will be conducted on the same platform that produced the original audit. With the same automation. By a different firm that will not look at it. We fixed the typo. The re-audit will not contain "sdf, g, dlkjf." It will contain different test data that will also not be reviewed. That is enhanced transparency. He said this was a coordinated smear campaign. One person with a Substack. That is the coordination. The smear was publishing our work product. The campaign lasted five posts. He said Delve was built to modernize compliance. Correct. We modernized it from a twelve-month process into a five-day template. The modernization worked. The compliance was modern. Modern means fast. Fast means nobody looks. Nobody looking is the product. He said we are not going anywhere. He is right. The PDF does not expire. The certifications are still active. LiteLLM was breached behind our certification. Mercor confirmed a related security incident behind our certification. The certifications are still valid because nobody revoked them because nobody reads them because that is the product. He said he is committed to building what is next. The video had two founders, one couch, and one prepared statement. It was filmed in what appears to be a living room. The lighting was professional. The apology was not. 1.4 million people watched the CEO of a compliance company respond to evidence of fabricated audits by calling the evidence a cyberattack. Buying the product is not an attack. Using it is not espionage. Describing it is not a smear. But we have hired forensics experts to prove otherwise. The record was 493 identical records. He set it straight. Nobody will ask how.

@heyblake RZRO.link

Drop your project URL Let’s drive some traffic

Jitni Hiring nahin ussay jyada hiring aur interview questions articles/blog / vlog/repo/course banaye ja rahe hain

Honestly, this is the most accurate diagram I've seen. Waterfall: You plan for 18 months and deliver exactly what nobody needs anymore. Agile: You deliver something usable at every step, but the CEO keeps asking, "Where's the car?" AI: You get the car on day one. It has six wheels, the doors are on backwards, and it has a rocket launcher. You spend more time making it yours than actually "building"; it's shaping. owning. verifying. That's what the best AI developers do now. They don't build. They shape and own.

insert <Munh se supari thook k bat kar re baba> meme

@mvkaran Sir, when do we receive confirmation mail for the #GithubConstellation event , on 11th April ?

🧨 Axios only needed to be resolved somewhere in your dependency graph to affect you. Semver + transitive deps + runtime installs = hidden blast radius. If you only checked your project’s lockfile, you may still not know. socket.dev/blog/hidden-bl… #nodejs