{"id":18551997,"url":"https://github.com/bepb/programmer_competency_matrix","last_synced_at":"2026-01-25T01:01:49.254Z","repository":{"id":142340903,"uuid":"613259149","full_name":"BEPb/Programmer_Competency_Matrix","owner":"BEPb","description":null,"archived":false,"fork":false,"pushed_at":"2023-03-19T18:52:06.000Z","size":392,"stargazers_count":29,"open_issues_count":0,"forks_count":2,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-02-17T10:48:58.105Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/BEPb.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-03-13T08:16:14.000Z","updated_at":"2025-01-11T23:19:25.000Z","dependencies_parsed_at":null,"dependency_job_id":"ba5f2930-d087-4e5e-b28d-f0385d806df6","html_url":"https://github.com/BEPb/Programmer_Competency_Matrix","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/BEPb/Programmer_Competency_Matrix","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BEPb%2FProgrammer_Competency_Matrix","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BEPb%2FProgrammer_Competency_Matrix/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BEPb%2FProgrammer_Competency_Matrix/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BEPb%2FProgrammer_Competency_Matrix/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/BEPb","download_url":"https://codeload.github.com/BEPb/Programmer_Competency_Matrix/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BEPb%2FProgrammer_Competency_Matrix/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28740391,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-24T22:12:27.248Z","status":"ssl_error","status_checked_at":"2026-01-24T22:12:10.529Z","response_time":89,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-06T21:11:29.899Z","updated_at":"2026-01-25T01:01:49.236Z","avatar_url":"https://github.com/BEPb.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cp\u003e\n  \u003cimg  src=\"https://img.shields.io/github/stars/BEPb/Programmer_Competency_Matrix\" /\u003e\n  \u003cimg src=\"https://img.shields.io/github/contributors/BEPb/Programmer_Competency_Matrix\" /\u003e\n  \u003cimg src=\"https://img.shields.io/github/last-commit/BEPb/Programmer_Competency_Matrix\" /\u003e\n  \u003cimg src=\"https://visitor-badge.laobi.icu/badge?page_id=BEPb.Programmer_Competency_Matrix\" /\u003e\n  \u003cimg src=\"https://img.shields.io/github/languages/count/BEPb/Programmer_Competency_Matrix\" /\u003e\n  \u003cimg src=\"https://img.shields.io/github/languages/top/BEPb/Programmer_Competency_Matrix\" /\u003e\n  \u003cimg src=\"https://img.shields.io/badge/license-MIT-blue.svg?color=f64152\" /\u003e\n  \u003cimg  src=\"https://img.shields.io/github/issues/BEPb/Programmer_Competency_Matrix\" /\u003e\n  \u003cimg  src=\"https://img.shields.io/github/issues-pr/BEPb/Programmer_Competency_Matrix\" /\u003e\n\u003c/p\u003e\n\u003cdiv align=\"center\"\u003e\n\n\n\u003cimg src=\"./art/logo.png\" alt=\"Bot logo\" width=\"300\" height=\"200\"\u003e\n\n\n# Programmer Competency Matrix\n\n\u003c/div\u003e\n\nRead in other languages: [Русский](README.ru.md)\n\n## Hi all. \nToday is March 13, 2023, and it just so happens that for more than 3 years I have been actively studying python \nprogramming as well as data science. The contract ends in half a year and I decided that it was time to change \nactivities from a radio engineer to a machine learning specialist. But how to evaluate myself, how to show the \nfuture employer what I know, how I can develop??? Divide and rule (lat. divide et impera) - says the maxim of the \nRoman Senate, let's approach the answer to the question asked systematically. Let's separate all the components of \nmy specialist knowledge and evaluate them using the competence matrix.\n\nOf course, I didn’t reinvent the wheel and took a ready-made matrix (the most common version was proposed by Sijin \nJoseph [here](https://sijinjoseph.netlify.app/programmer-competency-matrix/)) and honestly answered these questions, \nthe answer was diligently put into separate files.\n\n#### in progress...\n\n\n\u003cdetails\u003e\n           \u003csummary\u003eComputer Science\u003c/summary\u003e\n           \u003cp\u003ein progress...\u003c/p\u003e\n\n- [ ] **Data structures**\n  - [x] Level 0 - Doesn’t know the difference between Array and LinkedList\n  - [x] Level 1 - Able to explain and use Arrays, LinkedLists, Dictionaries etc in practical programming tasks\n  - [x] Level 2 - Knows space and time tradeoffs of the basic data structures, Arrays vs LinkedLists, Able to explain\n    how hashtables can be implemented and can handle collisions, Priority queues and ways to implement them etc.\n  - [x] Level 3 - Knowledge of advanced data structures like B-trees, binomial and fibonacci heaps, AVL/Red Black trees,\n    Splay Trees, Skip Lists, tries etc.\n\n- [ ] **Algorithms**\n  - [x] Level 0 - Unable to find the average of numbers in an array (It’s hard to believe but I’ve interviewed such candidates)\n  - [x] Level 1 - Basic sorting, searching and data structure traversal and retrieval algorithms\n  - [x] Level 2 -  Tree, Graph, simple greedy and divide and conquer algorithms, is able to understand the \n    relevance of the levels of this matrix.\n  - [ ] Level 3 - Able to recognize and code  dynamic programming solutions, good knowledge of graph algorithms, \n    good knowledge of numerical computation algorithms, able to identify NP problems etc.\n    \n- [ ] **Systems programming**\n  - [x] Level 0 - Doesn’t know what a compiler, linker or interpreter is\n  - [x] Level 1 - Basic understanding of compilers, linker and interpreters. Understands what assembly code is and \n    how things work at the hardware level. Some knowledge of virtual memory and paging.\n  - [ ] Level 2 -  Understands kernel mode vs. user mode, multi-threading, synchronization primitives and how they’re\n        implemented, able to read assembly code. Understands how networks work, understanding of network protocols and\n        socket level programming.\n  - [ ] Level 3 - Understands the entire programming stack, hardware (CPU + Memory + Cache +\n        Interrupts + microcode), binary code, assembly, static and dynamic linking, compilation, interpretation, JIT\n        compilation, garbage collection, heap, stack, memory addressing…\n\n\u003c/details\u003e\n\u003cdetails\u003e\n           \u003csummary\u003eSoftware Engineering\u003c/summary\u003e\n            in progress...\n\n- [ ] **Source code version control**\n  - [x] Level 0 - Folder backups by date\n  - [x] Level 1 - VSS and beginning CVS/SVN user\n  - [x] Level 2 -  Proficient in using CVS and SVN features. Knows how to branch and merge, use patches setup repository \nproperties etc.\n  - [ ] Level 3 - Knowledge of  distributed VCS systems. Has tried out Bzr/Mercurial/Darcs/Git\n\n- [ ] **Build  automation**\n  - [x] Level 0 - Only knows how to build from IDE\n  - [x] Level 1 - Knows how to build the system from the command line\n  - [x] Level 2 - Can setup a script to build the basic system\n  - [ ] Level 3 - Can setup a script to build the system and also documentation, installers, generate release notes \n    and tag the code in source control\n\n- [ ] **Automated testing**\n  - [x] Level 0 - Thinks that all testing is the job of the tester\n  - [x] Level 1 - Has written automated unit tests and comes up with good unit test cases for the code that is being written\n  - [x] Level 2 - Has written code in TDD manner\n  - [ ] Level 3 - Understands and is able to setup automated functional, load/performance and UI tests\n\n\u003c/details\u003e\n\u003cdetails\u003e\n           \u003csummary\u003eProgramming\u003c/summary\u003e\n            in progress...\n \n- [ ] **Problem decomposition**\n  - [x] Level 0 - Only straight line code with copy paste for reuse\n  - [x] Level 1 - Able to break up problem into multiple functions\n  - [x] Level 2 -  Able to come up with reusable functions/objects that solve the overall problem\n  - [ ] Level 3 - Use of appropriate data structures and algorithms and comes up with generic/object-oriented code \n    that encapsulate aspects of the problem that are subject to change.\n\n\n- [ ] **Systems decomposition**\n  - [x] Level 0 - Not able to think above the level of a single file/class\n  - [x] Level 1 - Able to break up problem space and design solution as long as it is within the same platform/technology\n  - [x] Level 2 - Able to design systems that span multiple technologies/platforms.\n  - [ ] Level 3 - Able to visualize and design complex systems with multiple product lines and integrations with  \n    external systems. Also should be able to design operations support systems like monitoring, reporting, fail \n    overs etc.\n  \n- [ ] **Communication**\n  - [x] Level 0 - Cannot express thoughts/ideas to peers. Poor spelling and grammar.\n  - [x] Level 1 - Peers can understand what is being said. Good spelling and grammar.\n  - [x] Level 2 - Is able to effectively communicate with peers\n  - [ ] Level 3 - Able to understand and communicate thoughts/design/ideas/specs in a unambiguous\n        manner and adjusts communication as per the context\n  - This is an often under rated but very critical criteria\n        for judging a programmer. With the increase in outsourcing of programming tasks to places where English is not\n        the\n        native tongue this issue has become more prominent. I know of several projects that failed because the\n        programmers\n        could not understand what the intent of the communication was.\n  \n- [ ] **Code organization within a file**\n  - [x] Level 0 - no evidence of organization within a file\n  - [x] Level 1 - Methods are grouped logically or by accessibility\n  - [x] Level 2 - Code is grouped into regions and well commented with references to other source files \n  - [ ] Level 3 - File has license header, summary, well commented, consistent white space usage. The file should look\n        beautiful.\n  \n- [ ] **Code organization across files**\n  - [x] Level 0 - No thought given to organizing code across files\n  - [x] Level 1 - Related files are grouped into a folder\n  - [x] Level 2 -  Each physical file has a unique purpose, for e.g. one class definition, one feature implementation etc.\n  - [ ] Level 3 - Code organization at a physical level closely\n        matches design and looking at file names and folder distribution provides insights into\n        design\n \n- [ ] **Source tree organization**\n  - [x] Level 0 - Everything in one folder\n  - [x] Level 1 - Basic separation of code into logical folders.\n  - [x] Level 2 - No circular dependencies, binaries, libs, docs, builds, third-party code all\n        organized into appropriate folders\n  - [ ] Level 3 - Physical layout of source tree matches logical hierarchy and organization.\n        The directory names and organization provide insights into the design of the system.\n  - The difference between\n        this and the previous item is in the scale of organization, source tree organization relates to the entire set\n        of\n        artifacts that define the system.\n \n- [ ] **Code readability**\n  - [x] Level 0 - Mono-syllable names\n  - [x] Level 1 - Good names for files, variables classes, methods etc.\n  - [x] Level 2 - No long functions, comments explaining unusual code, bug fixes,\n        code assumptions\n  - [ ] Level 3 - Code assumptions are verified using asserts, code flows naturally – no deep nesting of\n        conditionals or methods\n \n- [ ] **Defensive coding**\n  - [x] Level 0 - Doesn’t understand the concept\n  - [x] Level 1 - Checks all arguments and asserts critical assumptions in code\n  - [x] Level 2 - Makes sure to check return values and check for exceptions around code that can fail.\n  - [ ] Level 3 - Has his own library to help with defensive coding, writes unit tests that simulate faults\n \n- [ ] **Error handling**\n  - [x] Level 0 - Only codes the happy case\n  - [x] Level 1 - Basic error handling around code that can throw exceptions/generate errors\n  - [x] Level 2 -  Ensures that  error/exceptions leave program in good state, resources, connections and memory is \n    all cleaned up  properly\n  - [ ] Level 3 - Codes to detect possible exception before, maintain consistent exception handling strategy in all\n        layers of code, come up with guidelines on exception handling for entire system.\n \n- [ ] **IDE**\n  - [x] Level 0 - Mostly uses IDE for text editing\n  - [x] Level 1 - Knows their way around the interface,\n        able to effectively use the IDE using menus.\n  - [x] Level 2 -  Knows keyboard shortcuts for most used operations.\n  - [ ] Level 3 - Has written custom macros\n \n- [ ] **API**\n  - [x] Level 0 - Needs to look up the documentation frequently\n  - [x] Level 1 - Has the most frequently used APIs in memory\n  - [x] Level 2 - Vast and In-depth knowledge of the API\n  - [ ] Level 3 - Has written libraries that sit on top of the API to simplify frequently used tasks and to fill in gaps\n        in the API\n  - E.g. of API can be Java library, .net framework or the custom API for the\n        application\n \n- [ ] **Frameworks**\n  - [x] Level 0 - Has not used any framework outside of the core platform\n  - [x] Level 1 - Has heard about but not used the popular frameworks available for the platform.\n  - [x] Level 2 - Has used more than one framework in a professional capacity and is well-versed with the idioms of \n    the frameworks.\n  - [ ] Level 3 - Author of framework\n \n- [ ] **Requirements**\n  - [x] Level 0 - Takes the given requirements and codes to spec\n  - [x] Level 1 - Come up with questions regarding missed cases in the spec\n  - [x] Level 2 - Understand complete picture and come up with entire areas that need to be speced \n  - [ ] Level 3 - Able to suggest better alternatives and flows to given requirements based on  experience\n \n- [ ] **Scripting**\n  - [x] Level 0 - No knowledge of scripting tools\n  - [x] Level 1 - Batch files/shell scripts\n  - [x] Level 2 - Perl/Python/Ruby/VBScript/Powershell\n  - [ ] Level 3 - Has written and published reusable code\n \n- [ ] **Database**\n  - [x] Level 0 - Thinks that Excel is a database\n  - [x] Level 1 - Knows basic database concepts, normalization, ACID, transactions and can write simple selects\n  - [x] Level 2 - Able to design good and normalized  database schemas keeping in mind the queries that’ll have to \n    be run, proficient in use of views, stored procedures, triggers and user defined types. Knows difference \n    between clustered and non-clustered indexes. Proficient in use of ORM tools.\n  - [ ] Level 3 - Can do basic database administration, performance optimization, index optimization, write\n        advanced select queries, able to replace cursor usage with relational sql, understands how data is stored\n        internally,  understands how indexes are stored internally, understands how databases can be mirrored, \n    replicated etc. Understands how the two phase commit works.\n\n\n\u003c/details\u003e\n\u003cdetails\u003e\n           \u003csummary\u003eExperience\u003c/summary\u003e\n            in progress...\n\n- [ ] **Languages with professional experience**\n  - [x] Level 0 - Imperative or Object Oriented\n  - [x] Level 1 - Imperative, Object-Oriented and declarative (SQL), added bonus if they understand static vs dynamic\n        typing, weak vs strong typing and static inferred types\n  - [x] Level 2 - Functional, added bonus if they understand lazy\n        evaluation, currying, continuations\n  - [ ] Level 3 - Concurrent (Erlang, Oz) and Logic (Prolog)\n\n \n- [ ] **Platforms with professional\n        experience**\n  - [x] Level 0 - 1\n  - [x] Level 1 - 2-3\n  - [x] Level 2 - 4-5\n  - [ ] Level 3 - 6+\n \n- [ ] **Years of professional experience**\n  - [x] Level 0 - 1\n  - [x] Level 1 - 2-5\n  - [x] Level 2 - 6-9\n  - [ ] Level 3 - 10+\n \n- [ ] **Domain knowledge**\n  - [x] Level 0 - No knowledge of the domain\n  - [x] Level 1 - Has worked on at least one product in the domain.\n  - [x] Level 2 - Has worked on multiple products in the same domain.\n  - [ ] Level 3 - Domain expert. Has designed and implemented several products/solutions in the\n        domain. Well versed with standard terms, protocols used in the domain.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n           \u003csummary\u003eKnowledge\u003c/summary\u003e\n            in progress...\n\n- [ ] **Tool knowledge**\n  - [x] Level 0 - Limited to primary IDE (VS.Net, Eclipse etc.)\n  - [x] Level 1 - Knows about some alternatives to popular and standard tools.\n  - [x] Level 2 - Good knowledge of editors, debuggers, IDEs, open source alternatives etc. etc. For e.g.\n        someone who knows most of the tools from Scott Hanselman’s power tools list. Has used ORM tools.\n  - [ ] Level 3 - Has actually written tools and scripts, added bonus if they’ve been published.\n \n- [ ] **Languages exposed to**\n  - [x] Level 0 - Imperative or Object Oriented\n  - [x] Level 1 - Imperative, Object-Oriented and declarative (SQL), added\n        bonus if they understand static vs dynamic typing, weak vs strong typing and static inferred\n        types\n  - [x] Level 2 -  Functional, added bonus if they understand lazy evaluation, currying, continuations\n  - [ ] Level 3 - Concurrent\n        (Erlang, Oz) and Logic (Prolog)\n \n- [ ] **Codebase knowledge**\n  - [x] Level 0 - Has never looked at the codebase\n  - [x] Level 1 - Basic knowledge of the code layout and how to build the system\n  - [x] Level 2 - Good working knowledge of code base, has implemented several bug fixes and maybe some small features.\n  - [ ] Level 3 - Has implemented multiple big  features in the codebase and can easily visualize the changes \n    required for most features or bug fixes.\n \n- [ ] **Knowledge of upcoming technologies**\n  - [x] Level 0 - Has not heard of the upcoming technologies\n  - [x] Level 1 - Has heard of upcoming technologies in the field\n  - [x] Level 2 - Has downloaded the alpha preview/CTP/beta and read some articles/manuals\n  - [ ] Level 3 - Has played with the previews and has actually built something with it and as a bonus shared that \n    with everyone else\n \n- [ ] **Platform internals**\n  - [x] Level 0 - Zero knowledge of platform internals\n  - [x] Level 1 - Has basic knowledge of how the platform works internally\n  - [x] Level 2 - Deep knowledge of platform internals and can visualize how the platform takes the program and\n        converts it into executable code.\n  - [ ] Level 3 - Has written tools to enhance or provide information on platform internals.\n        For e.g. disassemblers, decompilers, debuggers etc.\n \n- [ ] **Books**\n  - [x] Level 0 - Unleashed series, 21 days series, 24 hour series, dummies series…\n  - [x] Level 1 - Code Complete, Don’t Make me Think, Mastering Regular Expressions\n  - [x] Level 2 - Design Patterns, Peopleware, Programming Pearls, Algorithm Design Manual, Pragmatic Programmer,\n        Mythical Man month\n  - [ ] Level 3 - Structure and Interpretation of Computer Programs, Concepts Techniques, Models of\n        Computer Programming, Art of Computer Programming, Database systems , by C. J Date, Thinking Forth, Little\n        Schemer\n \n- [ ] **Blogs**\n  - [x] Level 0 - Has heard of them but never got the time.\n  - [x] Level 1 - Reads tech/programming/software engineering blogs and listens to podcasts regularly.\n  - [x] Level 2 - Maintains a link blog with some collection of useful articles and tools that he/she has collected\n  - [ ] Level 3 - Maintains a blog in which personal insights and thoughts on programming are shared\n \n\u003c/details\u003e\n\n\n\n\n\n\n\n\n\n---\n\n\u003cdetails\u003e\n           \u003csummary\u003eFull table\u003c/summary\u003e\n           \u003cp\u003e\n\u003c!--   my-table --\u003e\n\u003ctable width=\"80%\"\u003e\n\n\u003cthead\u003e\n    \u003ctr\u003e\n    \u003cth\u003e\u003ch4\u003eComputer Science\u003c/h4\u003e\u003c/th\u003e\n    \u003cth\u003e\u003c/th\u003e\n    \u003cth\u003e\u003c/th\u003e\n    \u003cth\u003e\u003c/th\u003e\n    \u003cth\u003e\u003c/th\u003e\n    \u003cth\u003e\u003c/th\u003e\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e (Level 0)\u003c/td\u003e\n    \u003ctd\u003e (Level 1)\u003c/td\u003e\n    \u003ctd\u003e (Level 2)\u003c/td\u003e\n    \u003ctd\u003e (Level 3)\u003c/td\u003e\n    \u003ctd\u003eComments\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n    \u003ctd\u003edata structures\u003c/td\u003e\n    \u003ctd background=\"green\"\u003eDoesn’t know the difference between Array and LinkedList\u003c/td\u003e\n    \u003ctd\u003eAble to explain and use Arrays, LinkedLists, Dictionaries etc in practical programming tasks\u003c/td\u003e\n    \u003ctd\u003eKnows space and time tradeoffs of the basic data structures, Arrays vs LinkedLists, Able to explain\n    how hashtables can be implemented and can handle collisions, Priority queues and ways to implement them etc.\n    \u003c/td\u003e\n    \u003ctd\u003eKnowledge of advanced data structures like B-trees, binomial and fibonacci heaps, AVL/Red Black trees,\n    Splay Trees, Skip Lists, tries etc.\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n    \u003ctd\u003ealgorithms\u003c/td\u003e\n\u003ctd\u003eUnable to find the average of numbers in an array (It’s hard to believe but I’ve interviewed such candidates)\u003c/td\u003e\n\u003ctd\u003eBasic sorting, searching and data structure traversal and retrieval algorithms\u003c/td\u003e\n\u003ctd\u003eTree, Graph, simple greedy and divide and conquer\nalgorithms, is able to understand the relevance of the levels of this matrix.\u003c/td\u003e\n\u003ctd\u003eAble to recognize and code\ndynamic programming solutions, good knowledge of graph algorithms, good knowledge of numerical computation\nalgorithms, able to identify NP problems etc.\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\u003c\u003e\n    \u003ctd\u003esystems programming\u003c/td\u003e\n    \u003ctd\u003eDoesn’t know\n        what a compiler, linker or interpreter is\n    \u003c/td\u003e\n    \u003ctd\u003eBasic understanding of compilers, linker and interpreters.\n        Understands what assembly code is and how things work at the hardware level. Some knowledge of virtual memory\n        and\n        paging.\n    \u003c/td\u003e\n    \u003ctd\u003eUnderstands kernel mode vs. user mode, multi-threading, synchronization primitives and how they’re\n        implemented, able to read assembly code. Understands how networks work, understanding of network protocols and\n        socket level programming.\n    \u003c/td\u003e\n    \u003ctd\u003eUnderstands the entire programming stack, hardware (CPU + Memory + Cache +\n        Interrupts + microcode), binary code, assembly, static and dynamic linking, compilation, interpretation, JIT\n        compilation, garbage collection, heap, stack, memory addressing…\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003e\u003ch4\u003eSoftware\n        Engineering\u003c/h4\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e2n (Level 0)\u003c/td\u003e\n    \u003ctd\u003en2\n        (Level 1)\n    \u003c/td\u003e\n    \u003ctd\u003en (Level 2)\u003c/td\u003e\n    \u003ctd\u003elog(n) (Level 3)\u003c/td\u003e\n    \u003ctd\u003eComments\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003esource code version\n        control\n    \u003c/td\u003e\n    \u003ctd\u003eFolder backups by date\u003c/td\u003e\n    \u003ctd\u003eVSS and beginning CVS/SVN user\u003c/td\u003e\n    \u003ctd\u003eProficient in using CVS and\n        SVN features. Knows how to branch and merge, use patches setup repository properties etc.\n    \u003c/td\u003e\n    \u003ctd\u003eKnowledge of\n        distributed VCS systems. Has tried out Bzr/Mercurial/Darcs/Git\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003ebuild\n        automation\n    \u003c/td\u003e\n    \u003ctd\u003eOnly knows how to build from IDE\u003c/td\u003e\n    \u003ctd\u003eKnows how to build the system from the command\n        line\n    \u003c/td\u003e\n    \u003ctd\u003eCan setup a script to build the basic system\u003c/td\u003e\n    \u003ctd\u003eCan setup a script to build the system and also\n        documentation, installers, generate release notes and tag the code in source\n        control\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eautomated testing\u003c/td\u003e\n    \u003ctd\u003eThinks that all testing is the job of the\n        tester\n    \u003c/td\u003e\n    \u003ctd\u003eHas written automated unit tests and comes up with good unit test cases for the code that is being\n        written\n    \u003c/td\u003e\n    \u003ctd\u003eHas written code in TDD manner\u003c/td\u003e\n    \u003ctd\u003eUnderstands and is able to setup automated functional,\n        load/performance and UI tests\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\n\n\u003ctr\u003e\n    \u003ctd\u003e\u003ch4\u003eProgramming\u003c/h4\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\n    \u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e2n (Level 0)\u003c/td\u003e\n    \u003ctd\u003en2 (Level 1)\u003c/td\u003e\n    \u003ctd\u003en (Level 2)\u003c/td\u003e\n    \u003ctd\u003elog(n) (Level 3)\n    \u003c/td\u003e\n    \u003ctd\u003eComments\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eproblem decomposition\u003c/td\u003e\n    \u003ctd\u003eOnly straight line code with copy paste for\n        reuse\n    \u003c/td\u003e\n    \u003ctd\u003eAble to break up problem into multiple functions\u003c/td\u003e\n    \u003ctd\u003eAble to come up with reusable\n        functions/objects that solve the overall problem\n    \u003c/td\u003e\n    \u003ctd\u003eUse of appropriate data structures and algorithms and comes\n        up with generic/object-oriented code that encapsulate aspects of the problem that are subject to change.\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003esystems decomposition\u003c/td\u003e\n    \u003ctd\u003eNot able to think above the level of a single\n        file/class\n    \u003c/td\u003e\n    \u003ctd\u003eAble to break up problem space and design solution as long as it is within the same\n        platform/technology\n    \u003c/td\u003e\n    \u003ctd\u003eAble to design systems that span multiple technologies/platforms.\u003c/td\u003e\n    \u003ctd\u003eAble to\n        visualize and design complex systems with multiple product lines and integrations with external systems. Also\n        should\n        be able to design operations support systems like monitoring, reporting, fail overs etc.\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003ecommunication\u003c/td\u003e\n    \u003ctd\u003eCannot express thoughts/ideas to peers. Poor spelling and grammar.\n    \u003c/td\u003e\n    \u003ctd\u003ePeers can understand what is being said. Good spelling and grammar.\u003c/td\u003e\n    \u003ctd\u003eIs able to effectively\n        communicate with peers\n    \u003c/td\u003e\n    \u003ctd\u003eAble to understand and communicate thoughts/design/ideas/specs in a unambiguous\n        manner and adjusts communication as per the context\n    \u003c/td\u003e\n    \u003ctd\u003eThis is an often under rated but very critical criteria\n        for judging a programmer. With the increase in outsourcing of programming tasks to places where English is not\n        the\n        native tongue this issue has become more prominent. I know of several projects that failed because the\n        programmers\n        could not understand what the intent of the communication was.\n    \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003ecode organization within a\n        file\n    \u003c/td\u003e\n    \u003ctd\u003eno evidence of organization within a file\u003c/td\u003e\n    \u003ctd\u003eMethods are grouped logically or by\n        accessibility\n    \u003c/td\u003e\n    \u003ctd\u003eCode is grouped into regions and well commented with references to other source\n        files\n    \u003c/td\u003e\n    \u003ctd\u003eFile has license header, summary, well commented, consistent white space usage. The file should look\n        beautiful.\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003ecode organization across files\u003c/td\u003e\n    \u003ctd\u003eNo thought given to organizing code\n        across files\n    \u003c/td\u003e\n    \u003ctd\u003eRelated files are grouped into a folder\u003c/td\u003e\n    \u003ctd\u003eEach physical file has a unique purpose, for e.\n        g. one class definition, one feature implementation etc.\n    \u003c/td\u003e\n    \u003ctd\u003eCode organization at a physical level closely\n        matches design and looking at file names and folder distribution provides insights into\n        design\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003esource tree organization\u003c/td\u003e\n    \u003ctd\u003eEverything in one folder\u003c/td\u003e\n    \u003ctd\u003eBasic separation\n        of code into logical folders.\n    \u003c/td\u003e\n    \u003ctd\u003eNo circular dependencies, binaries, libs, docs, builds, third-party code all\n        organized into appropriate folders\n    \u003c/td\u003e\n    \u003ctd\u003ePhysical layout of source tree matches logical hierarchy and organization.\n        The directory names and organization provide insights into the design of the system.\n    \u003c/td\u003e\n    \u003ctd\u003eThe difference between\n        this and the previous item is in the scale of organization, source tree organization relates to the entire set\n        of\n        artifacts that define the system.\n    \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003ecode readability\u003c/td\u003e\n    \u003ctd\u003eMono-syllable names\u003c/td\u003e\n    \u003ctd\u003eGood names\n        for files, variables classes, methods etc.\n    \u003c/td\u003e\n    \u003ctd\u003eNo long functions, comments explaining unusual code, bug fixes,\n        code assumptions\n    \u003c/td\u003e\n    \u003ctd\u003eCode assumptions are verified using asserts, code flows naturally – no deep nesting of\n        conditionals or methods\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003edefensive coding\u003c/td\u003e\n    \u003ctd\u003eDoesn’t understand the\n        concept\n    \u003c/td\u003e\n    \u003ctd\u003eChecks all arguments and asserts critical assumptions in code\u003c/td\u003e\n    \u003ctd\u003eMakes sure to check return\n        values and check for exceptions around code that can fail.\n    \u003c/td\u003e\n    \u003ctd\u003eHas his own library to help with defensive coding,\n        writes unit tests that simulate faults\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eerror handling\u003c/td\u003e\n    \u003ctd\u003eOnly codes the happy\n        case\n    \u003c/td\u003e\n    \u003ctd\u003eBasic error handling around code that can throw exceptions/generate errors\u003c/td\u003e\n    \u003ctd\u003eEnsures that\n        error/exceptions leave program in good state, resources, connections and memory is all cleaned up\n        properly\n    \u003c/td\u003e\n    \u003ctd\u003eCodes to detect possible exception before, maintain consistent exception handling strategy in all\n        layers of code, come up with guidelines on exception handling for entire system.\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eIDE\u003c/td\u003e\n    \u003ctd\u003eMostly uses IDE for text editing\u003c/td\u003e\n    \u003ctd\u003eKnows their way around the interface,\n        able to effectively use the IDE using menus.\n    \u003c/td\u003e\n    \u003ctd\u003eKnows keyboard shortcuts for most used operations.\u003c/td\u003e\n    \u003ctd\u003eHas\n        written custom macros\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eAPI\u003c/td\u003e\n    \u003ctd\u003eNeeds to look up the documentation\n        frequently\n    \u003c/td\u003e\n    \u003ctd\u003eHas the most frequently used APIs in memory\u003c/td\u003e\n    \u003ctd\u003eVast and In-depth knowledge of the\n        API\n    \u003c/td\u003e\n    \u003ctd\u003eHas written libraries that sit on top of the API to simplify frequently used tasks and to fill in gaps\n        in the API\n    \u003c/td\u003e\n    \u003ctd\u003eE.g. of API can be Java library, .net framework or the custom API for the\n        application\n    \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eframeworks\u003c/td\u003e\n    \u003ctd\u003eHas not used any framework outside of the core platform\u003c/td\u003e\n    \u003ctd\u003eHas\n        heard about but not used the popular frameworks available for the platform.\n    \u003c/td\u003e\n    \u003ctd\u003eHas used more than one framework\n        in a professional capacity and is well-versed with the idioms of the frameworks.\n    \u003c/td\u003e\n    \u003ctd\u003eAuthor of\n        framework\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003erequirements\u003c/td\u003e\n    \u003ctd\u003eTakes the given requirements and codes to spec\u003c/td\u003e\n    \u003ctd\u003eCome\n        up with questions regarding missed cases in the spec\n    \u003c/td\u003e\n    \u003ctd\u003eUnderstand complete picture and come up with entire\n        areas that need to be speced\n    \u003c/td\u003e\n    \u003ctd\u003eAble to suggest better alternatives and flows to given requirements based on\n        experience\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003escripting\u003c/td\u003e\n    \u003ctd\u003eNo knowledge of scripting tools\u003c/td\u003e\n    \u003ctd\u003eBatch files/shell\n        scripts\n    \u003c/td\u003e\n    \u003ctd\u003ePerl/Python/Ruby/VBScript/Powershell\u003c/td\u003e\n    \u003ctd\u003eHas written and published reusable\n        code\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003edatabase\u003c/td\u003e\n    \u003ctd\u003eThinks that Excel is a database\u003c/td\u003e\n    \u003ctd\u003eKnows basic database\n        concepts, normalization, ACID, transactions and can write simple selects\n    \u003c/td\u003e\n    \u003ctd\u003eAble to design good and normalized\n        database schemas keeping in mind the queries that’ll have to be run, proficient in use of views, stored\n        procedures,\n        triggers and user defined types. Knows difference between clustered and non-clustered indexes. Proficient in use\n        of\n        ORM tools.\n    \u003c/td\u003e\n    \u003ctd\u003eCan do basic database administration, performance optimization, index optimization, write\n        advanced select queries, able to replace cursor usage with relational sql, understands how data is stored\n        internally,\n        understands how indexes are stored internally, understands how databases can be mirrored, replicated etc.\n        Understands how the two phase commit works.\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\n\u003ctr\u003e\n    \u003ctd\u003e\u003ch4\u003eExperience\u003c/h4\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\n    \u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e2n (Level 0)\u003c/td\u003e\n    \u003ctd\u003en2 (Level 1)\u003c/td\u003e\n    \u003ctd\u003en (Level 2)\u003c/td\u003e\n    \u003ctd\u003elog(n)\n        (Level 3)\n    \u003c/td\u003e\n    \u003ctd\u003eComments\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003elanguages with professional experience\u003c/td\u003e\n    \u003ctd\u003eImperative or Object\n        Oriented\n    \u003c/td\u003e\n    \u003ctd\u003eImperative, Object-Oriented and declarative (SQL), added bonus if they understand static vs dynamic\n        typing, weak vs strong typing and static inferred types\n    \u003c/td\u003e\n    \u003ctd\u003eFunctional, added bonus if they understand lazy\n        evaluation, currying, continuations\n    \u003c/td\u003e\n    \u003ctd\u003eConcurrent (Erlang, Oz) and Logic (Prolog)\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eplatforms with professional\n        experience\n    \u003c/td\u003e\n    \u003ctd\u003e1\u003c/td\u003e\n    \u003ctd\u003e2-3\u003c/td\u003e\n    \u003ctd\u003e4-5\u003c/td\u003e\n    \u003ctd\u003e6+\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eyears of professional\n        experience\n    \u003c/td\u003e\n    \u003ctd\u003e1\u003c/td\u003e\n    \u003ctd\u003e2-5\u003c/td\u003e\n    \u003ctd\u003e6-9\u003c/td\u003e\n    \u003ctd\u003e10+\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003edomain knowledge\u003c/td\u003e\n    \u003ctd\u003eNo\n        knowledge of the domain\n    \u003c/td\u003e\n    \u003ctd\u003eHas worked on at least one product in the domain.\u003c/td\u003e\n    \u003ctd\u003eHas worked on multiple\n        products in the same domain.\n    \u003c/td\u003e\n    \u003ctd\u003eDomain expert. Has designed and implemented several products/solutions in the\n        domain. Well versed with standard terms, protocols used in the domain.\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\n\u003ctr\u003e\n    \u003ctd\u003e\u003ch4\u003eKnowledge\u003c/h4\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003etool\n        knowledge\n    \u003c/td\u003e\n    \u003ctd\u003eLimited to primary IDE (VS.Net, Eclipse etc.)\u003c/td\u003e\n    \u003ctd\u003eKnows about some alternatives to popular and\n        standard tools.\n    \u003c/td\u003e\n    \u003ctd\u003eGood knowledge of editors, debuggers, IDEs, open source alternatives etc. etc. For e.g.\n        someone who knows most of the tools from Scott Hanselman’s power tools list. Has used ORM tools.\n    \u003c/td\u003e\n    \u003ctd\u003eHas\n        actually written tools and scripts, added bonus if they’ve been published.\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003elanguages\n        exposed to\n    \u003c/td\u003e\n    \u003ctd\u003eImperative or Object Oriented\u003c/td\u003e\n    \u003ctd\u003eImperative, Object-Oriented and declarative (SQL), added\n        bonus if they understand static vs dynamic typing, weak vs strong typing and static inferred\n        types\n    \u003c/td\u003e\n    \u003ctd\u003eFunctional, added bonus if they understand lazy evaluation, currying, continuations\u003c/td\u003e\n    \u003ctd\u003eConcurrent\n        (Erlang, Oz) and Logic (Prolog)\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003ecodebase knowledge\u003c/td\u003e\n    \u003ctd\u003eHas never looked at the\n        codebase\n    \u003c/td\u003e\n    \u003ctd\u003eBasic knowledge of the code layout and how to build the system\u003c/td\u003e\n    \u003ctd\u003eGood working knowledge of\n        code base, has implemented several bug fixes and maybe some small features.\n    \u003c/td\u003e\n    \u003ctd\u003eHas implemented multiple big\n        features in the codebase and can easily visualize the changes required for most features or bug fixes.\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eknowledge of upcoming technologies\u003c/td\u003e\n    \u003ctd\u003eHas not heard of the upcoming\n        technologies\n    \u003c/td\u003e\n    \u003ctd\u003eHas heard of upcoming technologies in the field\u003c/td\u003e\n    \u003ctd\u003eHas downloaded the alpha\n        preview/CTP/beta and read some articles/manuals\n    \u003c/td\u003e\n    \u003ctd\u003eHas played with the previews and has actually built\n        something with it and as a bonus shared that with everyone else\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eplatform\n        internals\n    \u003c/td\u003e\n    \u003ctd\u003eZero knowledge of platform internals\u003c/td\u003e\n    \u003ctd\u003eHas basic knowledge of how the platform works\n        internally\n    \u003c/td\u003e\n    \u003ctd\u003eDeep knowledge of platform internals and can visualize how the platform takes the program and\n        converts it into executable code.\n    \u003c/td\u003e\n    \u003ctd\u003eHas written tools to enhance or provide information on platform internals.\n        For e.g. disassemblers, decompilers, debuggers etc.\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003ebooks\u003c/td\u003e\n    \u003ctd\u003eUnleashed series, 21\n        days series, 24 hour series, dummies series…\n    \u003c/td\u003e\n    \u003ctd\u003eCode Complete, Don’t Make me Think, Mastering Regular\n        Expressions\n    \u003c/td\u003e\n    \u003ctd\u003eDesign Patterns, Peopleware, Programming Pearls, Algorithm Design Manual, Pragmatic Programmer,\n        Mythical Man month\n    \u003c/td\u003e\n    \u003ctd\u003eStructure and Interpretation of Computer Programs, Concepts Techniques, Models of\n        Computer Programming, Art of Computer Programming, Database systems , by C. J Date, Thinking Forth, Little\n        Schemer\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n    \u003ctd\u003eblogs\u003c/td\u003e\n    \u003ctd\u003eHas heard of them but never got the time.\u003c/td\u003e\n    \u003ctd\u003eReads\n        tech/programming/software engineering blogs and listens to podcasts regularly.\n    \u003c/td\u003e\n    \u003ctd\u003eMaintains a link blog with\n        some collection of useful articles and tools that he/she has collected\n    \u003c/td\u003e\n    \u003ctd\u003eMaintains a blog in which personal\n        insights and thoughts on programming are shared\n    \u003c/td\u003e\n    \u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003c/p\u003e\n         \u003c/details\u003e\n\n\n\n\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbepb%2Fprogrammer_competency_matrix","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fbepb%2Fprogrammer_competency_matrix","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbepb%2Fprogrammer_competency_matrix/lists"}