Transform Figma Files to Production Ready Code. Build web and mobile apps in days, not months.

San Francisco
Joined December 2023
Include

Only show posts containing:

Exclude

Hide posts containing:

Time range
-
Minimum likes
CodeParrot (YC W23) retweeted
🚀 Excited to share our latest episode of the Ignite podcast! Join us as we chat with @royaljain4, co-founder and CEO of @codeparrotAI, about his inspiring journey from IIT Bombay to leading a groundbreaking AI-driven startup. 🌟
1
2
3
547
How to improve #LLMs using RLHF? Just ask humans to rate the output. Find out how does it work #GenAI
1
1
637
CodeParrot (YC W23) retweeted
paulthadev
@paulthadev28 Jun 2024
Time to test out @codeparrotAI on a project.
1
1
305
Yes, cursor support is coming soon! Currently on vscode only. @vedantsopinions
1
1
22
CodeParrot (YC W23) retweeted
Just had a talk with @royaljain4 , Founder of @codeparrotAI . I think this tool is actually gonna change my way of working. Figma -> React+Tailwind -> yes 🫶🎉
1
2
3
879
Do Large Language Models like @codeparrotAI or @github 's Copilot really understand your code? Short Answer, No. But then how do they seem to know what you want?
1
1
2
2
600
Thank You For the mention @NayakSatya_SG !
Are you a startup struggling with UI/UX for production ? Meet @codeparrotAI an AI powered tool that transforms Figma files to production ready code. #buildinpublic @figma #IndieDevs
1
2
339
That's a good idea! Putting it on the roadmap. Hoping our CTO doesn't pull out his hairs by tonight, given the feature requests we are getting 😀
1
1
52
Try it out once? Let us know what you need
76
We are live on @ycombinator ! Months of hard work and struggle behind this. Would love to get your honest feedback.
YC W23's @codeparrotAI converts Figma designs and screenshots into production-ready code, so developers can build stunning UI lightning fast. Share your Figma files and set your code preferences, and CodeParrot will have your screens ready in minutes. ycombinator.com/launches/L5M…
3
2
10
1,433
Replying to @reedddtm
Hey, Sorry for the late response. Think your DM is closed, can you DM us or write at [email protected] to help us debug
15
👉So, the next time you find yourself debugging a piece of JavaScript, remember the tale of the == operator. It's a quirky story, but one that encapsulates the essence of navigating the eccentricities of programming languages.
1
2
238
🌟Manual Comparison A more reliable approach involves manually comparing the length and each element of the arrays. (Check Slide 3 for the code)
1
3
320
🌟 One quick but not always recommended method is to compare the JSON string representations of the arrays.
1
2
18
👉Since their references are not the same, the comparison returns false. 👉 So, How to Correctly Compare Arrays ? Since direct comparison using === doesn't work as expected for arrays, you might wonder how to check if two arrays contain the same elements in the same order.
1
2
18
👉When you compare [1,2] === [1,2], you are comparing two separate arrays that happen to contain the same values. Despite the identical contents, these arrays are distinct objects stored in different locations in memory.
1
2
16
👉However, when it comes to comparing objects (and arrays are a type of object in JavaScript), the === operator compares their references, not their contents. In other words, === checks to see if both operands point to the same object in memory.
1
2
18
👉The === operator in JavaScript is known as the "strict equality" operator. It checks for both value and type equality.
2
2
16