Subj : Re: Software development book recommendation
To   : tenser
From : hollowone
Date : Mon Mar 17 2025 01:12 pm

 te> One of John Ousterhout's criticisms of Martin is that he doesn't
 te> balance his advice: he goes to an extreme, so far as to call
 te> comments failures, but doesn't discuss when they may be necessary.
 te> The advice is thus not usefully weighted in situations where
 te> things are ambiguous.

Well Ousterhout writes you shouldn't worry about error handling related to memory management. Computers today have enough ram to handle malloc just fine... :> which if read without careful consideration of the context is like... of fuck... come on John...

I could not also blindly agree with his exception handling tactics. Generally there are better ways to handle corner cases than raising exceptions anyway... 

Deep modules vs. shallow functions is huge it depends to me. 

but I really liked the strategic vs. tactical programming terminology.
It well describes AI aided programming today (so focused on task definition that it often forgets the system to be built... highly tactical), vs. human processed AI code at the end to ensure it never forgets about system architecture while realizing task formulated by a question or user story....

-h1

.... Xerox Alto was the thing. Anything after we use is just a mere copy.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

.