AI Usage December 2024 @vercel v0 for front end @cursor_ai | Prithvir on Binance Square

Trending Articles

Bookmarked and Liked

--

AI Usage December 2024
@vercel v0 for front end
@cursor_ai for back end
@grok for brainrot translation
@ChatGPTapp for hard math and research
@perplexity_ai for search
@MSFTCopilot for nothing

Disclaimer: Includes third-party opinions. No financial advice. May include sponsored content. See T&Cs.

2k

0

Replies 0

Explore the latest crypto news

⚡️ Be a part of the latests discussions in crypto

💬 Interact with your favorite creators

👍 Enjoy content that interests you

Email / Phone number

Relevant Creator

@Square-Creator-8d6e2a457836

Explore More From Creator

Deciding which blockchain to deploy on first

--

o1 is at least 10x better than 4o at writing code, but I can’t tell if it’s taking too long to load or if my attention span is cooked.

--

I wouldn’t sleep on FOCGs just yet. The Atari 2600 was garbage compared to arcade machines. But it landed in living rooms and flipped the script on monetization. Mobile games did the same thing. They were underpowered next to desktop games, but they forged new bonds b/w devs and players. That was a game-changer, even with tiny screens. Now there are Fully Onchain Games (FOCGs). They’re clunky and not as slick as regular games. But they open doors to fresh capital and economic experiments we haven’t fully explored yet. If history teaches us anything, it’s that the platform with worse specs can still upend the market by changing the rules.

--

10 Lessons from Prompt Engineering Our apps have scaled to tens of thousands of users, tracking billions of dollars of onchain assets. Here are my lessons on using prompt engineering: 👇🏻 1. Don’t ask AI to build a whole application. Break the request into smaller chunks. - Start with a single component. - Don't ask it to generate a page. Request a subsection of a page. - Don’t ask it to develop an entire feature. First, have it create a sub-feature. 2. Provide clear guidelines on theme and style. - Include screenshots and working code. - Use examples. Show what a good output looks like. - The more specific, the better. 3. Specify the format you want (e.g., Markdown, JSON, TypeScript, etc.). 4. Set constraints. - Word limit - Performance requirements - Design principles 5. Iterate. Give feedback and refine until it’s right. Context windows are limited, but short-term memory is no longer an issue. 6. Leverage system messages. Define roles (e.g., “You are an expert UI designer”). 7. Ask for step-by-step reasoning. This improves accuracy. In 2025, the prompt engineering skillset variance will increase exponentially. The variance in software engineering will further increase as well. What are some techniques that have helped you guys improve your prompts? @crypto_linn220, @cryptogideon_125, @cryptomanran544, @dynamo_patrick230, @hmalviya9193, @jake_pahor137, @krybharat469, @milesdeutscher428, @rektdiomedes236, @saushank_123, @the_smart_ape123, @thedefiplug106

--

No I don't Remix, Hardhat, or Foundry. I just write in Solidity in Notepad and copy-paste into the terminal.

--

Latest News

Ethereum(ETH) Drops Below 3,300 USDT with a 2.23% Decrease in 24 Hours

--

BNB Drops Below 700 USDT with a 2.59% Decrease in 24 Hours

--

Circle's USDC Circulation Increases By $1.1 Billion In A Week

--

Bitcoin(BTC) Drops Below 103,000 USDT with a Narrowed 1.71% Increase in 24 Hours

--

Bitcoin And Ethereum Prices Decline

--

Trending Articles

$PNUT Short Liquidation Analysis Liquidation Amount: $15,8

🚨 *Why 75% of Traders Face Losses: The Math Behind It* 🚨

🚨 Shiba Inu (SHIB) Outflows Soar 883%: What’s Behind This Massive Move?

ADA LIMITED OPPORTUNITY ALERT ⚠️ YOU'RE TRULY LUCKY 🎉 Cong

Cookie Preferences

Cookie Preferences