<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>books - Category - Charles Muchogo</title>
        <link>https://charles.muchogo.com/categories/books/</link>
        <description>books - Category - Charles Muchogo</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 18 Jun 2022 20:10:03 &#43;0300</lastBuildDate><atom:link href="https://charles.muchogo.com/categories/books/" rel="self" type="application/rss+xml" /><item>
    <title>Being an effective enginner</title>
    <link>https://charles.muchogo.com/posts/books/effective_engineer/review/</link>
    <pubDate>Sat, 18 Jun 2022 20:10:03 &#43;0300</pubDate>
    <author>Author</author>
    <guid>https://charles.muchogo.com/posts/books/effective_engineer/review/</guid>
    <description><![CDATA[Takeaways from The Effective Engineer by Edmond Lau]]></description>
</item><item>
    <title>Planning not to fail in software development</title>
    <link>https://charles.muchogo.com/posts/books/code_complete/three_four/</link>
    <pubDate>Sat, 26 Sep 2020 13:16:57 &#43;0300</pubDate>
    <author>Author</author>
    <guid>https://charles.muchogo.com/posts/books/code_complete/three_four/</guid>
    <description><![CDATA[As in building construction, the success or failure is mostly pre-determined during the preparation phase through processes such as blueprints, surveys, permits etc. This applies to software too and doing the most expensive part of a big project twice is not good, just like bringing down a skyscraper which is halfway done.
High quality practices in software engineering emphasize on quality at the beginning, middle and end of a project. This begs the question of what constitutes quality at the beginning?]]></description>
</item><item>
    <title>Software Development</title>
    <link>https://charles.muchogo.com/posts/books/code_complete/one_two/</link>
    <pubDate>Mon, 21 Sep 2020 12:13:29 &#43;0300</pubDate>
    <author>Author</author>
    <guid>https://charles.muchogo.com/posts/books/code_complete/one_two/</guid>
    <description><![CDATA[Generally, construction is the art of building something. Software, just as anything man made, is constructed through an activity commonly referred to as programming. The process/activity has a lifecycle in which an idea is developed into something useful and over the years a set of standard activities/processes have been developed.
At its core it involves: planning, detailed design, coding, debugging, integration, testing. Other processes include problem definition, high level design, requirements development and maintenance.]]></description>
</item></channel>
</rss>
