Oddbean new post about | logout
 hahaha

fuck agile

the biggest problem in software dev is architects, people who know how to keep features down to a small enough size that the work can be stable at the prescribed deadline

at 3 years full time i started to get a bit of a grasp on architecture and i feel like i can pretty much be given a job description now, and within a couple of days tell you how long it will take, how many people it will need, and what features probably will need more time

software architecture is like building architecture but different... instead of load bearing requirements and foundations and whatnot, we have feature counts, which have trees of features under them, and you have to elaborate them down to a certain depth to actually get the picture of how much is involved

people and time are the main resources, as distinct from materials and labor and equipment... in my recent work i have also discovered that it can slow things down a lot if it's not easy to coordinate people's days to each other, remote work is really hard to do if people aren't "excessively" chatty about what they are doing because you can only sync up progress and deal with problems if people TALK ABOUT THEM

anyhow

maybe some day soon i'll actually get to architect for something bigger with more people, but for now, just continuing to do my own thing and notice the features and time involved so i can use this info later and to help my own work in the meantime