Dayton Outar > Recent Status Updates

Showing 1-30 of 1,554
Dayton Outar
Dayton Outar is finished with Effective Modern C++: 42 Specific Ways to Improve Your Use of C++11 and C++14
So, skimmed through chapter 5. Some concepts from the best practices in chapter 5 are intuitive. Others are not. Concurrency API as well needs some practice for certain parts to be intuitive.
Oct 01, 2024 01:59AM Add a comment
Effective Modern C++: 42 Specific Ways to Improve Your Use of C++11 and C++14

Dayton Outar
Dayton Outar is 81% done with Effective Modern C++: 42 Specific Ways to Improve Your Use of C++11 and C++14
Skimmed through chapter 7, Concurrency API. Now onto Chapter 5. Last 8 est practices left.
Sep 30, 2024 05:58PM Add a comment
Effective Modern C++: 42 Specific Ways to Improve Your Use of C++11 and C++14

Dayton Outar
Dayton Outar is on page 833 of 1552 of The Linux Programming Interface: A Linux and UNIX System Programming Handbook
I noticed I'm already familiar with a lot of topics. So, only chapters 41 to 44 left to do
Sep 20, 2024 02:27AM Add a comment
The Linux Programming Interface: A Linux and UNIX System Programming Handbook

Dayton Outar
Dayton Outar is on page 92 of 352 of The Pragmatic Programmer: Your Journey to Mastery, 20th Anniversary Edition
In computing, the term has come to signify a kind of independence or decoupling. Two or more things are orthogonal if changes in one do not affect any of the others. In a well-designed system, the database code will be orthogonal to the user interface: you can change the interface without affecting the database, and swap databases without changing the interface.
Sep 19, 2024 10:55AM Add a comment
The Pragmatic Programmer: Your Journey to Mastery, 20th Anniversary Edition

Dayton Outar
Dayton Outar is 60% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Skimmed through chapter 2. I pretty much had flashbacks to being in innovation lab sitting in there with a cross-functional team for about 4 months.
Sep 13, 2024 06:25AM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 57% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Chapter 2 (on page 30),
"If you spend all of your time working alone, you’re increasing the risk of unnecessary failure and cheating your potential for growth. Even though software development is deeply intellectual work that can require deep concentration and alone time, you must play that off against the value (and need!) for collaboration and review."
Sep 13, 2024 06:16AM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 57% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Chapters left to complete: 1, 2, 3, 6, 8, 9, 13, 14, 15, 19 and 22. (11 chapters left)
Sep 13, 2024 06:10AM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 57% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Realized that I read chapter 5 already. Skimmed through chapters 11 and 12
Sep 13, 2024 06:08AM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 43% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Only chapters 19 (Critique) and 22 (Large-Scale Changes) need to be read through for Part IV (Tools)
Sep 13, 2024 05:57AM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 43% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Skimmed through chapters 17 (Code Search) and chapter 20, (Static Analysis)
Sep 13, 2024 05:56AM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 37% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Chapter 4,
"When engineers do not focus on users of different nationalities, ethnicities, races, genders, ages, socioeconomic statuses, abilities, and belief systems, even the most talented staff will inadvertently fail their users."
Sep 13, 2024 01:45AM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 33% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Skimmed through chapter 18. I know and used a number of build systems.
Sep 12, 2024 03:48PM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 28% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Skimmed through chapters 16, 21 and 25. I do know of these and lobbied for them. I setup a local Nuget package manager. Chose hosting options on many occassions.
Sep 12, 2024 03:46PM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 15% done with Software Engineering at Google: Lessons Learned from Programming Over Time
Skimmed through chapters 9, 10, 24 and 25. I already know these topics, did research and even wrote literature on it.
Sep 12, 2024 03:36PM Add a comment
Software Engineering at Google: Lessons Learned from Programming Over Time

Dayton Outar
Dayton Outar is 33% done with Modern Control Engineering
Chapter 6 - "Control Systems Analysis and Design by the Root-Locus Method"
Sep 11, 2024 04:46AM Add a comment
Modern Control Engineering

Dayton Outar
Dayton Outar is 20% done with Modern Control Engineering
Skimmed onto Chapter 5. I get the idea. Just that thing about shifting into state space model from page 74
Sep 10, 2024 04:25AM Add a comment
Modern Control Engineering

« previous 1 3 4 5 6 7 8 9 51 52
Follow Dayton's updates via RSS