Programmer Competency Matrix

程序员应用动手能力评测-Programmer Competency Matrix 今天的收获还是挺大的,首先看下Programmer Competency Matrix,我之所以说是 程序员应用动手能力评测 ,是因为此评测完全是面向企业工作的程序员的(技术),而非计算机科学的研究人员。我自己评测了一下,现将评测结果记录下来。 阅读详情

http://www.indiangeek.net/programmer-competency-matrix/

 

 

Computer Science
 2n (Level 0)n2 (Level 1)n (Level 2)log(n) (Level 3)Comments
data structuresDoesn’t know the difference between Array and LinkedListAble to explain and use Arrays, LinkedLists, Dictionaries etc in practical programming tasksKnows space and time tradeoffs of the basic data structures, Arrays vs LinkedLists, Able to explain how hashtables can be implemented and can handle collisions, Priority queues and ways to implement them etc.Knowledge of advanced data structures like B-trees, binomial and fibonacci heaps, AVL/Red Black trees, Splay Trees, Skip Lists, tries etc. 
algorithmsUnable to find the average of numbers in an array (It’s hard to believe but I’ve interviewed such candidates)Basic sorting, searching and data structure traversal and retrieval algorithmsTree, Graph, simple greedy and divide and conquer algorithms, is able to understand the relevance of the levels of this matrix.Able to recognize and code dynamic programming solutions, good knowledge of graph algorithms, good knowledge of numerical computation algorithms, able to identify NP problems etc.Working with someone who has a good topcoder ranking would be an unbelievable piece of luck!
systems programmingDoesn’t know what a compiler, linker or interpreter isBasic understanding of compilers, linker and interpreters. Understands what assembly code is and how things work at the hardware level. Some knowledge of virtual memory and paging.Understands kernel mode vs. user mode, multi-threading, synchronization primitives and how they’re implemented, able to read assembly code. Understands how networks work, understanding of network protocols and socket level programming.Understands the entire programming stack, hardware (CPU + Memory + Cache + Interrupts + microcode), binary code, assembly, static and dynamic linking, compilation, interpretation, JIT compilation, garbage collection, heap, stack, memory addressing… 
Software Engineering
 2n (Level 0)n2 (Level 1)n (Level 2)log(n) (Level 3)Comments
source code version controlFolder backups by dateVSS and beginning CVS/SVN userProficient in using CVS and SVN features. Knows how to branch and merge, use patches setup repository properties etc.Knowledge of distributed VCS systems. Has tried out Bzr/Mercurial/Darcs/Git 
build automationOnly knows how to build from IDEKnows how to build the system from the command lineCan setup a script to build the basic systemCan setup a script to build the system and also documentation, installers, generate release notes and tag the code in source control 
automated testingThinks that all testing is the job of the testerHas written automated unit tests and comes up with good unit test cases for the code that is being writtenHas written code in TDD mannerUnderstands and is able to setup automated functional, load/performance and UI tests 
Programming
 2n (Level 0)n2 (Level 1)n (Level 2)log(n) (Level 3)Comments
problem decompositionOnly straight line code with copy paste for reuseAble to break up problem into multiple functionsAble to come up with reusable functions/objects that solve the overall problemUse of appropriate data structures and algorithms and comes up with generic/object-oriented code that encapsulate aspects of the problem that are subject to change. 
systems decompositionNot able to think above the level of a single file/classAble to break up problem space and design solution as long as it is within the same platform/technologyAble to design systems that span multiple technologies/platforms.Able to visualize and design complex systems with multiple product lines and integrations with external systems. Also should be able to design operations support systems like monitoring, reporting, fail overs etc. 
communicationCannot express thoughts/ideas to peers. Poor spelling and grammar.Peers can understand what is being said. Good spelling and grammar.Is able to effectively communicate with peersAble to understand and communicate thoughts/design/ideas/specs in a unambiguous manner and adjusts communication as per the contextThis is an often under rated but very critical criteria for judging a programmer. With the increase in outsourcing of programming tasks to places where English is not the native tongue this issue has become more prominent. I know of several projects that failed because the programmers could not understand what the intent of the communication was.
code organization within a fileno evidence of organization within a fileMethods are grouped logically or by accessibilityCode is grouped into regions and well commented with references to other source filesFile has license header, summary, well commented, consistent white space usage. The file should look beautiful. 
 2n (Level 0)n2 (Level 1)n (Level 2)log(n) (Level 3)Comments
code organization across filesNo thought given to organizing code across filesRelated files are grouped into a folderEach physical file has a unique purpose, for e.g. one class definition, one feature implementation etc.Code organization at a physical level closely matches design and looking at file names and folder distribution provides insights into design 
source tree organizationEverything in one folderBasic separation of code into logical folders.No circular dependencies, binaries, libs, docs, builds, third-party code all organized into appropriate foldersPhysical layout of source tree matches logical hierarchy and organization. The directory names and organization provide insights into the design of the system.The difference between this and the previous item is in the scale of organization, source tree organization relates to the entire set of artifacts that define the system.
code readabilityMono-syllable namesGood names for files, variables classes, methods etc.No long functions, comments explaining unusual code, bug fixes, code assumptionsCode assumptions are verified using asserts, code flows naturally – no deep nesting of conditionals or methods 
defensive codingDoesn’t understand the conceptChecks all arguments and asserts critical assumptions in codeMakes sure to check return values and check for exceptions around code that can fail.Has his own library to help with defensive coding, writes unit tests that simulate faults 
 2n (Level 0)n2 (Level 1)n (Level 2)log(n) (Level 3)Comments
error handlingOnly codes the happy caseBasic error handling around code that can throw exceptions/generate errorsEnsures that error/exceptions leave program in good state, resources, connections and memory is all cleaned up properlyCodes to detect possible exception before, maintain consistent exception handling strategy in all layers of code, come up with guidelines on exception handling for entire system. 
IDEMostly uses IDE for text editingKnows their way around the interface, able to effectively use the IDE using menus.Knows keyboard shortcuts for most used operations.Has written custom macros 
APINeeds to look up the documentation frequentlyHas the most frequently used APIs in memoryVast and In-depth knowledge of the APIHas written libraries that sit on top of the API to simplify frequently used tasks and to fill in gaps in the APIE.g. of API can be Java library, .net framework or the custom API for the application
frameworksHas not used any framework outside of the core platformHas heard about but not used the popular frameworks available for the platform.Has used more than one framework in a professional capacity and is well-versed with the idioms of the frameworks.Author of framework 
 2n (Level 0)n2 (Level 1)n (Level 2)log(n) (Level 3)Comments
requirementsTakes the given requirements and codes to specCome up with questions regarding missed cases in the specUnderstand complete picture and come up with entire areas that need to be specedAble to suggest better alternatives and flows to given requirements based on experience 
scriptingNo knowledge of scripting toolsBatch files/shell scriptsPerl/Python/Ruby/VBScript/PowershellHas written and published reusable code 
databaseThinks that Excel is a databaseKnows basic database concepts, normalization, ACID, transactions and can write simple selectsAble to design good and normalized database schemas keeping in mind the queries that’ll have to be run, proficient in use of views, stored procedures, triggers and user defined types. Knows difference between clustered and non-clustered indexes. Proficient in use of ORM tools.Can do basic database administration, performance optimization, index optimization, write advanced select queries, able to replace cursor usage with relational sql, understands how data is stored internally, understands how indexes are stored internally, understands how databases can be mirrored, replicated etc. Understands how the two phase commit works. 
Experience
 2n (Level 0)n2 (Level 1)n (Level 2)log(n) (Level 3)Comments
languages with professional experienceImperative or Object OrientedImperative, Object-Oriented and declarative (SQL), added bonus if they understand static vs dynamic typing, weak vs strong typing and static inferred typesFunctional, added bonus if they understand lazy evaluation, currying, continuationsConcurrent (Erlang, Oz) and Logic (Prolog) 
platforms with professional experience12-34-56+ 
years of professional experience12-56-910+ 
domain knowledgeNo knowledge of the domainHas worked on at least one product in the domain.Has worked on multiple products in the same domain.Domain expert. Has designed and implemented several products/solutions in the domain. Well versed with standard terms, protocols used in the domain. 
Knowledge
 2n (Level 0)n2 (Level 1)n (Level 2)log(n) (Level 3)Comments
tool knowledgeLimited to primary IDE (VS.Net, Eclipse etc.)Knows about some alternatives to popular and standard tools.Good knowledge of editors, debuggers, IDEs, open source alternatives etc. etc. For e.g. someone who knows most of the tools from Scott Hanselman’s power tools list. Has used ORM tools.Has actually written tools and scripts, added bonus if they’ve been published. 
languages exposed toImperative or Object OrientedImperative, Object-Oriented and declarative (SQL), added bonus if they understand static vs dynamic typing, weak vs strong typing and static inferred typesFunctional, added bonus if they understand lazy evaluation, currying, continuationsConcurrent (Erlang, Oz) and Logic (Prolog) 
codebase knowledgeHas never looked at the codebaseBasic knowledge of the code layout and how to build the systemGood working knowledge of code base, has implemented several bug fixes and maybe some small features.Has implemented multiple big features in the codebase and can easily visualize the changes required for most features or bug fixes. 
knowledge of upcoming technologiesHas not heard of the upcoming technologiesHas heard of upcoming technologies in the fieldHas downloaded the alpha preview/CTP/beta and read some articles/manualsHas played with the previews and has actually built something with it and as a bonus shared that with everyone else 
 2n (Level 0)n2 (Level 1)n (Level 2)log(n) (Level 3)Comments
platform internalsZero knowledge of platform internalsHas basic knowledge of how the platform works internallyDeep knowledge of platform internals and can visualize how the platform takes the program and converts it into executable code.Has written tools to enhance or provide information on platform internals. For e.g. disassemblers, decompilers, debuggers etc. 
booksUnleashed series, 21 days series, 24 hour series, dummies series…Code Complete, Don’t Make me Think, Mastering Regular ExpressionsDesign Patterns, Peopleware, Programming Pearls, Algorithm Design Manual, Pragmatic Programmer, Mythical Man monthStructure and Interpretation of Computer Programs, Concepts Techniques, Models of Computer Programming, Art of Computer Programming, Database systems , by C. J Date, Thinking Forth, Little Schemer 
blogsHas heard of them but never got the time.Reads tech/programming/software engineering blogs and listens to podcasts regularly.Maintains a link blog with some collection of useful articles and tools that he/she has collectedMaintains a blog in which personal insights and thoughts on programming are shared

程序员能力矩阵(中英文对照) 对照着看一下吧,比较全面的介绍了程序员应具备的能力。 立即下载

相关推荐

从碰撞电离到雪崩击穿:Sentaurus仿真中的模型选择与验证艺术

本文深入探讨了Sentaurus TCAD中雪崩击穿模型的选取与验证方法,特别关注平行平面结的仿真实践。通过对比Chynoweth、van Overstraeten等主流模型的适用场景与精度差异,结合具体案例展示了从几何建模到边界条件设定的完整验证流程,并针对非理想因素提供了有效的补偿技术,助力工程师提升器件仿真的准确性与可靠性。

weixin_29074295的博客 593

程序员自我修养1:能力矩阵

程序员自我修养1:能力矩阵 资料来自与网络整理,仅供学习参考,不用于商业用途 请注意,每个级别的知识都是累积的。在 n级意味着您还了解,若低于n的水平,说明还需要努力学习,掌握 前言 程序员能力矩阵可以一定程度上反应自己当前的能力水平,同时也给自己一个努力的方向,让自己找到要努力的方向和目标。 本文可供大家检测自己目前所在的能力水平,同时也方便大家制定自己下一步需要努力的方向,使自己早日称为优秀的程序员,资深专家 Part1: 计算机科学 chart1: 数据结构 1. 级别说明 2n(Leve

Qingwen Yi的博客 3739

Fluent新手避坑:遇到‘Floating point exception’别慌,这7个排查步骤帮你搞定

本文为Fluent新手提供了遇到‘Floating point exception’错误时的7个详细排查步骤。从理解浮点异常的本质到边界条件检查、时间步长设置、求解器选择、网格优化、亚松弛因子调节以及高阶格式的取舍,帮助用户快速定位并解决问题,确保CFD仿真的稳定性和准确性。

weixin_30480075的博客 260

[架构之路-152]-《软考-系统分析师》- 8-软件工程-2-软件工程的N维矩阵模型与软件开发方法(形式化方法、逆 向 工 程)

近年来,形式化方法己不再只是一种研究所里的学术研究工作,而是己经开始被工业界接受并应用于开发实际的系统。例如,在需求分析中,形式化方法的思想是利用。

文火冰糖(王文兵)的博客 6449

基于 Datawhale 开源量化投资学习指南(10):基于 LightGBM 的量化选股

通过本篇文章,我们深入探索了如何运用 LightGBM 机器学习模型实现量化选股。首先,我们通过获取股票的历史数据,进行特征工程和标签制作,将选股问题转化为一个分类问题。接着,我们使用 LightGBM 训练模型,并在验证集和测试集中评估了模型的表现。该选股策略的核心在于结合机器学习算法,从历史数据中寻找能够捕捉股票短期涨跌的关键特征,从而为投资者提供辅助决策支持。虽然本文的模型取得了一定的效果,但这只是量化投资领域的一小部分。

不想宅的冷同学 1348

Isaac Sim 6 利用Replicator实现高效语义分割与实例分割(实践指南5.10)

本文详细介绍了如何利用Isaac Sim 6的Replicator工具高效生成语义分割和实例分割数据集。通过虚拟环境自动标注,效率提升20倍以上,特别适用于农业机器人等计算机视觉项目。文章包含环境配置、场景构建、批量标注技巧及实例分割处理等实战指南,帮助开发者快速掌握合成数据生成技术。

weixin_42526415的博客 268

(转)软件工程师能力矩阵

玩笑的博客 1646

transformer中QKV的通俗理解(剩女与备胎的故事)

用vit的时候读了一下transformer的思想,前几天面试结束之后发现对QKV又有点忘记了, 写一篇文章来记录一下 参考链接: 哔哩哔哩:在线激情讲解transformer&Attention注意力机制(上)在线激情讲解transformer&Attention注意力机制(上)_哔哩哔哩_bilibiliAttention is all you need介绍 更具体的介绍可以去阅读论文在Attention is all you need这篇文章中提出了著名的Transformer模型Transforme

Peter的博客 1万+

聊聊程序员的能力矩阵

我在之前的文章提过,为啥你5年经验比不过人家2年工作经验,这都是刻意练习的结果,因为你5年的工作经验可能是1年经验在舒适区里面重复了5次,而别人不断打怪升级。这个时候就有人说了,涛哥我们...

涛哥聊Python 1338

单相PWM整流器四象限运行原理

简述单相PWM整流器四象限运行原理。

m0_75208156的博客 8308

VisionMaster4.3.0+C#开发环境搭建实战:如何快速跑通第一个视觉检测demo?

本文详细介绍了海康VisionMaster 4.3.0机器视觉平台与C#的开发环境搭建实战。从软件安装、示例程序导入、解决NuGet包冲突,到配置并成功运行第一个视觉检测Demo,提供了完整的步骤指南和常见问题排查方法,帮助开发者快速上手二次开发。

weixin_29219189的博客 406

开发人员能力矩阵

MicrosoftInternetExplorer402DocumentNotSpecified7.8Normal0开发人员能力矩阵 概述 本文档主要描述开发人员对不同技术领域掌握的深度。每一个技术领域包含4个层次,层次之间是递进关系。能力矩阵用于综合评估开发人员的技能分布。基本的代码编写 <table style="border-collapse:collapse

黑照的技术空间 7846

多模态轨迹预测:行人、车辆的交互式推理

多模态轨迹预测:行人、车辆的交互式推理 ,人工智能,计算机视觉,大模型,AI,本文围绕多模态轨迹预测中行人与车辆的交互式推理展开,介绍了其定义,即综合多种信息预测交通参与者未来多种轨迹。涵盖基础概念如轨迹表示、模态、交互关系,技术框架包括数据处理、特征提取、预测模型(物理、机器学习、深度学习模型等)及结果评估。还探讨了交互式推理方法、面临的不确定性处理等挑战、应用场景、未来发展方向、相关工具及实际案例,展现了该技术在智能交通等领域的重要性与发展潜力。​

不踩坑,不知道坑有多深;不总结,踩过的坑白踩。 14万+

程序员能力矩阵,Programmer Competency Matrix

http://sijinjoseph.com/programmer-competency-matrix/ mark 一下 TBD

fantasysolo的博客 219

廖雪峰Python教程[完整版]

廖雪峰的python教程整理的,已经排好版了,而且还是完整的,适合小白

STM32F407中文手册

STM32f407中文手册 本参考手册面向应用开发人员,提供有关使用 STM32F405xx/07xx、STM32F415xx/17xx、 STM32F42xxx 和 STM32F43xxx 微控制器存储器与外设的完整信息。STM32F405xx/07xx、STM32F415xx/17xx、STM32F42xxx 和 STM32F43xxx 构成一个微 控制器系列,各产品具有不同的存储器大小、封装和外设。有关订购信息以及器件的机械与电气特性,请参见数据手册。有关 ARM Cortex™-M4F 内核的信息,请参见《Cortex™-M4F 技术参考手册》。

程序员能力矩阵 Programmer Competency Matrix

原文:http://sijinjoseph.com/programmer-competency-matrix/ 注意:每个层次的知识都是渐增的,位于层次n,也蕴涵了你需了解所有低于层次n的知识。 计算机科学 Computer Science 2n(Level 0) n2(Level 1) n(Level 2) log(n)(Level 3) ...

dihuanglei2485的博客 192

win10 跳过U8环境检测的IE WebControls.rar

win10 安装u8的时候 提示IE WebControls 不通过,这个工具可以欺骗u8的检查。 跳过U8环境检测的IE WebControls。提示导入失败后,重新检测通过。

[FWD]Programmer Competency Matrix

系统中国 906

精雕软件(JDpaint) 5.5 绿色版

精雕软件(JDpaint) 5.5 绿色版精雕软件(JDpaint) 5.5 绿色版精雕软件(JDpaint) 5.5 绿色版

上一篇: java class loader
下一篇: c++ References vs. Pointers
FireCoder
博客等级 码龄17年 65粉丝 100原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值