Suprateek

[Suprateek @TiresomeFanatic]

@thedeserterJJ @ns123abc Every harness you use, does that. These guys just got caught.

[Suprateek @TiresomeFanatic]

@0xmrtn @cjzafir Because context bloat is a thing. A better place to have your "context cached" is an md file you always have control over your context in that way.

A fresh chat is 99 times better then continuing everything in the same one.

[Vox @Voxyz_ai]

one more tip: review completed work in a 𝗳𝗿𝗲𝘀𝗵 𝗖𝗼𝗱𝗲𝘅 𝘀𝗲𝘀𝘀𝗶𝗼𝗻.

It didn't take part in the implementation, so it doesn't carry the original session's 𝗿𝗲𝗮𝘀𝗼𝗻𝗶𝗻𝗴 𝗶𝗻𝗲𝗿𝘁𝗶𝗮.

Before closing the original session, have it create review-brief.md in the repo root.

The brief contains only:

→ your original request, verbatim
→ requirements or scope changes you approved later
→ the diff or commit range to review

Leave out the 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝘀𝘂𝗺𝗺𝗮𝗿𝘆.

In the fresh session, send:

Read review-brief.md. Use the repo, docs, diff, and tests as evidence. Mark every requirement complete, partial, or missing. Look for requirements that never made it into the implementation. Fix confirmed issues, rerun the tests, then delete review-brief.md.

I take the lazy route: handoff writes the context file. A fresh session reads it, then runs ce-code-review.

both skills below 👇

[Pratham @Prathkum]

New way to hire developers in the AI world:

1. Skip the "are you proficient in TS?" questions. Spend 2-3 minutes on their genuine interest in AI's future.

2. Give them a broken piece of code and an AI tool. If they can’t use the AI to diagnose and fix the root cause in 10 minutes, they’re behind the curve.

3. Reverse-engineer their logic. Don’t just look at the output. Ask: "What instructions did you give the AI to get here, and why did you iterate on them?"

4. They should be able to explain the "why" behind every design choice. Technical depth matters more now, not less.

5. Use the interview to see if they can use AI to map out a system, rather than just writing individual functions.

[Suprateek @TiresomeFanatic]

@aadeetyeah @GruhamBot @twitrbnb @flatshareblr @Flashmateshq @FlatsnFlatmates Hey I’m looking for a flatmate too in the same area. Are you interested in looking for 2bhks that we can share?

[Suprateek @TiresomeFanatic]

Project based learning is your friend. Forget learning the concepts first. Go straight to building something, when you get stuck somewhere, then learn that part, rinse repeat.
Choosing a project to build is much more intresting and fun than choosing what to learn. And the end of it, you’ve learned a lot and have something to show for it

[Suprateek @TiresomeFanatic]

@wojakcodes How can I find these clients. Any pointers? I’m a RN dev

[Suprateek @TiresomeFanatic]

@sidborderwala Iteration 6 looks much better. The final one just looks off. Also looks like you’re not following design principles. Because both the font and symbol have unequal inner padding/margin vertically it just looks off. Choose either the font or the symbols having both looks not good

[Suprateek @TiresomeFanatic]

@AryanTrivedi_7 Interested

[Suprateek @TiresomeFanatic]

@Klaviyodeepdive UP

[Suprateek @TiresomeFanatic]

@shashwatsinggh @BangaloreRoomi Hi, interested but unable to DM. Please DM me

[Suprateek @TiresomeFanatic]

@peakbengaluru @sidvro Around cubbon park, mg road, Shivaji Nagar

[Suprateek @TiresomeFanatic]

@RalphyRiches00 TECH

[Suprateek @TiresomeFanatic]

@appfr3d @LeonDvlpmnt @expo CNG? Can you please link to some documentation? Would be helpful

[Suprateek @TiresomeFanatic]

@maharshii https://t.co/kI9vlgkQ3Z

In the context of vastness of space it is indeed a result of a small pure chance

[Suprateek @TiresomeFanatic]

@rajiv_17_ FREE

[Suprateek @TiresomeFanatic]

@piracy4life GOLF

[Suprateek @TiresomeFanatic]

@harshitagu72595 youtube

[Suprateek @TiresomeFanatic]

@RalphyRiches00 ROBLOX

[Suprateek @TiresomeFanatic]

@RalphyRiches00 ROBLOX