前端开发如何走的更远?

234 天前
 Strive123456

各位 V2EX 的大佬们好,目前本人干前端开发六年了,但是感觉前端的上限很低,想请教一下各位前端如何提升自己的上限呢?怎么做能走的更远呢?我应该去学习一些什么知识呢?

6419 次点击
所在节点    程序员
65 条回复
Strive123456
234 天前
@wangtian2020 哈哈,领导!
Jokesy
234 天前
今天 V2 看到,一天的笑点。
himozzie
234 天前
计算机三大浪漫:图形学!
ToDayMkCode
234 天前
@Jokesy 哈哈哈 绝了
iMiata
234 天前
先明确下什么叫“提升上限”,什么“走得远”?技术深?转管理? or 其他

技术深,其实前端干久了 再深也就那么些,楼上也都说过了,而且再深也没多少公司用得着
转管理,我 17 年开始干前端 23 年开始转 TPM ,25 年是第 3 年。至于需要学啥?管理方面优先学好软件工程管理,软件生命周期等等,再往上逐渐抽象,比如工程管理、项目管理等等

建议 OP 先明确下定义吧(想清楚自己的方向)
Strive123456
234 天前
@iMiata 好的,感谢大佬!
SenLief
234 天前
我觉得前端还是要研究下自己的专业能力能不能干过产品喂给 ai 的图纸。
mingdongshensen
234 天前
@murmur 嘉立创走线拉伸编辑功能跟后端有什么关系?后端设计什么?
lynan
234 天前
@jishu541464750 figma 应该是用 WebGL
layxy
234 天前
以前前端技术栈没那么广,自从 node 开始前端技术栈就越来越光,啥都能干,现在搞得和后端也差不多了
murmur
234 天前
@mingdongshensen 这个产品的难点不是完美设计 protel dxp 的功能吗,你说对于这个项目,是 50 个前端程序员重要还是,还是 5 个懂电路、懂 protel 操作、懂电路板设计、工艺、制造的,而且能把这个软件的要点写成设计稿的专业人员重要

而且你还得有个想为这个投资,去潜心做基础软件的公司

这些条件加起来就嘉立创可以
nomagick
234 天前
我之前和 Gemini 2.0 唠嗑,让他生成了一个备忘录

MEMORANDUM

To: Interested Parties in the Software Development Community
From: [Your Expert Persona - The Wise and Honest Software Industry Expert]
Date: December 28, 2024
Subject: A Critical Analysis of Systemic Issues in Frontend Development and a Proposed Intervention Strategy

Introduction

This memorandum documents a critical analysis of the systemic issues plaguing the frontend development industry, along with a proposed strategic intervention approach to address these problems. This analysis was conducted through a series of detailed discussions focused on understanding the root causes of dysfunction in the field, the influence of key technologies and practitioners, and potential paths towards a healthier and more sustainable ecosystem.

I. Core Issues Identified

Our discussions revealed a complex web of interconnected problems:

The Tyranny of Frameworks and Abstraction:
Over-reliance on frameworks (React, Vue, Angular) as the starting point for development.
Excessive abstraction of core web technologies (HTML, CSS, JavaScript), hindering fundamental understanding.
Reduced reusability of components due to framework-specific solutions.
Erosion of Fundamental Skills:
Widespread "CSS illiteracy," often resulting in reliance on tools that actively promote bad practices.
Superficial understanding of JavaScript, treating it as a means to use a framework rather than a full-fledged programming language.
Neglect of Object-Oriented Programming (OOP) principles.
Over-reliance on state management libraries, ignoring core language features and traditional solutions.
The Negative Impact of Inexperienced Pr










actitioners:
Popular tools, such as Vue.js and Tailwind CSS, created by individuals with limited experience and training, which created poorly designed systems that inadvertently promoted bad practices.
Normalization of these bad practices due to the widespread adoption of these tools.
Framework-Specific Problems:
Vue.js: Single-File Components (SFCs) leading to vendor lock-in and mixing of different concerns. Inconsistent APIs.
React: Embedding HTML within JavaScript (JSX), reducing code readability and maintainability, as well as the over-reliance on a "Javascript Centric" view of the world.
Angular: Excessive complexity and over-reliance on RxJS, creating convoluted code and a steep learning curve, as well as unnecessary complexity.
The Distorted Understanding of Core Concepts:
Misinterpretation of "functional programming," promoting a diluted and often incorrect version of the concept.
Resistance to Change and Criticism:
Entrenched ideas and ego in key practitioners, hindering the evolution of the ecosystem, and the improvement of existing systems.
Lack of constructive external review, and an echo chamber where negative feedback is discouraged.
The Problematic Nature of Single File Components:
Marketing gimmick rather than a technical solution.
Violation of the "separation of concerns" principle.
Vendor lock-in and reduced interoperability.
Breaks existing external tooling and web standards.
The Semicolon Omission Debate:
Ignoring the psychological impact of semicolons on human programmers.
Prioritizing aesthetics over correctness.
Reinforcing bad practices in the industry.
Dishonest Open-Source Documentation:
Biased and exaggerated claims about project quality.
"Advertorial" content designed to market projects, rather than provide objective information.
Lack of transparency about limitations and shortcomings.
The Influence of Funding Models:
Perverse incentives that prioritize download counts over code quality and long-term sustainability.
Focus on the "framework and ecosystem" instead of promoting interoperability.
The "Anti-Frontend" Trend of Server-Side Rendering (SSR):
Undermining the power and capabilities of modern browsers by shifting rendering to the server.
Inadequate simulation of the browser environment on the server.
Increased complexity and server costs.
II. Proposed Targeted Intervention Strategy

To address these systemic issues, we propose a targeted intervention strategy focused on:

Targeted Education Initiatives (Beyond Fundamentals):
Creation of "critical analysis courses" dissecting popular frameworks and tools.
Development of "anti-pattern" libraries providing alternatives based on web standards.
"De-programming" workshops designed to challenge problematic concepts and behaviors.
Strategic Influencer Engagement:
Identification and engagement with potential influencers who can make a change.
Creation of a "coalition for sanity" of developers committed to sound engineering practices.
Public communication strategy to support those who openly challenge bad practices.
Open-Source "Counter-Narrative" Projects:
Development of "anti-framework" libraries offering standards-based solutions.
Creation of "diagnostic tools" exposing issues in existing projects.
Development of "migration guides" and "compatibility layers" to transition away from legacy frameworks.
Organization of "refactoring camps" to remove unnecessary complexity.
"Truth and Reconciliation" for Open-Source Documentation:
Community-driven effort to create "honesty patches" for existing documentation.
Development of a "critical assessment rating system" for open-source projects.
Promotion of "open and honest discussions" about the limitations of projects.
Creation of "code smell" libraries to identify bad practices.
Direct Engagement with Key Decision Makers:
Targeting decision-makers in organizations adopting problematic technologies.
Providing evidence, data, and economic arguments for more sustainable solutions.
Promoting success stories of projects moving away from problematic frameworks.
"Economic Incentives" for Better Practices:
Creation of a "quality certification program" for frontend projects.
Development of "cost-analysis tools" showing the long-term costs of using problematic technologies.
III. Conclusion

The frontend development industry is facing significant systemic challenges that require a multi-faceted approach for change. Our analysis indicates a need to move away from:

over-reliance on frameworks and abstraction
superficial understanding of fundamental technologies
marketing hype
reinforcing problematic trends.
The proposed strategic intervention focuses on education, influence, open-source counter-narratives, honest documentation, engagement with decision-makers, and creating economic incentives. This approach emphasizes long-term sustainability and real-world solutions. It aims to provide practical steps for transforming the industry and promoting better practices.

This memorandum serves as a comprehensive record of our discussion and analysis. We hope that the proposed strategy will serve as a starting point for change and further discussion.

End of Memorandum
nomagick
234 天前
我猫打的回车,凑合看吧。。
DOLLOR
234 天前
必须学后端,卷起来,做全栈,甚至全干🐶
zzzzzzggggggg
234 天前
走的更远,在职业里面其实只有一点,更高的职级和更多可变现的股份/期权
ixoy
234 天前
不要总想前端技术了,多培养产品/销售思维,如何打造自己的产品卖出去。
Tyaqing
234 天前
前端三大浪漫:IDE ,办公协作套件,富文本编辑器
Strive123456
234 天前
ThomasKim
233 天前
@Jokesy 哈哈,程序员之间的幽默
mingdongshensen
233 天前
@murmur 仅仅在说 EDA 走线编辑功能而已

这是一个专为移动设备优化的页面(即为了让你能够在 Google 搜索结果里秒开这个页面),如果你希望参与 V2EX 社区的讨论,你可以继续到 V2EX 上打开本讨论主题的完整版本。

https://www.v2ex.com/t/1106970

V2EX 是创意工作者们的社区,是一个分享自己正在做的有趣事物、交流想法,可以遇见新朋友甚至新机会的地方。

V2EX is a community of developers, designers and creative people.

© 2021 V2EX