“Empty your mind, be formless. Shapeless, like water. If you put water into a cup, it becomes the cup. You put water into a bottle and it becomes the bottle. You put it in a teapot, it becomes the teapot. Now, water can flow or it can crash. Be water, my friend.”Bruce Lee
The “Mind is the key to relaxation. To relax the mind is to simply let go, and letting go of the body is relaxation. While relaxation is performed through the body, the basis for relaxation is the mind itself.” This is posted on the Chan Meditation Center website. It’s simple, we know we need to relax and we need to quiet our mind to do it.
I practice Chan meditation and not those guided meditations. I personally do not find them useful, someone talking in my ear when I am trying to quiet my brain. But I have come across a 15-minute guided meditation that teaches how to do empty mind.
I recommend this until you feel you have the technique and then venture to meditate without it.
Good luck and enjoy.
Enterprise Architecture helps an organization
realize its competitive advantage.
“The entire purpose of enterprise architecture frameworks is that they’re supposed to let you accurately and consistently describe architectures. If they can’t do that — if they can’t describe how SharePoint and your ERP suite fit together with everything else you’re running or will want to run — then what value do they provide?” Bob Lewis commented in his CIO magazine article, “The dark secrets of enterprise architecture.”
Bob Lewis continues with what he calls secrets, but they seem to be more opinions. Expressing that “One reason EA frameworks and methodologies fail so often is that they are, in the end, waterfall in nature.” Many of today’s frameworks did begin in the 1980s where software delivery was waterfall and the TOGAF architectural development method (ADM) at first glance may appear waterfall; however, the ADM process is a guide and TOGAF recommends leveraging the steps as they work best
for the organization. ADM is not an immutable process that an organization must follow exactly as documented.
The frameworks are not ‘broken.’ The difficulties that enterprise architecture (EA) is facing are not from the tools and methodologies, but with its alignment with the organization. Still seen as an IT role, enterprise architects are continually left out of key business strategy and planning sessions. The perception of the role needs to change.
Diann Daniel defines EA in her CIO Magazine Article, “The Rising Importance of the Enterprise Architect” as “the process of aligning a business’s strategic vision with its information technology. It connects different business units for synergistic communication and collaboration, creating a more seamless customer (or end-user) experience, “
One tool for this alignment is capability mapping; which provides a view of the enterprise that both business analysts, and IT architects could use to design current and future systems. It defines ‘what’ the business does, it does not try to explain the where, why, or how it is accomplished. It is not focused on architecting the solution as the article is trying to tell us, but aligning the organization and IT.
How to implement a systematic note-taking habit or process that effectively supports knowledge retention when I am reading. This is the question I continue to try and answer, as I imagine so many others do as well. Not a simple problem, but also not impossible, as we learn from Maria Popova (Brain Pickings) and Ryan Holiday.
Both Maria and Ryan have processes which allow them to gather and index information that will be available for them once they sit to write. Myself and many writers I know have the opposite experience. We read and retain some of the book, we kind of remember where we read something and spend too much time hunting it down again. Problem, of course, the ideas we had are lost as we search for the content we need.
Where did I see that story about … every writer has said at one time!
The ideas below work for both paper and digital, but my focus is on digital in this blog post. I think the paper process might be easier due to the one tool – the book – the digital requires more steps and organization.
Build an alternate Index
Maria Popova spoke with Tim Ferriss during a podcast. One topic was specific to how she read and researched the topics, how was she gathering and organizing all this information? She shared the process for building an alternate index. A new index for the book you are reading that stores not keywords but ideas and themes matches to the pages that store content that can be leveraged.
“it’s an index based not on keywords, but on ideas.”Maria Popova
How to do it
We begin by thinking about the themes or ideas that we want to retain information on. I found Maria’s Brain Pickings Bookshelf useful for understanding themes. Navigate the site and you can see an example of how she may breakdown the reading she is doing. For example, Science is top level, then click a book and you can see other themes on the left.
However, is science a theme or a keyword? If this is a theme then we want to understand the reason we are reading — what are we researching — and then we will see the book in a particular light. Let’s begin by creating the alternate index.
The process seems simple enough:
- Pick the page or grab a notebook that you can write in
- As you read the book mark anything that matches a theme you are working on, e.g. quotes, statements, tips and techniques.
- To mark, add the Theme/idea to the new index page and the page number.
Having a Process
From what I’ve read and what I am currently trying, there seems to be two sets of themes. One is global and found in everything I read and the other depends on the book.
I may find a list of common things like
- Statistics or facts
- Research or Read
- Content and information (to quote in writing)
It would also be useful to have a tag for each and when you are reading you can mark the text, so you remember why you market it in the future.
The dynamic list may be the sub-topics in the theme you are researching. For example, I read technology and currently my sub-topics are DevOps and CI/CD practices.
Action Index and Key Takeaways from the book
Todd Henry in his podcast speaks about creating a page where you can record your ideas, thoughts, and ponderings. I like this idea because I lose my thoughts when reading and then have to go back and reread to trigger the thoughts again, so basically they are continually lost, like a set of car keys!
I currently create index cards with the highlighted passages from the book. It takes hours to do this and I don’t think I get the same return from the process. In writing this post I also realized a quote from Robert Green.
“I read a book, very carefully, writing on the margins with all kinds of notes. A few weeks later I return to the book, and transfer my scribbles on to note cards, each card representing an important theme in the book.”Robert Greene
What caught my eye? “transfer my scribbles on to note cards” He is not rewriting the notes from the book, unless its a quote or passage he wants to reference I believe, but he is documenting his own thoughts from digesting the content.
This is why I believe the Thoughts/Pondering’s page will be some powerful.
How to do it
- On a new page, different than the new alternate index
- Title the section with something that matches the thoughts you are having now.
- Reference the page or chapter to reference again
- Write out your thoughts, ideas, learnings
Where to store this content?
I travel for work and digital is my first choice, so I can work anywhere. I also like to move between my Mac, phone, and ipad. My tool of choice right now is Evernote. I’ve been testing “bucket’s” from The Creative Habit by Twyla Tharp. I have a folder for each project in Evernote and I put everything in it. Notes, video’s, pictures, etc.. and when I am ready to work on the project, I have everything I need to begin.
Writing it Down
Finally we want to transfer the knowledge from the book somewhere we can use it when we start writing. There are two ideas:
- Create index cards that can be leveraged when writing
- Create the cards in Evernote or Scrivener where you can use them when writing or print them.
I hope this information has been useful. I will continue to update this page as I progress in my own research. Please add any useful links or ideas in the comments please.
You can read more about these processes here:
As a technical professional we are expected to keep up with the trends in our industry. The internet provides free access to several sources. The question, which resources are best for you?
Of course this is a short list! I will continue to add as I find things and please share anything useful in the comments.
In a recent ZDNet article, “DevOps may finally help deliver the software automation we’ve been waiting for,” Joe McKendrick has a conversation with Sacha Labourey from Cloudbees and it caught my attention, Sacha said:
“within larger organizations, “it’s just harder — size is in itself a factor of inertia,” he says. “Silos are much stronger.. so even if there is a mandate from the top down to change, it just takes a lot of energy and time to fight all of those headwinds.”Sacha Labourey from Cloudbees
Silo’s, politics, and legacy systems do make the transition difficult, but not impossible. Focus on breaking the habits and start small. Gene Kim, Jez humble, et al.. in “The DevOps Handbook,” asserts that:
an organization needs to create a dedicated transformation team. Make them accountable, provide clear goals, and allow them to work autonomous from the current organization. Demonstrate real value through the new processes.Jez humble
The goal is to move away from the ingrained habits and politics. If you cannot — you will fail!
Continuous Monitoring is not an afterthought; however, it is for most. Monitoring through each phase (concept to cash) provides transparency to how the systems is acting and reacting.
This transparency helps you troubleshoot issues and identify risks in the process and system. Get a baseline and look for bottlenecks or performance issues.
Work with your customers. the business owners, and understand their questions. Monitor to answer those questions and be a superstar.
The goal of CD is to be able to release software frequently,
and reliably, in a frictionless manner.
By Daniel Horton
“By now it should be clear that the only way to create value is to release. Testing your products against the marketplace is crucial for the agility of your organization,“ Don McGreal wrote in his book “The professional product owner.” An organization’s ability to release features to its customer base in a fast and reliable manner is a differentiator that we see in many industries. It is the difference between being the top company or the runner up.
Each client I meet has the same problem. They are inundated with manual processes, procedures, and habits that have built up over years. The statement “it’s just how we do it” is often used. However, these habits are the reason they cannot move forward. The focus is too much on the deliverable and less on the process of delivering. Thoughtworks Studios sums it up well in a white paper on agile release management.
“Many organizations have a release process that takes hours or days. Why is this so? The most common reason is that releasing new versions of software is predominantly a manual process that involves changes to many separate systems. Operating systems, infrastructure, and middleware must be configured, and their state verified.”
Manual processes increase the percentage of errors. Coordination becomes more difficult, and the correct procedures are normally not written down for teams to follow. Everything is done based on experience and memory. Additionally:
“Another major contributory factor to painful releases is poor collaboration between the people involved in delivering software. Developers, testers, DBAs, operations staff, and managers all need to work together from the beginning of every project to ensure its success. Instead, it is typical to see developers throwing work over the wall to testers, testers entering bugs into defect systems rather than working with developers to fix them, and the operations team trying to deploy software that is not production ready, and in many cases, hasn’t even been tested in a production- like environment.”
Many of these issues can be reduced and even eliminated with a clear focus on release management, automation, and communication. Start small and focus on a vertical slice that cuts through everything. Add metrics to show the benefits of your changes and your on the right path for success.
“I learned very early the difference between knowing
the name of something and knowing something.”
– Richard Feynman
Do you say “I read it in a book” or do you really know how it works? So many people learn the buzzwords and really don’t understand the underlying concepts. Which comes out when you start having a detailed conversation on the topic. I’ve had this happen and I feel embarrassed that I do not know enough and also frustrated because there is never enough time to learn everything. Then there is the fact that we only retain about 10% of what we read. According to the learning pyramid, from the NTL Institute for Applied Behavioral Science, we retain 10% from reading, 20% from audio/visual, 30% from demonstrations, and 90% from teaching others what we have learned.
The moral of the story – begin teaching others to become smarter! Seriously, you will retain more of what you learned if you prepare and hopefully teach others the techniques you’ve learned. It is called the Feynman Technique and it defines how to quickly learn pretty much anything. The concept breaks a topic down into its core and then explains it a 5 year old.
There are several variations on the web, but the technique may be defined as:
- Choose a Concept
- Explain it to a 5 year old
- Understand your knowledge gap
- Simplify as much as possible
- Use Analogies, stories, etc..
In the Real-World
The process really is straightforward. We want to write an explanation that is simple, not stupid and unintelligent, but simple, clear, and concise. Here are the steps:
- Get out a piece of paper (or word, etc.)
- At the top write the topic or subject you want to clarify and teach to another
- Begin explaining the topic in your writing on the paper.
- Use simple language
- Use Diagrams
- Use Analogies and stories
- Review the draft for lack of clarity or missing content.
- Go back and research
- Update the document and continue the loop reviewed in #3 above
- Final review is looking to see that we’ve obtained clarity.
- Look for any technical jargon, etc..
- Update the document to provide additional clarity
Another technique I recommend is recording yourself. With today’s technology you can easily record and review your progress. Check if you are clear and concise when teaching the topic or are you pausing, skipping, or just lost on the details? Do this until you are able to explain the topic clearly. The camera will help you with presentation skills as well.