are often divided right into a separate frontend and backend. The frontend handles what the consumer sees, whereas the backend handles the entire logic and processing. It is a pure separation of issues that the majority platforms merely use as a result of it really works effectively.
Nevertheless, whenever you make modifications to your utility, you typically must make modifications 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 typically written in numerous languages: frontend with TypeScript and the backend with Python
- It’s important to take care of permissions and auth, and take care of 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 identical time has grow to be less complicated. On this article, I’ll offer you a high-level overview of how I work every day with each frontend and backend code, and ensure the 2 techniques combine seamlessly.
Why work with each frontend and backend
The explanation you’re employed with each frontend and backend code on the identical time is just due to necessity. Let’s say you need to add a brand new characteristic in your utility, the place a consumer can retailer their AI chatbot conversations and entry them later.
This characteristic merely requires modifications in each the frontend and the backend. It’s essential 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 often more practical to work with each frontend and backend. Think about if you happen to needed to implement the AI chatbot conversations characteristic, and also you had been solely engaged on the frontend. You’d then need to implement the frontend a part of the course, after which coordinate with one other backend engineer on the way to retailer the conversations. You’d need to spend time discussing:
- The schema for storing conversations
- Which information must be included?
- What ought to the endpoint be known as
That is tremendous time-consuming. When you’ve ever labored in a processional software program engineering setting, you know the way a lot time it takes.
As a substitute, if you happen to do the work solo, you don’t need to do any coordination and may transfer at a a lot better pace.
Methods to work successfully with frontend and backend code
On this part, I’ll cowl some methods I take advantage of to work successfully with each frontend and backend code. With the discharge of a super-effective coding agent, this has grow to be a lot less complicated, and also you don’t must have in depth expertise in each frontend and backend code to be efficient.
Use Workspaces
Workspaces are an extremely highly effective characteristic when working in a number of repositories. You are able to do this with Cursor utilizing “Add workspace”, or with any CLI instrument by merely pointing the agent to the repositories you need to work with. Now the mannequin can have the context of each related repositories and thus be capable to 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 keeping with some directions, and it robotically updates the backend with the corresponding code to simply accept the frontend modifications. In fact, this works the opposite means as effectively.
Monorepos
Monorepos are additionally tremendous highly effective. The other of a monorepo is to have all your code unfold into totally different repositories (often known as microservices). In my expertise, this doesn’t work very effectively, because it merely makes it more durable for you and your coding brokers to maintain observe of the place all the pieces is.
As a substitute, I extremely suggest shifting all the pieces to a monorepo, the place you’ve got all of your code in a single codebase. Now you’ll be able to simply create guidelines, comparable to pre-commit hooks, that apply to all your code and would not have to duplicate them throughout a number of repositories. Moreover, you’ll be able to simply have AGENTS.md recordsdata protecting and explaining the entire repository, so brokers simply maintain observe of the place all the pieces 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 widespread to have a monorepo for the frontend/API code, after which a separate repository dealing with extra advanced processing, comparable to operating brokers or doing doc processing. Thus, you’ll typically 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 various alternate options to AGENTS.MD, comparable to CLAUDE.md, WARP.md, or .cursorrules. In my expertise, nonetheless, AGENTS.MD is learn by all coding brokers, regardless of which one you utilize.
Thus I like to recommend utilizing AGENTS.md as a result of if you happen to ever change an agent sooner or later, or your coworkers are utilizing totally different brokers, you’ll be able to all profit equally.
You’ll be able to have an AGENTS.md file within the root of your repository that gives a high-level overview of the repository, form of like a README. This may clarify to the agent which folders comprise which logic, making it simpler for the agent to navigate the code.
Moreover, you’ll be able to have AGENT.md in all subfolders as effectively. For instance, if in case you have a service in a single folder, you may 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 modifications to your code, remember to replace AGENTS.md. You’ll be able to, for instance, immediate your coding agent to replace the related AGENTS.md recordsdata for you, given what it discovered in its final session, and it’ll robotically add essential notes. Remember to push these modifications to GitHub as effectively, after all, so your colleagues can profit from the data you’ve gained.
Conclusion
On this article, I’ve mentioned the way to successfully work with each frontend and backend code. I began off by explaining why it’s essential to know the way to work with each frontend and backend, highlighting that it’s often a more practical means of getting stuff carried out. Moreover, I elaborated on some methods I take advantage of to work successfully with frontend and backend, protecting the usage of Workspaces, monorepos, and AGENTS.md. I imagine 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 means attainable, to be able to resolve a very powerful issues, in the perfect and best method.
👉 My free eBook and Webinar:
🚀 10x Your Engineering with LLMs (Free 3-Day Electronic mail Course)
📚 Get my free Imaginative and prescient Language Fashions book
💻 My webinar on Imaginative and prescient Language Fashions
👉 Discover me on socials:
💌 Substack
🐦 X / Twitter
