The only difference between an item and a sub-item is that a sub-item has a parent item. An item is defined as some amount of text that may also have one or more sub-items. Yeah, I recently gave Atwood’s three things concept a try and it did shine a clear light on the three things, but – fact – there are more than three big things to tackle each day.Īs data structures go, a text outline is simple. However, stuff has recently started falling through the cracks it’s not clear what belongs in Asana versus Field Notes versus my brain. This is an inefficient system that until recently has been creating just enough value to quiet the productivity rage. I remain in a troubling post-Things world where I’m using a bizarre combination of Asana, Field Notes, and my brain to keep track of the world. There’s tool in the domain of explanation and organization which I’m not certain is the domain of engineers, but serves the same purpose: outlines. I find this often a better means of explanation than sitting down how the code is organized and how it works. You can walk up to the white-board and clearly visually describe the part of the system that needs explanation. Sometimes… branches or decisions occur.Ī key aspect of a flow chart is that fact it is visual. When certain conditions exist, you can move to another state. This isn’t exactly correct – engineers think in code, but most of the planet does not, but, chances are, they understand the concept of a flowchart. One of the key tenets I talk about regarding understanding the engineering mindset is that software engineers think in terms of flow charts.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |