Help
RSS
API
Feed
Maltego
Contact
Domain > blog.mattblair.co
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2014-07-04
54.235.90.126
(
ClassC
)
2014-07-07
54.243.69.90
(
ClassC
)
2014-07-09
54.243.166.168
(
ClassC
)
2024-10-02
185.199.108.153
(
ClassC
)
Port 80
HTTP/1.1 200 OKConnection: keep-aliveContent-Length: 33671Server: GitHub.comContent-Type: text/html; charsetutf-8Last-Modified: Wed, 19 Jun 2024 18:30:50 GMTAccess-Control-Allow-Origin: *ETag: 667323da-8387expires: Wed, 02 Oct 2024 06:33:34 GMTCache-Control: max-age600x-proxy-cache: MISSX-GitHub-Request-Id: B003:356DC8:47357A:490DEC:66FCE6E6Accept-Ranges: bytesAge: 0Date: Wed, 02 Oct 2024 06:23:34 GMTVia: 1.1 varnishX-Served-By: cache-bfi-kbfi7400036-BFIX-Cache: MISSX-Cache-Hits: 0X-Timer: S1727850215.767163,VS0,VE97Vary: Accept-EncodingX-Fastly-Request-ID: 7906f58fa6ad434a2597f445e7e71e1aee3ad250 !doctype html>html langen> head> meta charsetutf-8>title>A Place for Poor Examples/title>meta namedescription contentI read that you learn more from a poor example than from a correct one. I don't believe this but that means my site will be a success.>meta nameviewport contentwidthdevice-width, initial-scale1.0>meta nametwitter:card contentsummary_large_image>meta propertyog:site_name contentA Place for Poor Examples>meta propertyog:title contentA Place for Poor Examples>meta propertyog:description contentI read that you learn more from a poor example than from a correct one. I don't believe this but that means my site will be a success.>meta propertyog:type contentwebsite>meta propertyog:url contenthttps://blog.mattblair.co/> meta propertyog:image contenthttps://blog.mattblair.co/img/headshot-4.png> link relmanifest href/favicon/site.webmanifest?v1> link relapple-touch-icon sizes180x180 href/favicon/apple-touch-icon.png?v1> link relicon typeimage/png sizes32x32 href/favicon/favicon-32x32.png?v1> link relicon typeimage/png sizes16x16 href/favicon/favicon-16x16.png?v1> link relmask-icon href/favicon/safari-pinned-tab.svg?v1 color#ffffff> link relshortcut icon href/favicon/favicon.ico?v1> meta namemsapplication-config content/favicon/browserconfig.xml?v1> meta namemsapplication-TileColor content#ffffff> meta nametheme-color content#ffffff> meta namegenerator contentHugo 0.118.2> link relstylesheet href/css/bundle.min.5233f2a4cd515395301b4154f6c1c621695e8cf53faa0935b76ac52fed7f4585.css integritysha256-UjPypM1RU5UwG0FU9sHGIWlejPU/qgk1t2rFL+1/RYU>link relstylesheet href/css/add-on.css>/head> body> header idsite-header> nav idsite-nav> h1 classnav-title> a href/ classnav> A Place for Poor Examples /a> /h1> menu idsite-nav-menu classflyout-menu menu> a href/ classnav link>i classfa fa-home>/i> Home/a> a href/about/ classnav link>i classfar fa-id-card>/i> About/a> a href/blog/ classnav link>i classfar fa-newspaper>/i> Blog/a> a href/categories/ classnav link>i classfas fa-sitemap>/i> Categories/a> a href/tags/ classnav link>i classfas fa-tag>/i> Tags/a> a href#share-menu classnav link share-toggle>i classfas fa-share-alt> /i>Share/a> a href#search-input classnav link search-toggle>i classfas fa-search> /i>Search/a> /menu> a href#search-input classnav search-toggle>i classfas fa-search fa-2x> /i>/a> a href#share-menu classnav share-toggle>i classfas fa-share-alt fa-2x> /i>/a> a href#lang-menu classnav lang-toggle langen>en/a> a href#site-nav classnav nav-toggle>i classfas fa-bars fa-2x>/i>/a> /nav> menu idsearch classmenu>input idsearch-input classsearch-input menu>/input>div idsearch-results classsearch-results menu>/div>/menu> menu idlang-menu classflyout-menu menu> a href# langen classnav link active>English (en)/a> a hrefhttps://blog.mattblair.co/fr/ langfr classnav link>Français (fr)/a> a hrefhttps://blog.mattblair.co/pl/ langpl classnav link>Polski (pl)/a> a hrefhttps://blog.mattblair.co/pt/ langpt classnav link>Português (pt)/a> a hrefhttps://blog.mattblair.co/de/ langde classnav link>Deutsche (de)/a> a hrefhttps://blog.mattblair.co/es/ langes classnav link>Española (es)/a> a hrefhttps://blog.mattblair.co/zh-cn/ langzh-cn classnav link>中文 (zh-cn)/a> a hrefhttps://blog.mattblair.co/zh-tw/ langzh-tw classnav link>中文 (zh-tw)/a> a hrefhttps://blog.mattblair.co/ja/ langja classnav link>日本語 (ja)/a> a hrefhttps://blog.mattblair.co/nl/ langnl classnav link>Nederlands (nl)/a> /menu> menu idshare-menu classflyout-menu menu> h1>Share Post/h1> a href//twitter.com/share?textA%20Place%20for%20Poor%20Examples&urlhttps%3a%2f%2fblog.mattblair.co%2f target_blank relnoopener classnav share-btn twitter> p>Twitter/p> /a> a href//www.facebook.com/sharer/sharer.php?uhttps%3a%2f%2fblog.mattblair.co%2f target_blank relnoopener classnav share-btn facebook> p>Facebook/p> /a> a href//www.reddit.com/submit?urlhttps%3a%2f%2fblog.mattblair.co%2f&titleA%20Place%20for%20Poor%20Examples target_blank relnoopener classnav share-btn reddit> p>Reddit/p> /a> a href//www.linkedin.com/shareArticle?urlhttps%3a%2f%2fblog.mattblair.co%2f&titleA%20Place%20for%20Poor%20Examples target_blank relnoopener classnav share-btn linkedin> p>LinkedIn/p> /a> a href//www.pinterest.com/pin/create/button/?urlhttps%3a%2f%2fblog.mattblair.co%2f&descriptionA%20Place%20for%20Poor%20Examples target_blank relnoopener classnav share-btn pinterest> p>Pinterest/p> /a> a hrefmailto:?subjectCheck%20out%20this%20post%20by %7b%20%20%20%20%20%20%20%20map%5b%5d%7d&bodyhttps%3a%2f%2fblog.mattblair.co%2f target_blank classnav share-btn email data-proofer-ignore> p>Email/p> /a> /menu> /header> div idwrapper> section idsite-intro > a href/>img src/img/headshot-4.png classcircle width100 altMatt Blair />/a> header> h1>Matt Blair/h1> /header> main> p>I read that you learn more from a poor example than from a correct one. I dont believe this but that means my site will be a success./p> /main> footer> ul classsocnet-icons> li>a href/index.xml typeapplication/rss+xml target_blank titleRSS classfas fa-rss>/a>/li> li>a href//github.com/duereg target_blank relnoopener titleGitHub classfab fa-github>/a>/li>li>a href//www.linkedin.com/in/mattblair target_blank relnoopener titleLinkedIn classfab fa-linkedin>/a>/li> /ul> /footer> /section> main idsite-main> article classpost> header> div classtitle> h2>a href/blog/20240619-build-vs-buy/>Build vs. Buy/a>/h2> p>A Debate around Feature Flags/p> /div> div classmeta> time datetime2024-06-19 10:00:00 -0800 -0800>June 19, 2024/time> p>3-Minute Read/p> /div>/header> div classcontent> p>In the software development world, teams often face the dilemma of whether to build a tool in-house or purchase an existing solution. This “build vs. buy” debate can significantly impact a company’s efficiency, budget, and focus. A quintessential example of this debate is the implementation of feature flags./p> /div> footer> a href/blog/20240619-build-vs-buy/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/refactoring/>refactoring/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/refactoring/>Refactoring/a>/li> li>a classarticle-terms-link href/tags/build-vs-buy/>Build vs Buy/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20240414-establishing-1-1s-that-work/>Establishing 1-1s that work/a>/h2> p>My lessons learned/p> /div> div classmeta> time datetime2024-04-14 11:52:59 -0800 -0800>April 14, 2024/time> p>4-Minute Read/p> /div>/header> div classcontent> p>The primary purpose of one-on-one meetings is to give your reports a chance to discuss issues and topics that they find important. It’s an opportunity for them to bring up concerns, challenges, and ideas that might not surface during regular team meetings. This is not a meeting to get status updates on projects! Schedule other time for that./p> /div> footer> a href/blog/20240414-establishing-1-1s-that-work/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/direct-reports/>direct reports/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/direct-reports/>Direct Reports/a>/li> li>a classarticle-terms-link href/tags/1-1/>1-1/a>/li> li>a classarticle-terms-link href/tags/11/>1:1/a>/li> li>a classarticle-terms-link href/tags/one-on-one/>one on one/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20240305-refactoring-a-legacy-codebase/>Refactoring a Legacy Codebase/a>/h2> p>A Step-by-Step Approach - Immediate, Short, Medium, Long Term changes/p> /div> div classmeta> time datetime2024-03-05 11:52:59 -0800 PST>March 5, 2024/time> p>3-Minute Read/p> /div>/header> div classcontent> p>In my current role, I inherited an older codebase where best practices were often overlooked. As I reviewed the code and the surrounding processes, I found numerous areas for improvement in both code quality and operational practices./p> /div> footer> a href/blog/20240305-refactoring-a-legacy-codebase/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/refactoring/>refactoring/a>/li> li>a classarticle-terms-link href/categories/legacy-code/>legacy code/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/refactoring/>Refactoring/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20231206-early-team-hiring/>Hiring for an Early-Stage Team/a>/h2> p>How to build a foundational team/p> /div> div classmeta> time datetime2023-12-06 11:41:58 -0800 PST>December 6, 2023/time> p>4-Minute Read/p> /div>/header> div classcontent> p>These are some notes I took from a hiring event I attended. I hope they help someone in the future (even if that someone is me)./p> /div> footer> a href/blog/20231206-early-team-hiring/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/hiring/>hiring/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/hiring/>Hiring/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230907-can-reports/>Decoding the Origins of CAN Reports/a>/h2> p>A SitRep in three parts/p> /div> div classmeta> time datetime2023-09-07 15:22:57 -0800 -0800>September 7, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>In the realm of incident management, accurate and swift communication is vital. Different organizations adopt various strategies to ensure efficient communication during emergencies. One such strategy that has been gaining traction is the utilization of CAN reports, a mnemonic that stands for “Conditions, Actions, Needs.” Let us delve deeper into the intricacies and origins of this unique reporting format./p> /div> footer> a href/blog/20230907-can-reports/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/sitrep/>SitRep/a>/li> li>a classarticle-terms-link href/categories/can/>CAN/a>/li> li>a classarticle-terms-link href/categories/tech-debt/>Tech Debt/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/incident-management/>Incident Management/a>/li> li>a classarticle-terms-link href/tags/technical-improvements/>Technical Improvements/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230508-tech-improvement-roadmap/>Strategic Approaches for Technical Improvement/a>/h2> /div> div classmeta> time datetime2023-05-07 12:19:57 -0800 -0800>May 7, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>Technical debt is a common challenge faced by engineering teams, requiring deliberate efforts to manage and pay it down. In this blog post, we will explore different approaches to tackling technical debt and building a long-term technical strategy. We will also highlight the importance of involving senior individual contributors (ICs) and engineering managers (EMs) in shaping the strategy, while considering the alignment with business and product goals./p> /div> footer> a href/blog/20230508-tech-improvement-roadmap/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/project/>Project/a>/li> li>a classarticle-terms-link href/categories/planning/>Planning/a>/li> li>a classarticle-terms-link href/categories/tech-debt/>Tech Debt/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/project/>Project/a>/li> li>a classarticle-terms-link href/tags/planning/>Planning/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/technical-excellence/>Technical Excellence/a>/li> li>a classarticle-terms-link href/tags/technical-improvements/>Technical Improvements/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230404-crunch-time/>Crunch Time/a>/h2> p>Approaches for Formalized Recovery Time/p> /div> div classmeta> time datetime2023-04-04 03:10:07 -0800 -0800>April 4, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>Crunch periods are a reality in many industries, and sometimes they are necessary to meet an immovable deadline. However, working under high-pressure situations for an extended period can lead to burnout, and it’s essential to provide support for the team after the crunch is over. In this blog post, we will discuss different approaches for formalized recovery time after a crunch period./p> /div> footer> a href/blog/20230404-crunch-time/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/project/>Project/a>/li> li>a classarticle-terms-link href/categories/planning/>Planning/a>/li> li>a classarticle-terms-link href/categories/performance/>Performance/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/project/>Project/a>/li> li>a classarticle-terms-link href/tags/planning/>Planning/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/technical-excellence/>Technical Excellence/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230327-code-quality/>Improving Software Quality/a>/h2> p>Leading Metrics to Measure and Strategies to Implement/p> /div> div classmeta> time datetime2023-03-27 10:54:47 -0800 -0800>March 27, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>As a manager, you’re responsible for ensuring that the software your team creates is of the highest quality possible. This means reducing the number of bugs and improving code quality. But how do you measure these improvements? And what strategies can you implement to achieve them?/p> /div> footer> a href/blog/20230327-code-quality/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/code-quality/>Code Quality/a>/li> li>a classarticle-terms-link href/categories/quality/>Quality/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/code-quality/>Code Quality/a>/li> li>a classarticle-terms-link href/tags/quality/>Quality/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230302-changing-stacks/>Moving Between Tech Stacks/a>/h2> p>How difficult is it?/p> /div> div classmeta> time datetime2023-03-02 17:31:07 -0800 PST>March 2, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>When it comes to software engineering roles, experience in the tech stack you’re going to be working in is valuable but not specifically required. A good engineer can ramp up and learn new stacks. However, someone experienced in the tech stack can contribute quickly to key development initiatives, while also bringing outside experience using the stack./p> /div> footer> a href/blog/20230302-changing-stacks/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/project/>Project/a>/li> li>a classarticle-terms-link href/categories/planning/>Planning/a>/li> li>a classarticle-terms-link href/categories/performance/>Performance/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/project/>Project/a>/li> li>a classarticle-terms-link href/tags/planning/>Planning/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/technical-excellence/>Technical Excellence/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230221-technical-excellence/>Promoting Technical Excellence in your Organization/a>/h2> /div> div classmeta> time datetime2023-02-21 17:31:07 -0800 PST>February 21, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>I was speaking to a friend who works at a startup with a team of around 14 engineers. 80% of them are mid level engineers with 3-4 years of experience. They all work in product squads covering specific areas./p> /div> footer> a href/blog/20230221-technical-excellence/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/project/>Project/a>/li> li>a classarticle-terms-link href/categories/planning/>Planning/a>/li> li>a classarticle-terms-link href/categories/performance/>Performance/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/project/>Project/a>/li> li>a classarticle-terms-link href/tags/planning/>Planning/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/technical-excellence/>Technical Excellence/a>/li> /ul> /div> /footer>/article> div classpagination> a href/page/2/ classbutton right>span>Next Page/span>/a> /div> /main> section idsite-sidebar> section idrecent-posts> header> h1>Recent Posts/h1> /header> article classmini-post> header> h2>a href/blog/20240619-build-vs-buy/>Build vs. Buy/a>/h2> time classpublished datetime2024-06-19 10:00:00 -0800 -0800>June 19, 2024/time> /header> /article> article classmini-post> header> h2>a href/blog/20240414-establishing-1-1s-that-work/>Establishing 1-1s that work/a>/h2> time classpublished datetime2024-04-14 11:52:59 -0800 -0800>April 14, 2024/time> /header> /article> article classmini-post> header> h2>a href/blog/20240305-refactoring-a-legacy-codebase/>Refactoring a Legacy Codebase/a>/h2> time classpublished datetime2024-03-05 11:52:59 -0800 PST>March 5, 2024/time> /header> /article> footer> a href/blog/ classbutton>See More/a> /footer> /section> section idcategories> header> h1>a href/categories>Categories/a>/h1> /header> ul> li> a href/categories/engineering/>engineeringspan classcount>69/span>/a> li> a href/categories/technical/>technicalspan classcount>69/span>/a> li> a href/categories/javascript/>javascriptspan classcount>55/span>/a> li> a href/categories/management/>managementspan classcount>36/span>/a> li> a href/categories/development/>developmentspan classcount>31/span>/a> li> a href/categories/learning/>learningspan classcount>31/span>/a> li> a href/categories/performance/>performancespan classcount>14/span>/a> li> a href/categories/planning/>planningspan classcount>13/span>/a> li> a href/categories/project/>projectspan classcount>11/span>/a> li> a href/categories/growth/>growthspan classcount>10/span>/a> li> a href/categories/teaching/>teachingspan classcount>10/span>/a> li> a href/categories/classes/>classesspan classcount>9/span>/a> li> a href/categories/motivation/>motivationspan classcount>4/span>/a> li> a href/categories/training/>trainingspan classcount>4/span>/a> li> a href/categories/evaluation/>evaluationspan classcount>2/span>/a> li> a href/categories/refactoring/>refactoringspan classcount>2/span>/a> li> a href/categories/tech-debt/>tech-debtspan classcount>2/span>/a> li> a href/categories/wfh/>wfhspan classcount>2/span>/a> li> a href/categories/work-from-home/>work-from-homespan classcount>2/span>/a> li> a href/categories/agile/>agilespan classcount>1/span>/a> li> a href/categories/calendar/>calendarspan classcount>1/span>/a> li> a href/categories/can/>canspan classcount>1/span>/a> li> a href/categories/code-quality/>code-qualityspan classcount>1/span>/a> li> a href/categories/coffee/>coffeespan classcount>1/span>/a> li> a href/categories/direct-reports/>direct-reportsspan classcount>1/span>/a> li> a href/categories/git/>gitspan classcount>1/span>/a> li> a href/categories/hiring/>hiringspan classcount>1/span>/a> li> a href/categories/incident/>incidentspan classcount>1/span>/a> li> a href/categories/legacy-code/>legacy-codespan classcount>1/span>/a> li> a href/categories/links/>linksspan classcount>1/span>/a> li> a href/categories/quality/>qualityspan classcount>1/span>/a> li> a href/categories/scheduling/>schedulingspan classcount>1/span>/a> li> a href/categories/search/>searchspan classcount>1/span>/a> li> a href/categories/sitrep/>sitrepspan classcount>1/span>/a> /li> /ul> /section> section idmini-bio> header> h1>About/h1> /header> p>This theme was developed for Hugo./p> footer> a href/about classbutton>Learn More/a> /footer> /section> /section> footer idsite-footer> ul classsocnet-icons> li>a href/index.xml typeapplication/rss+xml target_blank titleRSS classfas fa-rss>/a>/li> li>a href//github.com/duereg target_blank relnoopener titleGitHub classfab fa-github>/a>/li>li>a href//www.linkedin.com/in/mattblair target_blank relnoopener titleLinkedIn classfab fa-linkedin>/a>/li> /ul> p classcopyright> © 2024 A Place for Poor Examples br> Theme: a hrefhttps://github.com/pacollins/hugo-future-imperfect-slim target_blank relnoopener>Hugo Future Imperfect Slim/a>br>A a hrefhttps://html5up.net/future-imperfect target_blank relnoopener>HTML5 UP port/a> | Powered by a hrefhttps://gohugo.io/ title0.118.2 target_blank relnoopener>Hugo/a> /p>/footer>a idback-to-top href# classfas fa-arrow-up fa-2x>/a> script src/js/highlight.js>/script> script>hljs.highlightAll();/script>script src/js/bundle.min.ad907ab88f4f7ed7618ae94d9b61dfb5dbda485c7da78031e5a32ef164d81dfb.js integritysha256-rZB6uI9PftdhiulNm2HftdvaSFx9p4Ax5aMu8WTYHfs>/script> script src/js/add-on.js>/script> /div> /body>/html>
Port 443
HTTP/1.1 200 OKConnection: keep-aliveContent-Length: 33671Server: GitHub.comContent-Type: text/html; charsetutf-8Last-Modified: Wed, 19 Jun 2024 18:30:50 GMTAccess-Control-Allow-Origin: *ETag: 667323da-8387expires: Wed, 02 Oct 2024 06:33:34 GMTCache-Control: max-age600x-proxy-cache: MISSX-GitHub-Request-Id: 9A4A:356DC8:47358C:490E01:66FCE6E6Accept-Ranges: bytesAge: 0Date: Wed, 02 Oct 2024 06:23:34 GMTVia: 1.1 varnishX-Served-By: cache-bfi-krnt7300100-BFIX-Cache: MISSX-Cache-Hits: 0X-Timer: S1727850215.916274,VS0,VE64Vary: Accept-EncodingX-Fastly-Request-ID: e7ab2c77e7a4e22268126e7091bf780806a59034 !doctype html>html langen> head> meta charsetutf-8>title>A Place for Poor Examples/title>meta namedescription contentI read that you learn more from a poor example than from a correct one. I don't believe this but that means my site will be a success.>meta nameviewport contentwidthdevice-width, initial-scale1.0>meta nametwitter:card contentsummary_large_image>meta propertyog:site_name contentA Place for Poor Examples>meta propertyog:title contentA Place for Poor Examples>meta propertyog:description contentI read that you learn more from a poor example than from a correct one. I don't believe this but that means my site will be a success.>meta propertyog:type contentwebsite>meta propertyog:url contenthttps://blog.mattblair.co/> meta propertyog:image contenthttps://blog.mattblair.co/img/headshot-4.png> link relmanifest href/favicon/site.webmanifest?v1> link relapple-touch-icon sizes180x180 href/favicon/apple-touch-icon.png?v1> link relicon typeimage/png sizes32x32 href/favicon/favicon-32x32.png?v1> link relicon typeimage/png sizes16x16 href/favicon/favicon-16x16.png?v1> link relmask-icon href/favicon/safari-pinned-tab.svg?v1 color#ffffff> link relshortcut icon href/favicon/favicon.ico?v1> meta namemsapplication-config content/favicon/browserconfig.xml?v1> meta namemsapplication-TileColor content#ffffff> meta nametheme-color content#ffffff> meta namegenerator contentHugo 0.118.2> link relstylesheet href/css/bundle.min.5233f2a4cd515395301b4154f6c1c621695e8cf53faa0935b76ac52fed7f4585.css integritysha256-UjPypM1RU5UwG0FU9sHGIWlejPU/qgk1t2rFL+1/RYU>link relstylesheet href/css/add-on.css>/head> body> header idsite-header> nav idsite-nav> h1 classnav-title> a href/ classnav> A Place for Poor Examples /a> /h1> menu idsite-nav-menu classflyout-menu menu> a href/ classnav link>i classfa fa-home>/i> Home/a> a href/about/ classnav link>i classfar fa-id-card>/i> About/a> a href/blog/ classnav link>i classfar fa-newspaper>/i> Blog/a> a href/categories/ classnav link>i classfas fa-sitemap>/i> Categories/a> a href/tags/ classnav link>i classfas fa-tag>/i> Tags/a> a href#share-menu classnav link share-toggle>i classfas fa-share-alt> /i>Share/a> a href#search-input classnav link search-toggle>i classfas fa-search> /i>Search/a> /menu> a href#search-input classnav search-toggle>i classfas fa-search fa-2x> /i>/a> a href#share-menu classnav share-toggle>i classfas fa-share-alt fa-2x> /i>/a> a href#lang-menu classnav lang-toggle langen>en/a> a href#site-nav classnav nav-toggle>i classfas fa-bars fa-2x>/i>/a> /nav> menu idsearch classmenu>input idsearch-input classsearch-input menu>/input>div idsearch-results classsearch-results menu>/div>/menu> menu idlang-menu classflyout-menu menu> a href# langen classnav link active>English (en)/a> a hrefhttps://blog.mattblair.co/fr/ langfr classnav link>Français (fr)/a> a hrefhttps://blog.mattblair.co/pl/ langpl classnav link>Polski (pl)/a> a hrefhttps://blog.mattblair.co/pt/ langpt classnav link>Português (pt)/a> a hrefhttps://blog.mattblair.co/de/ langde classnav link>Deutsche (de)/a> a hrefhttps://blog.mattblair.co/es/ langes classnav link>Española (es)/a> a hrefhttps://blog.mattblair.co/zh-cn/ langzh-cn classnav link>中文 (zh-cn)/a> a hrefhttps://blog.mattblair.co/zh-tw/ langzh-tw classnav link>中文 (zh-tw)/a> a hrefhttps://blog.mattblair.co/ja/ langja classnav link>日本語 (ja)/a> a hrefhttps://blog.mattblair.co/nl/ langnl classnav link>Nederlands (nl)/a> /menu> menu idshare-menu classflyout-menu menu> h1>Share Post/h1> a href//twitter.com/share?textA%20Place%20for%20Poor%20Examples&urlhttps%3a%2f%2fblog.mattblair.co%2f target_blank relnoopener classnav share-btn twitter> p>Twitter/p> /a> a href//www.facebook.com/sharer/sharer.php?uhttps%3a%2f%2fblog.mattblair.co%2f target_blank relnoopener classnav share-btn facebook> p>Facebook/p> /a> a href//www.reddit.com/submit?urlhttps%3a%2f%2fblog.mattblair.co%2f&titleA%20Place%20for%20Poor%20Examples target_blank relnoopener classnav share-btn reddit> p>Reddit/p> /a> a href//www.linkedin.com/shareArticle?urlhttps%3a%2f%2fblog.mattblair.co%2f&titleA%20Place%20for%20Poor%20Examples target_blank relnoopener classnav share-btn linkedin> p>LinkedIn/p> /a> a href//www.pinterest.com/pin/create/button/?urlhttps%3a%2f%2fblog.mattblair.co%2f&descriptionA%20Place%20for%20Poor%20Examples target_blank relnoopener classnav share-btn pinterest> p>Pinterest/p> /a> a hrefmailto:?subjectCheck%20out%20this%20post%20by %7b%20%20%20%20%20%20%20%20map%5b%5d%7d&bodyhttps%3a%2f%2fblog.mattblair.co%2f target_blank classnav share-btn email data-proofer-ignore> p>Email/p> /a> /menu> /header> div idwrapper> section idsite-intro > a href/>img src/img/headshot-4.png classcircle width100 altMatt Blair />/a> header> h1>Matt Blair/h1> /header> main> p>I read that you learn more from a poor example than from a correct one. I dont believe this but that means my site will be a success./p> /main> footer> ul classsocnet-icons> li>a href/index.xml typeapplication/rss+xml target_blank titleRSS classfas fa-rss>/a>/li> li>a href//github.com/duereg target_blank relnoopener titleGitHub classfab fa-github>/a>/li>li>a href//www.linkedin.com/in/mattblair target_blank relnoopener titleLinkedIn classfab fa-linkedin>/a>/li> /ul> /footer> /section> main idsite-main> article classpost> header> div classtitle> h2>a href/blog/20240619-build-vs-buy/>Build vs. Buy/a>/h2> p>A Debate around Feature Flags/p> /div> div classmeta> time datetime2024-06-19 10:00:00 -0800 -0800>June 19, 2024/time> p>3-Minute Read/p> /div>/header> div classcontent> p>In the software development world, teams often face the dilemma of whether to build a tool in-house or purchase an existing solution. This “build vs. buy” debate can significantly impact a company’s efficiency, budget, and focus. A quintessential example of this debate is the implementation of feature flags./p> /div> footer> a href/blog/20240619-build-vs-buy/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/refactoring/>refactoring/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/refactoring/>Refactoring/a>/li> li>a classarticle-terms-link href/tags/build-vs-buy/>Build vs Buy/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20240414-establishing-1-1s-that-work/>Establishing 1-1s that work/a>/h2> p>My lessons learned/p> /div> div classmeta> time datetime2024-04-14 11:52:59 -0800 -0800>April 14, 2024/time> p>4-Minute Read/p> /div>/header> div classcontent> p>The primary purpose of one-on-one meetings is to give your reports a chance to discuss issues and topics that they find important. It’s an opportunity for them to bring up concerns, challenges, and ideas that might not surface during regular team meetings. This is not a meeting to get status updates on projects! Schedule other time for that./p> /div> footer> a href/blog/20240414-establishing-1-1s-that-work/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/direct-reports/>direct reports/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/direct-reports/>Direct Reports/a>/li> li>a classarticle-terms-link href/tags/1-1/>1-1/a>/li> li>a classarticle-terms-link href/tags/11/>1:1/a>/li> li>a classarticle-terms-link href/tags/one-on-one/>one on one/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20240305-refactoring-a-legacy-codebase/>Refactoring a Legacy Codebase/a>/h2> p>A Step-by-Step Approach - Immediate, Short, Medium, Long Term changes/p> /div> div classmeta> time datetime2024-03-05 11:52:59 -0800 PST>March 5, 2024/time> p>3-Minute Read/p> /div>/header> div classcontent> p>In my current role, I inherited an older codebase where best practices were often overlooked. As I reviewed the code and the surrounding processes, I found numerous areas for improvement in both code quality and operational practices./p> /div> footer> a href/blog/20240305-refactoring-a-legacy-codebase/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/refactoring/>refactoring/a>/li> li>a classarticle-terms-link href/categories/legacy-code/>legacy code/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/refactoring/>Refactoring/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20231206-early-team-hiring/>Hiring for an Early-Stage Team/a>/h2> p>How to build a foundational team/p> /div> div classmeta> time datetime2023-12-06 11:41:58 -0800 PST>December 6, 2023/time> p>4-Minute Read/p> /div>/header> div classcontent> p>These are some notes I took from a hiring event I attended. I hope they help someone in the future (even if that someone is me)./p> /div> footer> a href/blog/20231206-early-team-hiring/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/hiring/>hiring/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/hiring/>Hiring/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230907-can-reports/>Decoding the Origins of CAN Reports/a>/h2> p>A SitRep in three parts/p> /div> div classmeta> time datetime2023-09-07 15:22:57 -0800 -0800>September 7, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>In the realm of incident management, accurate and swift communication is vital. Different organizations adopt various strategies to ensure efficient communication during emergencies. One such strategy that has been gaining traction is the utilization of CAN reports, a mnemonic that stands for “Conditions, Actions, Needs.” Let us delve deeper into the intricacies and origins of this unique reporting format./p> /div> footer> a href/blog/20230907-can-reports/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/sitrep/>SitRep/a>/li> li>a classarticle-terms-link href/categories/can/>CAN/a>/li> li>a classarticle-terms-link href/categories/tech-debt/>Tech Debt/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/incident-management/>Incident Management/a>/li> li>a classarticle-terms-link href/tags/technical-improvements/>Technical Improvements/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230508-tech-improvement-roadmap/>Strategic Approaches for Technical Improvement/a>/h2> /div> div classmeta> time datetime2023-05-07 12:19:57 -0800 -0800>May 7, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>Technical debt is a common challenge faced by engineering teams, requiring deliberate efforts to manage and pay it down. In this blog post, we will explore different approaches to tackling technical debt and building a long-term technical strategy. We will also highlight the importance of involving senior individual contributors (ICs) and engineering managers (EMs) in shaping the strategy, while considering the alignment with business and product goals./p> /div> footer> a href/blog/20230508-tech-improvement-roadmap/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/project/>Project/a>/li> li>a classarticle-terms-link href/categories/planning/>Planning/a>/li> li>a classarticle-terms-link href/categories/tech-debt/>Tech Debt/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/project/>Project/a>/li> li>a classarticle-terms-link href/tags/planning/>Planning/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/technical-excellence/>Technical Excellence/a>/li> li>a classarticle-terms-link href/tags/technical-improvements/>Technical Improvements/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230404-crunch-time/>Crunch Time/a>/h2> p>Approaches for Formalized Recovery Time/p> /div> div classmeta> time datetime2023-04-04 03:10:07 -0800 -0800>April 4, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>Crunch periods are a reality in many industries, and sometimes they are necessary to meet an immovable deadline. However, working under high-pressure situations for an extended period can lead to burnout, and it’s essential to provide support for the team after the crunch is over. In this blog post, we will discuss different approaches for formalized recovery time after a crunch period./p> /div> footer> a href/blog/20230404-crunch-time/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/project/>Project/a>/li> li>a classarticle-terms-link href/categories/planning/>Planning/a>/li> li>a classarticle-terms-link href/categories/performance/>Performance/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/project/>Project/a>/li> li>a classarticle-terms-link href/tags/planning/>Planning/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/technical-excellence/>Technical Excellence/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230327-code-quality/>Improving Software Quality/a>/h2> p>Leading Metrics to Measure and Strategies to Implement/p> /div> div classmeta> time datetime2023-03-27 10:54:47 -0800 -0800>March 27, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>As a manager, you’re responsible for ensuring that the software your team creates is of the highest quality possible. This means reducing the number of bugs and improving code quality. But how do you measure these improvements? And what strategies can you implement to achieve them?/p> /div> footer> a href/blog/20230327-code-quality/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/code-quality/>Code Quality/a>/li> li>a classarticle-terms-link href/categories/quality/>Quality/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/code-quality/>Code Quality/a>/li> li>a classarticle-terms-link href/tags/quality/>Quality/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230302-changing-stacks/>Moving Between Tech Stacks/a>/h2> p>How difficult is it?/p> /div> div classmeta> time datetime2023-03-02 17:31:07 -0800 PST>March 2, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>When it comes to software engineering roles, experience in the tech stack you’re going to be working in is valuable but not specifically required. A good engineer can ramp up and learn new stacks. However, someone experienced in the tech stack can contribute quickly to key development initiatives, while also bringing outside experience using the stack./p> /div> footer> a href/blog/20230302-changing-stacks/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/project/>Project/a>/li> li>a classarticle-terms-link href/categories/planning/>Planning/a>/li> li>a classarticle-terms-link href/categories/performance/>Performance/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/project/>Project/a>/li> li>a classarticle-terms-link href/tags/planning/>Planning/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/technical-excellence/>Technical Excellence/a>/li> /ul> /div> /footer>/article> article classpost> header> div classtitle> h2>a href/blog/20230221-technical-excellence/>Promoting Technical Excellence in your Organization/a>/h2> /div> div classmeta> time datetime2023-02-21 17:31:07 -0800 PST>February 21, 2023/time> p>3-Minute Read/p> /div>/header> div classcontent> p>I was speaking to a friend who works at a startup with a team of around 14 engineers. 80% of them are mid level engineers with 3-4 years of experience. They all work in product squads covering specific areas./p> /div> footer> a href/blog/20230221-technical-excellence/ classbutton big>Read More/a> div classstats> ul classcategories> li>a classarticle-terms-link href/categories/management/>management/a>/li> li>a classarticle-terms-link href/categories/learning/>learning/a>/li> li>a classarticle-terms-link href/categories/development/>development/a>/li> li>a classarticle-terms-link href/categories/project/>Project/a>/li> li>a classarticle-terms-link href/categories/planning/>Planning/a>/li> li>a classarticle-terms-link href/categories/performance/>Performance/a>/li> /ul> ul classtags> li>a classarticle-terms-link href/tags/engineering-management/>Engineering Management/a>/li> li>a classarticle-terms-link href/tags/management/>Management/a>/li> li>a classarticle-terms-link href/tags/project/>Project/a>/li> li>a classarticle-terms-link href/tags/planning/>Planning/a>/li> li>a classarticle-terms-link href/tags/tech-debt/>Tech Debt/a>/li> li>a classarticle-terms-link href/tags/technical-excellence/>Technical Excellence/a>/li> /ul> /div> /footer>/article> div classpagination> a href/page/2/ classbutton right>span>Next Page/span>/a> /div> /main> section idsite-sidebar> section idrecent-posts> header> h1>Recent Posts/h1> /header> article classmini-post> header> h2>a href/blog/20240619-build-vs-buy/>Build vs. Buy/a>/h2> time classpublished datetime2024-06-19 10:00:00 -0800 -0800>June 19, 2024/time> /header> /article> article classmini-post> header> h2>a href/blog/20240414-establishing-1-1s-that-work/>Establishing 1-1s that work/a>/h2> time classpublished datetime2024-04-14 11:52:59 -0800 -0800>April 14, 2024/time> /header> /article> article classmini-post> header> h2>a href/blog/20240305-refactoring-a-legacy-codebase/>Refactoring a Legacy Codebase/a>/h2> time classpublished datetime2024-03-05 11:52:59 -0800 PST>March 5, 2024/time> /header> /article> footer> a href/blog/ classbutton>See More/a> /footer> /section> section idcategories> header> h1>a href/categories>Categories/a>/h1> /header> ul> li> a href/categories/engineering/>engineeringspan classcount>69/span>/a> li> a href/categories/technical/>technicalspan classcount>69/span>/a> li> a href/categories/javascript/>javascriptspan classcount>55/span>/a> li> a href/categories/management/>managementspan classcount>36/span>/a> li> a href/categories/development/>developmentspan classcount>31/span>/a> li> a href/categories/learning/>learningspan classcount>31/span>/a> li> a href/categories/performance/>performancespan classcount>14/span>/a> li> a href/categories/planning/>planningspan classcount>13/span>/a> li> a href/categories/project/>projectspan classcount>11/span>/a> li> a href/categories/growth/>growthspan classcount>10/span>/a> li> a href/categories/teaching/>teachingspan classcount>10/span>/a> li> a href/categories/classes/>classesspan classcount>9/span>/a> li> a href/categories/motivation/>motivationspan classcount>4/span>/a> li> a href/categories/training/>trainingspan classcount>4/span>/a> li> a href/categories/evaluation/>evaluationspan classcount>2/span>/a> li> a href/categories/refactoring/>refactoringspan classcount>2/span>/a> li> a href/categories/tech-debt/>tech-debtspan classcount>2/span>/a> li> a href/categories/wfh/>wfhspan classcount>2/span>/a> li> a href/categories/work-from-home/>work-from-homespan classcount>2/span>/a> li> a href/categories/agile/>agilespan classcount>1/span>/a> li> a href/categories/calendar/>calendarspan classcount>1/span>/a> li> a href/categories/can/>canspan classcount>1/span>/a> li> a href/categories/code-quality/>code-qualityspan classcount>1/span>/a> li> a href/categories/coffee/>coffeespan classcount>1/span>/a> li> a href/categories/direct-reports/>direct-reportsspan classcount>1/span>/a> li> a href/categories/git/>gitspan classcount>1/span>/a> li> a href/categories/hiring/>hiringspan classcount>1/span>/a> li> a href/categories/incident/>incidentspan classcount>1/span>/a> li> a href/categories/legacy-code/>legacy-codespan classcount>1/span>/a> li> a href/categories/links/>linksspan classcount>1/span>/a> li> a href/categories/quality/>qualityspan classcount>1/span>/a> li> a href/categories/scheduling/>schedulingspan classcount>1/span>/a> li> a href/categories/search/>searchspan classcount>1/span>/a> li> a href/categories/sitrep/>sitrepspan classcount>1/span>/a> /li> /ul> /section> section idmini-bio> header> h1>About/h1> /header> p>This theme was developed for Hugo./p> footer> a href/about classbutton>Learn More/a> /footer> /section> /section> footer idsite-footer> ul classsocnet-icons> li>a href/index.xml typeapplication/rss+xml target_blank titleRSS classfas fa-rss>/a>/li> li>a href//github.com/duereg target_blank relnoopener titleGitHub classfab fa-github>/a>/li>li>a href//www.linkedin.com/in/mattblair target_blank relnoopener titleLinkedIn classfab fa-linkedin>/a>/li> /ul> p classcopyright> © 2024 A Place for Poor Examples br> Theme: a hrefhttps://github.com/pacollins/hugo-future-imperfect-slim target_blank relnoopener>Hugo Future Imperfect Slim/a>br>A a hrefhttps://html5up.net/future-imperfect target_blank relnoopener>HTML5 UP port/a> | Powered by a hrefhttps://gohugo.io/ title0.118.2 target_blank relnoopener>Hugo/a> /p>/footer>a idback-to-top href# classfas fa-arrow-up fa-2x>/a> script src/js/highlight.js>/script> script>hljs.highlightAll();/script>script src/js/bundle.min.ad907ab88f4f7ed7618ae94d9b61dfb5dbda485c7da78031e5a32ef164d81dfb.js integritysha256-rZB6uI9PftdhiulNm2HftdvaSFx9p4Ax5aMu8WTYHfs>/script> script src/js/add-on.js>/script> /div> /body>/html>
View on OTX
|
View on ThreatMiner
Please enable JavaScript to view the
comments powered by Disqus.
Data with thanks to
AlienVault OTX
,
VirusTotal
,
Malwr
and
others
. [
Sitemap
]