book

Street Coder

Name: Street Coder
Author: Sedat Kapanoglu
ISBN: 9781617298370

by Sedat Kapanoglu

January 2022

Beginner to intermediate

272 pages

8h 34m

English

Manning Publications

Audiobook available

Read now

Unlock full access

inside front cover
Street Coder
Copyright
dedication
contents
front matter
prefaceacknowledgmentsabout this bookWho should read this bookHow this book is organized: A road mapAbout the codeliveBook discussion forumabout the authorabout the cover illustration
1 To the streets
1.1 What matters in the streets1.2 Who’s a street coder?1.3 Great street coders1.3.1 Questioning1.3.2 Results-driven1.3.3 High-throughput1.3.4 Embracing complexity and ambiguity1.4 The problems of modern software development1.4.1 Too many technologies1.4.2 Paragliding on paradigms1.4.3 The black boxes of technology1.4.4 Underestimating overhead1.4.5 Not my job1.4.6 Menial is genial1.5 What this book isn’t1.6 ThemesSummary
2 Practical theory
2.1 A crash course on algorithms2.1.1 Big-O better be good2.2 Inside data structures2.2.1 String2.2.2 Array2.2.3 List2.2.4 Linked list2.2.5 Queue2.2.6 Dictionary2.2.7 HashSet2.2.8 Stack2.2.9 Call stack2.3 What’s the hype on types?2.3.1 Being strong on the type2.3.2 Proof of validity2.3.3 Don’t framework hard, framework smart2.3.4 Types over typos2.3.5 To be nullable or non-nullable2.3.6 Better performance for free2.3.7 Reference types vs. value typesSummary
3 Useful anti-patterns
3.1 If it ain’t broke, break it3.1.1 Facing code rigidity3.1.2 Move fast, break things3.1.3 Respecting boundaries3.1.4 Isolating common functionality3.1.5 Example web page3.1.6 Leave no debt behind3.2 Write it from scratch3.2.1 Erase and rewrite3.3 Fix it, even if it ain’t broke3.3.1 Race toward the future3.3.2 Cleanliness is next to codeliness3.4 Do repeat yourself3.4.1 Reuse or copy?3.5 Invent it here3.6 Don’t use inheritance3.7 Don’t use classes3.7.1 Enum is yum!3.7.2 Structs rock!3.8 Write bad code3.8.1 Don’t use If/Else3.8.2 Use goto3.9 Don’t write code comments3.9.1 Choose great names3.9.2 Leverage functionsSummary
4 Tasty testing
4.1 Types of tests4.1.1 Manual testing4.1.2 Automated tests4.1.3 Living dangerously: Testing in production4.1.4 Choosing the right testing methodology4.2 How to stop worrying and love the tests4.3 Don’t use TDD or other acronyms4.4 Write tests for your own good4.5 Deciding what to test4.5.1 Respect boundaries4.5.2 Code coverage4.6 Don’t write tests4.6.1 Don’t write code4.6.2 Don’t write all the tests4.7 Let the compiler test your code4.7.1 Eliminate null checks4.7.2 Eliminate range checks4.7.3 Eliminate valid value checks4.8 Naming testsSummary

5 Rewarding refactoring
5.1 Why do we refactor?5.2 Architectural changes5.2.1 Identify the components5.2.2 Estimate the work and the risk5.2.3 The prestige5.2.4 Refactor to make refactoring easier5.2.5 The final stretch5.3 Reliable refactoring5.4 When not to refactorSummary
6 Security by scrutiny
6.1 Beyond hackers6.2 Threat modeling6.2.1 Pocket-sized threat models6.3 Write secure web apps6.3.1 Design with security in mind6.3.2 Usefulness of security by obscurity6.3.3 Don’t implement your own security6.3.4 SQL injection attacks6.3.5 Cross-site scripting6.3.6 Cross-site request forgery6.4 Draw the first flood6.4.1 Don’t use captcha6.4.2 Captcha alternatives6.4.3 Don’t implement a cache6.5 Storing secrets6.5.1 Keeping secrets in source codeSummary
7 Opinionated optimization
7.1 Solve the right problem7.1.1 Simple benchmarking7.1.2 Performance vs. responsiveness7.2 Anatomy of sluggishness7.3 Start from the top7.3.1 Nested loops7.3.2 String-oriented programming7.3.3 Evaluating 2b || !2b7.4 Breaking the bottle at the neck7.4.1 Don’t pack data7.4.2 Shop local7.4.3 Keep dependent works separated7.4.4 Be predictable7.4.5 SIMD7.5 1s and 0s of I/O7.5.1 Make I/O faster7.5.2 Make I/O non-blocking7.5.3 The archaic ways7.5.4 Modern async/await7.5.5 Gotchas of async I/O7.6 If all else fails, cacheSummary
8 Palatable scalability
8.1 Don’t use locks8.1.1 Double-checked locking8.2 Embrace inconsistency8.2.1 The dreaded NOLOCK8.3 Don’t cache database connections8.3.1 In the form of an ORM8.4 Don’t use threads8.4.1 The gotchas of async code8.4.2 MULTITHREADING with async8.5 Respect the monolithSummary
9 Living with bugs
9.1 Don’t fix bugs9.2 The error terror9.2.1 The bare truth of exceptions9.2.2 Don’t catch exceptions9.2.3 Exception resiliency9.2.4 Resiliency without transactions9.2.5 Exceptions vs. errors9.3 Don’t debug9.3.1 printf() debugging9.3.2 Dump diving9.3.3 Advanced rubber-duck debuggingSummary
index
inside back cover

Content preview from Street Coder

index

abstraction boundaries 56 – 57

alert command 156

algorithms

Big-O notation 17 – 18

defined 15 – 18

analyze prompt 239

anti-patterns 93

abstraction boundaries 56 – 57

bad code 83

breaking code 55

changing code 54, 62

classes 76

clean code 64 – 65

code rigidity 54 – 55

comments 88 – 90

enums 76 – 78

erasing and rewriting 61 – 62

example web page 59 – 60

gotos 85 – 88

If/Else constructs 83 – 85

inheritance 74 – 76

inventing 71 – 74

isolating common functionality 57 – 59

leveraging functions 90 – 92

naming 90

repetition 66 – 70

reusing vs. copying 70 – 71

structs 78 – 82

technical debt 60

upgrade scenarios 62 – 64

writing from scratch 61

applicability 224

architectural changes, refactoring 124, 126, 136

arrays 23 – 24

async code 219 – 220 ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781617298370Publisher Support Publisher Website Errata Page

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Street Coder

by Sedat Kapanoglu

index

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.