Skip to content

Instantly share code, notes, and snippets.

View evoingram's full-sized avatar
🏠
Working from home

Erica L. Ingram evoingram

🏠
Working from home
View GitHub Profile
@evoingram
evoingram / Resume.md
Last active May 8, 2024 17:43
Resume

ERICA L. INGRAM

Contact

@evoingram
evoingram / 2020-0725
Last active September 2, 2020 17:30
2020-0725
So many things to do; it's been forever since I wrote and i should keep it up. But even though I've dropped some things, still
other things have gotten so busy and I'm really having weird feelings about where I'm at, how far I've come, and what I'm about
to do. I'm confident I look like a good candidate and the big test will be acing all the grueling interviews.
"You miss 100% of the shots you don't take," said by Wayne Gretzky, is now hanging up on the edge of a shelf which I view every
day all day when i sit down at my computer.
Here's what I have left to do before I will call myself officially prepped for interviews:
- Review pretty much all my notes
@evoingram
evoingram / read-books
Last active July 23, 2020 01:34
Books I've Read & Recommend
- Clean Code
- The Clean Coder
- Clean Architecture
- Design Patterns: Elements of Reusable Object-Oriented Software
- Web Scalability for Startup Engineers
@evoingram
evoingram / Mission-Statement-Notes
Last active February 9, 2020 22:20
Mission Statement Notes
Trying to make a personal mission statement, so i thought i'd answer some broad questions and see what comes up.
Use concrete examples, and don’t judge your own answers.
@evoingram
evoingram / Projects-In-Progress.md
Last active July 10, 2020 07:34
Current Projects In Progress:
@wojteklu
wojteklu / clean_code.md
Last active June 29, 2024 08:22
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.


General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules

@jboner
jboner / latency.txt
Last active June 29, 2024 19:54
Latency Numbers Every Programmer Should Know
Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference 0.5 ns
Branch mispredict 5 ns
L2 cache reference 7 ns 14x L1 cache
Mutex lock/unlock 25 ns
Main memory reference 100 ns 20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy 3,000 ns 3 us
Send 1K bytes over 1 Gbps network 10,000 ns 10 us
Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD