Started reading “The Mythical Man Month”.
Although it is over 40 years old, concepts discussed in it still hold! Some might feel that it is dated from a “technology” perspective, but its brilliant from a “philosophy of development” perspective.
There's also something humbling about reading how programming and software development was done 40 years ago when the tools we have today didn't exist. Makes me realize how lucky and privileged modern engineers like me are.
Some highlights from what I’ve read so far:
- Brooks' Law: Adding manpower to a late software project makes it later. This means that adding more people to a project that's already behind schedule will only make it more delayed due to the time required for communication and training.
- Concept of Surgical Team: Brooks suggests that software development should be approached like surgery, where a small team of experts work together to achieve a common goal. This is because small teams are easier to manage and communicate with than large teams.
- False assumption that underlies the scheduling of a development project: “All will go well”. While finalizing a schedule, one shouldn’t be overly optimistic that each task will take only as long as it “ought” to take
Running a LLM on your machine -
New Krazam video dropped!
IETF Celebrates The Standards [LIVE at Demuxed '22]
OMG!!! INSANE IETF ANNOUNCEMENT 2022!! we were invited to close out the Demuxed '22 conference as special guest speakers // recorded live at Bespoke in San Francisco on October 15, 2022 // Watch the other Demuxed 2022 talks: https://www.youtube.com/playlist?list=PLkyaYNWEKcOf98lZxnCcL6y7ZIVU3oSYO // More information on Demuxed: https://2022.demuxed.com/ // Thumbnail photo by Michael O'Donnell: https://www.shinyredphoto.com/ // https://instagram.com/krazam.tv // https://twitter.com/krazamtv