{"id":851,"date":"2014-11-11T00:46:21","date_gmt":"2014-11-10T22:46:21","guid":{"rendered":"http:\/\/blog.adrianbolboaca.ro\/?p=851"},"modified":"2020-01-15T19:55:13","modified_gmt":"2020-01-15T17:55:13","slug":"add-features-on-legacy-code","status":"publish","type":"post","link":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/","title":{"rendered":"Legacy Coderetreat: Part 5 &#8211; Add features on Legacy Code"},"content":{"rendered":"<h2>Add features on legacy code<\/h2>\n<h3>Blog post series<\/h3>\n<p>This blog post is part of a series about <a href=\"http:\/\/legacycoderetreat.typepad.com\/\">legacy coderetreat<\/a> and legacy code techniques you can apply during your work. Please click to see <a href=\"\/2014\/04\/legacy-coderetrea\/#sessions\">more sessions<\/a> about legacy code.<\/p>\n<h3>Purpose<\/h3>\n<p>When we need to add features in legacy code we need to make sure we understand it. But the feature needs to be added to an existing system. For that we need first of all to understand the current behaviour of the system. After that we need to make room for the change by refactoring the existing code. Of course we need a safety net before refactoring the existing system. Once we have room for the new feature we can alter the existing system. The main purposes of writing tests before adding the feature would be first of all to make sure we do not introduce defects and secondly to make sure we add the wanted feature. By having tests written for the new feature we can validate them with our product colleagues.<\/p>\n<p>During the next section you will find the steps to take in order to minimize the risk of introducing defect or adding the wrong feature to legacy code, what you would do at a legacy coderetreat.<\/p>\n<figure id=\"attachment_834\" aria-describedby=\"caption-attachment-834\" style=\"width: 640px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-834 size-full\" src=\"http:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2014\/05\/changer-game.jpg\" alt=\"Add features on legacy code\" width=\"640\" height=\"480\" srcset=\"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2014\/05\/changer-game.jpg 640w, https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2014\/05\/changer-game-300x225.jpg 300w\" sizes=\"(max-width: 640px) 100vw, 640px\" \/><figcaption id=\"caption-attachment-834\" class=\"wp-caption-text\">Add features on legacy code<\/figcaption><\/figure>\n<h3><!--more-->Concept<\/h3>\n<p>Below there are some steps you can take in order to minimize the risk when adding a feature to legacy code. These steps respect the <a href=\"\/2013\/03\/taking-baby-steps\/\">Baby Steps<\/a> concept that minimize the risks of adding defects through small changes that can be understood by our minds and can be remembered easily.<\/p>\n<p>The main things we should care about when adding a feature to legacy code would be:<\/p>\n<ul>\n<li>Add the good feature<\/li>\n<li>Do not introduce a defect<\/li>\n<li>Finish adding the feature in a timely manner<\/li>\n<\/ul>\n<p><strong>Important: commit after each step to a local source control<\/strong><\/p>\n<p>Why would you want to commit so often? Well you are working with a system that could be very hard to change and very hard to understand. Mistakes can come out from any small change. You want to have a very easy to use undo button with all the changes. You would not like to be in the situation where some tests stop passing and you do not know what you did. Always when something is wrong, you can undo and continue from a clear state. This is a kind of backtracking in a graph of possible decisions maze.<\/p>\n<p><strong>Steps<\/strong><\/p>\n<ol>\n<li><strong>Build a Safety Net<\/strong><br \/>\nWe first need to understand if the described behaviour is a bug or not. For that we can write some characterization tests in order to understand what the system really does. The simplest form of characterization test is a system test. A couple of ideas to start writing the characterization tests are to use the generic approach <a href=\"\/2014\/04\/from-nothing-to-system-tests\/\">From Nothing to System Tests<\/a> or <a href=\"\/2014\/05\/legacy-coderetreat-golden-master\/\">the Golden Master technique<\/a>. We can generate system tests considering that the System Under Test (SUT) is a black box. You can find more details about how to do that in the blog posts and code casts about the above techniques.<br \/>\nDo not change the existing code. Just add the tests and let them run as fast as possible.<\/li>\n<li><strong>Add unit or component tests<\/strong><br \/>\nWe need to add unit tests or component tests around the area that needs to be changed in order to introduce the new feature. This process will show how flexible the current design is.<br \/>\nWith these tests we have a better type of test coverage, because even if we had covered all the code paths with the integrated tests at step 1, we might have forgotten some areas. And it is extremely difficult not to forget something in the process.<br \/>\nThese tests are faster and give us faster feedback than the integrated tests we wrote at step 1.<br \/>\nChange the existing code just as little as possible so that the unit tests can be written.<\/li>\n<li><strong>Make room for new feature with refactoring<\/strong><br \/>\nNow we have two safety nets, one coarse represented by the integrated tests at step 1, and another one which is softer and represented by the unit or component tests at step 2.<br \/>\nWe can use these safety nets to do smart refactoring. Sometimes we just need to improve the names and that&#8217;s all. In other cases we need to extract an interface and apply Dependency Inversion Principle. Or we need to do massive refactorings in order to create a more complicated integration layer with the new feature.<br \/>\nFor any integration layer, very simple, basic or very complicated, we need to clearly define the contract of collaboration between the systems. For all the integration layer some tests would be extremely useful and will help during the next step, of adding a feature.<br \/>\nCareful! Do not refactor too much; you need to refactor the minimum necessary to let the new feature be plugged in.<\/li>\n<li><strong>Add features on legacy code<\/strong><br \/>\nMake sure you can&nbsp;add features on legacy code in a timely manner. It is essential for the business to be able to add features on legacy code fast enough so it makes a difference.<br \/>\nIdeally test-drive the feature. If not at least write tests after you added the feature and make sure you have a good test coverage.<br \/>\nRun often the unit tests and the tests on the integration layer with the new system. At the end, when the feature was added, make sure to run all the automated tests you have.<\/li>\n<li><strong>Test Manually<\/strong><br \/>\nEach time you added a feature, do not rely only on automated tests. At least check the application in a minimal way, or even better, apply a good test plan.<\/li>\n<li><strong>Refactor, clean-up<\/strong><br \/>\nOnce everything works, we can improve the system with things like:<br \/>\n&#8211; having better names<br \/>\n&#8211; splitting better the responsibilities of the structures<br \/>\n&#8211; making automated tests more expressive<br \/>\n&#8211; refactoring integrated tests into integration tests and unit or component tests<br \/>\n&#8211; a lot of other things&#8230;<\/li>\n<\/ol>\n<p><strong>Remember: commit after each step to a local source control<\/strong><\/p>\n<h3>Outcomes<\/h3>\n<p>As with legacy code we do not always understand what is the needed feature or if we do understand, we might not know how we could change the code to accommodate the change, we can use this technique to have more certainty during the process. After this session you will understand how you can&nbsp;add features on legacy code, a code you do now know.<\/p>\n<p>You can use this technique whenever you want to increase your confidence when working with existing code. By <a href=\"\/2013\/03\/taking-baby-steps\/\">Taking Baby Steps<\/a> you can minimize the risks of introducing defects and maximize your chances to introduce the needed feature.<\/p>\n<h3>Remarks<\/h3>\n<p>These techniques are not simple to apply. For each of the steps we need to take a lot of care.<br \/>\nFor step 2 it always depends on the context if one can add unit tests or component tests.<br \/>\nFor step 3 it is always risky to not introduce defects, even if you have some safety nets put in place. Always do small steps and use the IDE for automated refactorings.<br \/>\nFor step 4 the main difficulty is to&nbsp;add features on legacy code fast and to test-drive it. We want to increase the test coverage of a legacy system, and what better way to do that than by covering<\/p>\n<h3>History<\/h3>\n<p>I use this technique whenever I need to add a feature on existing code. I thought about these steps in order to bring me confidence that I am on the good path and I will not introduce defects.<\/p>\n<p>This session is usually part of my facilitation of a Legacy Coderetreat.<\/p>\n<h3>Code Cast<\/h3>\n<p>Please find <a href=\"\/2015\/03\/episode-4-add-feature-on-legacy-code\/\">here<\/a> a code cast in Java about this session<\/p>\n<p>&nbsp;<\/p>\n<p>Feel free to <a href=\"contact\/\">contact me<\/a> to find more about how to add features on legacy code.<\/p>\n<p><em>Image credit: http:\/\/pixabay.com\/static\/uploads\/photo\/2014\/02\/05\/15\/04\/game-259109_640.jpg<\/em><\/p>\n<a target=\"_blank\" href=\"https:\/\/drpeterscode.com\/bad-bot-exterminator-protects-wordpress-sites-from-hackers-cyber-ddos-dos-attacks.php\"><img src=\"https:\/\/blog.adrianbolboaca.ro\/wp-content\/plugins\/dpabottomofpostpage\/apixel1x1.jpg\" ><\/a><table><\/table>","protected":false},"excerpt":{"rendered":"<p>Add features on legacy code Blog post series This blog post is part of a series about legacy coderetreat and legacy code techniques you can apply during your work. Please&hellip; <\/p>\n","protected":false},"author":3,"featured_media":2471,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[61,347],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.0 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Add features on legacy code, coderetreat Adrian Bolboaca<\/title>\n<meta name=\"description\" content=\"Find how you can add features on legacy code by using the legacy coderetreat codebase. Ask about facilitating a legacy coderetreat.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Add features on legacy code, coderetreat Adrian Bolboaca\" \/>\n<meta property=\"og:description\" content=\"Find how you can add features on legacy code by using the legacy coderetreat codebase. Ask about facilitating a legacy coderetreat.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/\" \/>\n<meta property=\"og:site_name\" content=\"Adrian Bolboaca\" \/>\n<meta property=\"article:published_time\" content=\"2014-11-10T22:46:21+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-01-15T17:55:13+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2014\/11\/legacy-code-part-5-1024x576.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"576\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Adrian Bolboaca\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Adrian Bolboaca\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/\"},\"author\":{\"name\":\"Adrian Bolboaca\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76\"},\"headline\":\"Legacy Coderetreat: Part 5 &#8211; Add features on Legacy Code\",\"datePublished\":\"2014-11-10T22:46:21+00:00\",\"dateModified\":\"2020-01-15T17:55:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/\"},\"wordCount\":1319,\"commentCount\":1,\"publisher\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76\"},\"articleSection\":[\"Legacy code\",\"Legacy Code Post\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/\",\"url\":\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/\",\"name\":\"Add features on legacy code, coderetreat Adrian Bolboaca\",\"isPartOf\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#website\"},\"datePublished\":\"2014-11-10T22:46:21+00:00\",\"dateModified\":\"2020-01-15T17:55:13+00:00\",\"description\":\"Find how you can add features on legacy code by using the legacy coderetreat codebase. Ask about facilitating a legacy coderetreat.\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.adrianbolboaca.ro\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Legacy Coderetreat: Part 5 &#8211; Add features on Legacy Code\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#website\",\"url\":\"https:\/\/blog.adrianbolboaca.ro\/\",\"name\":\"Adrian Bolboaca\",\"description\":\"Programmer, Trainer, Coach\",\"publisher\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.adrianbolboaca.ro\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76\",\"name\":\"Adrian Bolboaca\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2019\/11\/Adi-300x400.jpg\",\"contentUrl\":\"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2019\/11\/Adi-300x400.jpg\",\"width\":300,\"height\":400,\"caption\":\"Adrian Bolboaca\"},\"logo\":{\"@id\":\"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/image\/\"},\"description\":\"Adrian was involved in developing software for domains like energy, ecommerce, banking, customs and ERP\/CRM. He has been working with companies from Netherlands, Romania, Italy, France and Germany, and he is knowledgeable in software technical domains like: clean code, unit testing, test driven development, simple design, emergent design, working effectively with legacy code. As a continuous learner and challenger of existing ideas and concepts, Adrian is a supporter of movements that give new ideas on how to continuously improve software and that embrace the values of software quality and efficiency. He facilitated many code retreats in Romania, Belgium, France, Germany, Netherlands, Finland, Bulgaria and has a keen interest in serious games and using gamestorming for continuous improvement. He is fluent in Romanian, English and French, but when it comes to programming languages he supports language agnosticism, since he strongly believes that a programming language is only a tool towards higher level software concepts. As a constant participant to conferences and workshops, he is recognized for challenging ideas and getting people out of their comfort zone, not out of disrespect or lack of reverence for his peers, but out of his desire to show people that there are always things to learn. \u201cI try to be a continuous learner and a continuous teacher, because I think good software comes from the skills of the people that are involved in the process, on each and every level. Whenever I write code I focus on reducing domain complexity to obtain maintainable software. I love to develop software that helps companies to improve their business, to implement solutions that improve their internal processes and to motivate teams to use their capabilities to yet another level.\u201d Adrian works as a technical and organizational trainer and coach at Mozaic Works.\",\"sameAs\":[\"http:\/\/blog.adrianbolboaca.ro\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Add features on legacy code, coderetreat Adrian Bolboaca","description":"Find how you can add features on legacy code by using the legacy coderetreat codebase. Ask about facilitating a legacy coderetreat.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/","og_locale":"en_US","og_type":"article","og_title":"Add features on legacy code, coderetreat Adrian Bolboaca","og_description":"Find how you can add features on legacy code by using the legacy coderetreat codebase. Ask about facilitating a legacy coderetreat.","og_url":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/","og_site_name":"Adrian Bolboaca","article_published_time":"2014-11-10T22:46:21+00:00","article_modified_time":"2020-01-15T17:55:13+00:00","og_image":[{"width":1024,"height":576,"url":"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2014\/11\/legacy-code-part-5-1024x576.png","type":"image\/png"}],"author":"Adrian Bolboaca","twitter_misc":{"Written by":"Adrian Bolboaca","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/#article","isPartOf":{"@id":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/"},"author":{"name":"Adrian Bolboaca","@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76"},"headline":"Legacy Coderetreat: Part 5 &#8211; Add features on Legacy Code","datePublished":"2014-11-10T22:46:21+00:00","dateModified":"2020-01-15T17:55:13+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/"},"wordCount":1319,"commentCount":1,"publisher":{"@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76"},"articleSection":["Legacy code","Legacy Code Post"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/","url":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/","name":"Add features on legacy code, coderetreat Adrian Bolboaca","isPartOf":{"@id":"https:\/\/blog.adrianbolboaca.ro\/#website"},"datePublished":"2014-11-10T22:46:21+00:00","dateModified":"2020-01-15T17:55:13+00:00","description":"Find how you can add features on legacy code by using the legacy coderetreat codebase. Ask about facilitating a legacy coderetreat.","breadcrumb":{"@id":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.adrianbolboaca.ro\/2014\/11\/add-features-on-legacy-code\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.adrianbolboaca.ro\/"},{"@type":"ListItem","position":2,"name":"Legacy Coderetreat: Part 5 &#8211; Add features on Legacy Code"}]},{"@type":"WebSite","@id":"https:\/\/blog.adrianbolboaca.ro\/#website","url":"https:\/\/blog.adrianbolboaca.ro\/","name":"Adrian Bolboaca","description":"Programmer, Trainer, Coach","publisher":{"@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.adrianbolboaca.ro\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/9894e1b2a4241be86991388625407d76","name":"Adrian Bolboaca","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/image\/","url":"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2019\/11\/Adi-300x400.jpg","contentUrl":"https:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2019\/11\/Adi-300x400.jpg","width":300,"height":400,"caption":"Adrian Bolboaca"},"logo":{"@id":"https:\/\/blog.adrianbolboaca.ro\/#\/schema\/person\/image\/"},"description":"Adrian was involved in developing software for domains like energy, ecommerce, banking, customs and ERP\/CRM. He has been working with companies from Netherlands, Romania, Italy, France and Germany, and he is knowledgeable in software technical domains like: clean code, unit testing, test driven development, simple design, emergent design, working effectively with legacy code. As a continuous learner and challenger of existing ideas and concepts, Adrian is a supporter of movements that give new ideas on how to continuously improve software and that embrace the values of software quality and efficiency. He facilitated many code retreats in Romania, Belgium, France, Germany, Netherlands, Finland, Bulgaria and has a keen interest in serious games and using gamestorming for continuous improvement. He is fluent in Romanian, English and French, but when it comes to programming languages he supports language agnosticism, since he strongly believes that a programming language is only a tool towards higher level software concepts. As a constant participant to conferences and workshops, he is recognized for challenging ideas and getting people out of their comfort zone, not out of disrespect or lack of reverence for his peers, but out of his desire to show people that there are always things to learn. \u201cI try to be a continuous learner and a continuous teacher, because I think good software comes from the skills of the people that are involved in the process, on each and every level. Whenever I write code I focus on reducing domain complexity to obtain maintainable software. I love to develop software that helps companies to improve their business, to implement solutions that improve their internal processes and to motivate teams to use their capabilities to yet another level.\u201d Adrian works as a technical and organizational trainer and coach at Mozaic Works.","sameAs":["http:\/\/blog.adrianbolboaca.ro"]}]}},"_links":{"self":[{"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/posts\/851"}],"collection":[{"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/comments?post=851"}],"version-history":[{"count":0,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/posts\/851\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/media\/2471"}],"wp:attachment":[{"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/media?parent=851"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/categories?post=851"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.adrianbolboaca.ro\/wp-json\/wp\/v2\/tags?post=851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}