2 cppfront: Recap Safety for C++ 50 esp. guaranteed program-meaningful initialization Simplicity for C++ 10 esp. for programmers cppfront: What’s new Types, reflection, metafunctions, … Simplification CppCon 2019 Parameter passing d0708 CppCon 2020 Patmat using is and as P2392 CppCon 2021 Simplicity (goal: 10 less to know) Context-free, order independent “Zero-overhead” backward compatibility conferences9 cppfront: Recap Safety for C++ 50 esp. guaranteed program-meaningful initialization Simplicity for C++ 10 esp. for programmers cppfront: What’s new Types, reflection, metafunctions, … Simplification

xvi NOTES 1 왜 RISC-V인가? Leonardo da Vinci (1452-1519)는 르네상 스 아키텍트, 공학자, 조각가이자 모나리자의 화가이다. Simplicity is the ultimate sophistication. —Leonardo da Vinci 1.1 소개 RISC-V(“RISC five”)는 보편적인 명령어 집합 구조(instruction 추가할 것이다. 심지어 새로운 선택이 메뉴에 만들어지더라도 선택으로 남아있을 뿐이지 증분형 ISA처럼 반드시 구현해야 하는 새로운 요구사항이 되는 것은 아니다. Cost Simplicity Performance Isolation of Arch from Impl 1.3 ISA 설계 101 RISC-V ISA를 소개하기 전에 컴퓨터 아키텍트가 ISA를 설계하는 비용은 두 배 정도의 면적이므로 RISC-V Rocket 다이에 비해 4배(22) 정도이다. 10% 더 작은 다이는 1.2(1.12) 팩터까지 비용을 줄일수도 있다. Simplicity 단순한 프로세서는 실행시간 예측이 쉬 우므로 임베디드 응용 프로그램에 도움이 될 수 있다. 마이크로컨 트롤러의 어셈블리어 프로그래머들은 주로 정확한 타이밍

inspect. What does "good code" mean for unit tests? Part 2: Code Readability 49Readability Simplicity! Jon Jagger: Unit tests should have a cyclomatic complexity of 1 Unit Tests should have no logic even more rare. Aspirational Goal, Not Rule “Simplicity is prerequisite for reliability.” ― Edsger W. Dijkstra Part 2: Code Readability Simplicity 50Readability float compute_pi() { return std::acos(-1); the code under test even if they don't know what it's supposed to do Part 2: Code Readability Simplicity 54Step 3: Interesting Conditions "Interesting" values derive from studying the algorithm and

WebSocket servers and clients in Python. It implements RFC 6455 with a focus on correctness and simplicity. It passes the Autobahn Testsuite. Built on top of asyncio, Python’s standard asynchronous I/O on a message broker, for example. That’s all! The design of the websockets API was driven by simplicity. You don’t have to worry about performing the opening or the closing handshake, answering pings Protocol. This class inherits most of its methods from WebSocketCommonProtocol. For the sake of simplicity, it doesn’t rely on a full HTTP implementation. Its support for HTTP responses is very limited

a big endian system we should swap the bytes we read, e.g. calling SwapEndian function, but for simplicity this is omitted. The counterpart of CheckDataLoaded is UpdateRawData (??). When it is called, are on a big endian system we should swap each accelerator contents before writing it, but for simplicity this is omitted. Other methods we named earlier (Add, Delete, Clear) are trivial to implement: a big endian system we should swap the bytes we read, e.g. calling SwapEndian function, but for simplicity this is omitted. Now, we should create a resource. Of which class? Well, we must use resfactory

a library for building WebSocket servers and clients in Python with a focus on correctness and simplicity. Built on top of asyncio, Python’s standard asynchronous I/O framework, it provides an elegant message broker, for example. 1.1.5 That’s all! The design of the websockets API was driven by simplicity. You don’t have to worry about performing the opening or the closing handshake, answering pings Protocol. This class inherits most of its methods from WebSocketCommonProtocol. For the sake of simplicity, it doesn’t rely on a full HTTP implementation. Its support for HTTP responses is very limited

Suggest Better ways Ask about Simplicity Remind about Evolution Identify Technical DebtWhat-If? Did you consider? Suggest Better ways Ask about Simplicity Remind about Evolution Identify Mistakes by Navigator Actual mistakesHow about… Discuss & implement Better ways Ensure Simplicity Enable Evolution Address Technical Debt Evaluate more options!High- Ownership Functional

useful. - Laozi Contents: 1. Radical simplicity 2. Readable source text 3. Minimum viable documentation 4. Better is better than perfect Radical simplicity • Scalability and interoperability are more more important than a menagerie of unessential features. Scale comes from simplicity, speed, and ease. In- teroperability comes from unadorned, digestable content. • Fewer distractions make for better

changeable forever.” A good package starts with a good name Simple is better than complex Simplicity matters –C.A.R. Hoare “There are two ways of constructing a software design: One way is to are no obvious deficiencies. The first method is far more difficult.” –Edsger W. Dijkstra “Simplicity is prerequisite for reliability.” –Brian Kernighan “Controlling complexity is the essence much shorter than that. Three keystrokes and you’ve just started a sub process.” –Rob Pike, Simplicity is Complicated, dotGo 2015 Goroutines are the key to resource ownership in Go Under what condition

a library for building WebSocket servers and clients in Python with a focus on correctness and simplicity. Built on top of asyncio, Python’s standard asynchronous I/O framework, it provides an elegant message broker, for example. 1.1.8 That’s all! The design of the websockets API was driven by simplicity. You don’t have to worry about performing the opening or the closing handshake, answering pings Protocol. This class inherits most of its methods from WebSocketCommonProtocol. For the sake of simplicity, it doesn’t rely on a full HTTP implementation. Its support for HTTP responses is very limited