{"id":8174,"date":"2022-07-22T22:12:23","date_gmt":"2022-07-22T22:12:23","guid":{"rendered":"https:\/\/www.hexacorn.com\/blog\/?p=8174"},"modified":"2022-07-22T22:30:14","modified_gmt":"2022-07-22T22:30:14","slug":"the-curse-of-being-technical","status":"publish","type":"post","link":"https:\/\/www.hexacorn.com\/blog\/2022\/07\/22\/the-curse-of-being-technical\/","title":{"rendered":"The curse of being &#8216;technical&#8217;"},"content":{"rendered":"\n<p>You are either technical, or you are not.<\/p>\n\n\n\n<p>What does it mean?<\/p>\n\n\n\n<p>Many tried to answer that borderline philosophical question, but as far as I know no one is really able to pin it down to specifics. This is because it&#8217;s one of these things where &#8216;you know it when you see it&#8217;. The depth of our knowledge about different subjects varies and there is absolutely not a single list, or ultimate criteria that can be applied to tag someone as &#8216;technical&#8217; or &#8216;non-technical&#8217;.<\/p>\n\n\n\n<p>Where does it leave us?<\/p>\n\n\n\n<p>You are either technical, or you are not.<\/p>\n\n\n\n<p>What does it mean?<\/p>\n\n\n\n<p>For every aspect of infosec there exist a practitioner layer, often manifesting itself by an individual&#8217;s capability to deliver. You can master this level and still not be &#8216;technical&#8217;. Because being &#8216;technical&#8217; means being fluent on this practitioner layer, plus more. For example:<\/p>\n\n\n\n<ul><li>Can use existing tools to deliver, but can also validate the tools&#8217; output, or even write better tools<\/li><li>Sees gaps in existing tools and either improves the tools, or changes methodology<\/li><li>Sees events on multiple levels of abstractions (f.ex. thanks to knowing protocols, knowing how org works, how malware works, how advanced authentication protocols work, etc. aka knows what happens &#8216;under the hood&#8217;)<\/li><li>Sees connections where others don&#8217;t<\/li><li>Actually reads the fucking manuals and RFCs<\/li><li>Experiments and &#8216;has itchy fingers&#8217;<\/li><\/ul>\n\n\n\n<p><\/p>\n\n\n\n<p>You are either technical, or you are not.<\/p>\n\n\n\n<p>What does it mean?<\/p>\n\n\n\n<p>You are technical when you are one upping yourself against the average of your peers&#8230; <\/p>\n\n\n\n<p>It&#8217;s not about knowing to program, reverse engineering code, analyzing packets, or discovering vulnerabilities. It&#8217;s about optimization, pioneering solutions, knowing the tools best for both their best and their worst, being inquisitive, finding out, then leading and sharing knowledge. It&#8217;s about not being an arsehole, but the waterhole. It&#8217;s about being the inspiration as much as being easy to be inspired. It&#8217;s not about being &#8216;technical&#8217; at all. It&#8217;s about spotting &#8216;more technical than you&#8217; and&#8230; following, raising the bar, challenging the status quo. <\/p>\n\n\n\n<p>A &#8216;technical&#8217; person is always a disruptor and a game changer. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>You are either technical, or you are not. What does it mean? Many tried to answer that borderline philosophical question, but as far as I know no one is really able to pin it down to specifics. This is because &hellip; <a href=\"https:\/\/www.hexacorn.com\/blog\/2022\/07\/22\/the-curse-of-being-technical\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[8],"tags":[],"_links":{"self":[{"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/posts\/8174"}],"collection":[{"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/comments?post=8174"}],"version-history":[{"count":4,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/posts\/8174\/revisions"}],"predecessor-version":[{"id":8178,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/posts\/8174\/revisions\/8178"}],"wp:attachment":[{"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/media?parent=8174"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/categories?post=8174"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/tags?post=8174"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}