Rae

Prompt engineering is the future imo, because I’ve noticed that no one really cares who writes the code—as long as it works. It makes me a bit sad, because I genuinely enjoy coding.

On the weekends, I'm thinking I should build some tools or packages apart from my side projects—something that can be built easily. For example, I'm planning to build an npm package for React toast this weekend. It's a good start.

Rae

@raebuilds

18.04.

Day 4 of code till I get cancer - Made 1 PRs (opensource contribution) - Worked on project - Worked on soft skills

Rae

@raebuilds

18.04.

Day 3 of code till I get cancer - Solved 2 leetcode on trees - Worked on side prodect (worked for 5 hours straight) - Made 0 PRs (working on one) - Worked on soft skills

Rae

@raebuilds

18.04.

Hello developers, I'm currently working on an npm package that will act as a wrapper for your React app and help you build a better UI. It will read the DOM of your app and, with the help of LLMs, recommend changes and highlight errors. What do you all think about this idea?

Rae

@raebuilds

18.04.

I like to keep my backend separate, which is why I use either Node or Bun for the backend. I use Next.js only for the frontend because it makes frontend development so much easier (it’s good for backend too, but I personally don't prefer it). Am I missing out on something?

Rae

@raebuilds

18.04.

do you guys use nextjs for backend?

Rae

@raebuilds

17.04.

Day 2 of code till I get cancer - Solved 1 leetcode on trees - Worked on side prodect (worked for 5 hours straight) - Made 1 PR (Open source) - Worked on soft skills (talked to a German and an Argentinian guy)

Rae

@raebuilds

17.04.

I'm thinking on weekends I should build something beside my sideprojects and other stuffs. I have a lot of ideas, mostly related to npm packages. This weekend I will try to make a toast component.