are normally divided right into a separate frontend and backend. The frontend handles what the consumer sees, whereas the backend handles all the logic and processing. This can be a pure separation of issues that the majority platforms merely use as a result of it really works properly.
Nevertheless, once you make adjustments to your software, you usually have to make adjustments to each the frontend and the backend. That is the place full-stack engineers are available in: engineers who work with each the frontend and backend.
Working with each frontend and backend may be difficult, nonetheless, because of a number of causes:
- They’re usually written in numerous languages: frontend with TypeScript and the backend with Python
- You need to cope with permissions and auth, and cope with challenges like CORS errors
- They’re in numerous repositories and are deployed individually.
With the discharge of coding brokers, working with each frontend and backend code on the similar time has change into less complicated. On this article, I’ll offer you a high-level overview of how I work each day with each frontend and backend code, and ensure the 2 programs combine seamlessly.
Why work with each frontend and backend
The rationale you’re employed with each frontend and backend code on the similar time is just due to necessity. Let’s say you need to add a brand new function in your software, the place a consumer can retailer their AI chatbot conversations and entry them later.
This function merely requires adjustments in each the frontend and the backend. It’s worthwhile to replace the frontend to show the earlier conversations, and also you want the backend to deal with the storage and retrieval of conversations. Thus, you don’t have an choice to work with each the frontend and backend code.
Moreover, as an engineer, it’s normally more practical to work with each frontend and backend. Think about in the event you needed to implement the AI chatbot conversations function, and also you had been solely engaged on the frontend. You’d then must implement the frontend a part of the course, after which coordinate with one other backend engineer on how you can retailer the conversations. You’d must spend time discussing:
- The schema for storing conversations
- Which information needs to be included?
- What ought to the endpoint be known as
That is tremendous time-consuming. Should you’ve ever labored in a processional software program engineering setting, you understand how a lot time it takes.
As an alternative, in the event you do the work solo, you don’t must do any coordination and may transfer at a a lot larger velocity.
Methods to work successfully with frontend and backend code
On this part, I’ll cowl some strategies I exploit to work successfully with each frontend and backend code. With the discharge of a super-effective coding agent, this has change into a lot less complicated, and also you don’t have to have intensive expertise in each frontend and backend code to be efficient.
Use Workspaces
Workspaces are an extremely highly effective function when working in a number of repositories. You are able to do this with Cursor utilizing “Add workspace”, or with any CLI software by merely pointing the agent to the repositories you need to work with. Now the mannequin could have the context of each related repositories and thus be capable of implement a full-stack answer in a single go.
Workspaces are unbelievable. Earlier than I found it, I used to work with two separate Cursor tabs, one with the frontend code and one with the backend code. I’d then make one change within the frontend, and manually replace the backend to simply accept this new change.
No marvel it took ages for me to place out options. Now, I merely immediate my agent to replace the frontend in line with some directions, and it mechanically updates the backend with the corresponding code to simply accept the frontend adjustments. In fact, this works the opposite manner as properly.
Monorepos
Monorepos are additionally tremendous highly effective. The other of a monorepo is to have your entire code unfold into totally different repositories (normally known as microservices). In my expertise, this doesn’t work very properly, because it merely makes it more durable for you and your coding brokers to maintain monitor of the place every little thing is.
As an alternative, I extremely advocate shifting every little thing to a monorepo, the place you’ve got all of your code in a single codebase. Now you may simply create guidelines, reminiscent of pre-commit hooks, that apply to your entire code and don’t have to duplicate them throughout a number of repositories. Moreover, you may simply have AGENTS.md information masking and explaining the entire repository, so brokers simply maintain monitor of the place every little thing is.
If all of your code is in a monorepo, you’d additionally not want workspaces, as I described within the final part. Nevertheless, it’s fairly frequent to have a monorepo for the frontend/API code, after which a separate repository dealing with extra advanced processing, reminiscent of working brokers or doing doc processing. Thus, you’ll usually have to make use of workspaces anyway.
AGENTS.md as context
One other essential tip is to actively use and replace AGENTS.md. There are a lot of options to AGENTS.MD, reminiscent of CLAUDE.md, WARP.md, or .cursorrules. In my expertise, nonetheless, AGENTS.MD is learn by all coding brokers, irrespective of which one you utilize.
Thus I like to recommend utilizing AGENTS.md as a result of in the event you ever change an agent sooner or later, or your coworkers are utilizing totally different brokers, you may all profit equally.
You possibly can have an AGENTS.md file within the root of your repository that gives a high-level overview of the repository, type of like a README. This will clarify to the agent which folders comprise which logic, making it simpler for the agent to navigate the code.
Moreover, you may have AGENT.md in all subfolders as properly. For instance, if in case you have a service in a single folder, you might have an AGENTS.md file there explaining how the service works, or any quirks to pay attention to.
I additionally need to add that everytime you make adjustments to your code, make sure to replace AGENTS.md. You possibly can, for instance, immediate your coding agent to replace the related AGENTS.md information for you, given what it discovered in its final session, and it’ll mechanically add vital notes. Make sure you push these adjustments to GitHub as properly, in fact, so your colleagues can profit from the information you’ve gained.
Conclusion
On this article, I’ve mentioned how you can successfully work with each frontend and backend code. I began off by explaining why it’s vital to know how you can work with each frontend and backend, highlighting that it’s normally a more practical manner of getting stuff carried out. Moreover, I elaborated on some strategies I exploit to work successfully with frontend and backend, masking using Workspaces, monorepos, and AGENTS.md. I consider that sooner or later, we’ll all be full-stack engineers, contemplating how efficient coding brokers are. The work of a human engineer will merely be to coordinate all of your brokers in the best manner potential, as a way to remedy crucial issues, in the most effective and most effective method.
👉 My free eBook and Webinar:
🚀 10x Your Engineering with LLMs (Free 3-Day E-mail Course)
📚 Get my free Imaginative and prescient Language Fashions e book
💻 My webinar on Imaginative and prescient Language Fashions
👉 Discover me on socials:
💌 Substack
