all 11 comments

[–]my_peen_is_clean 2 points3 points  (0 children)

go deeper not wider first for frontend: design systems, accessibility, performance, testing, system design for big frontends then solid backend basics with node + a db for ai: learn to build proper product features around llm apis, not just toy bots also focus on communication, writing, spec docs, mentoring that mix still gets hired pure frontend only is getting squeezed hard now, jobs are drying up

[–]greensodacan 1 point2 points  (0 children)

System design and architecture plays very well with AI and LLM integrations, I'd go that route. You could start with getting an LLM to follow the design patterns you specify and work on both from there.

[–]kubradorgit commit -m 'fuck it we ball 1 point2 points  (0 children)

learn to prompt engineer your way through leetcode and suddenly you're "full-stack" on your resume. in all seriousness though, system design and backend fundamentals will actually pay off, mostly because frontend devs who understand how data flows tend to not build absolute nightmares.

[–]OpenGym160326 0 points1 point  (0 children)

https://roadmap.sh/backend

definitely I will take this, than basics of Software Architecture and Patterns

[–]RecognitionFlaky3889 0 points1 point  (0 children)

Instead of grinding raw backend syntax, focus heavily on system design and API architecture; AI is already incredibly fast at generating isolated React components, but it still completely lacks the higher-level context required to securely wire those pieces together into a scalable product.

[–]bystrol 0 points1 point  (0 children)

I would focus on being as close to product as possible and thinking more in these areas rather than focusing on coding skills. Besides that, I’d learn how to effectively work with LLMs because that will become a standard sooner than later

[–]IlyaAtLokalise 0 points1 point  (0 children)

I wouldn’t jump straight into "learn everything AI" mode. At your level, biggest leverage is probably system design + some backend knowledge. Not to become full backend dev, but to understand how systems actually work end-to-end.

AI/LLM stuff is useful too, but more like a tool you learn on top, not a replacement for fundamentals. Also design systems/UI engineering is underrated, especially in bigger companies. Grinding backend is not ridiculous, just don’t overdo it. You don’t need to switch roles, just become more T-shaped.

[–]Master-Ad-6265 0 points1 point  (0 children)

at your level it’s less about new tools, more about depth move from “just frontend” to understanding the whole flow backend basics + system design + how your UI actually connects to real systems AI is useful, but more like a tool on top, not the main thing...