Skip to content
프로젝트

mtdvio/every-programmer-should-know

GitHub에서 보기

mtdvio/every-programmer-should-know has 100,623 GitHub stars and 8,777 forks. GitHot measured +1 stars in 24 hours. Last checked 2026-11-08 13:59 UTC. Last push 2025-12-29.

이 수치를 측정하는 방법

모든 소프트웨어 개발자가 알아야 할 (대부분 기술적인) 내용을 모은 컬렉션

측정된 스타 증가

in 24h
+1
in 7 days
기록 수집 중
in 15 days
기록 수집 중
in 1 month
기록 수집 중

서로 겹치는 기간의 순증가량이며 일별 합계가 아닙니다. 측정값이 없으면 비워 둡니다. 스타는 관심도를 나타내며 품질을 보장하지 않습니다.

README.md

Original

Every Programmer Should Know :thinking:

A collection of (mostly) technical things every software developer should know.

These are resources I can recommend to every programmer regardless of their skill level or tech stack

Highly opinionated :bomb:. Not backed by science. Comes in no particular order :recycle:


:star: it and share with a friendly developer!



P.S. You don't need to know all of that by heart to be a programmer. But knowing the stuff will help you become better! :muscle:

P.P.S. Contributions are welcome!


Introduction

Falsehoods

  • Awesome Falsehoods 💊 Curated list of falsehoods programmers believe in. Check for things you do not know about Strings, Addresses, Names, Numbers, Emails, Timezones and Dates and more.

Algorithms

Data Structures

Numbers

Strings

Latency

Time

Memory

Distributed Systems

Machine Learning

RegExp

Security

UX/Usability

SEO

Architecture

Code Design

Engineering Philosophy

Practices

Career

Fine-tune Your Resume

Open Source

Remote Work

Problem Solving

Soft Skills

Mental Health

  • Awesome Mental Health
    A curated list of awesome articles, websites and resources about mental health in the software industry.

Papers on Programming

Free Books on Programming

Services :zap:

Licenses

Where To Look For Further Info

Coding Practice Sites :zap:

Learning through entertainment:

Platform Engineering

A modern discipline that evolved from DevOps and SRE principles, focused on improving developer experience and productivity by building and managing self-service tools and workflows, often through an Internal Developer Platform (IDP). The goal is to reduce cognitive load on developers and streamline the path to production.

관련 프로젝트 살펴보기