Help
RSS
API
Feed
Maltego
Contact
Domain > midcareerdeveloper.com
×
Welcome!
Right click nodes and scroll the mouse to navigate the graph.
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2025-09-25
3.5.85.245
(
ClassC
)
2026-01-18
52.92.132.83
(
ClassC
)
Port 80
HTTP/1.1 200 OKx-amz-id-2: LRNTN7V6l4kPQOu2b30guxL+lSH5m+67lNdtFXxMwJy4tJxKSUkmICNLYMgeOqZU7JKuwVDfSmcx-amz-request-id: YTF22Y4GSYK950DSDate: Sun, 18 Jan 2026 04:55:24 GMTLast-Modified: Mon, 28 Jan 2019 21:33:48 GMTETag: eaa4d975242b1075b1cedcd7b36a639bContent-Type: text/htmlContent-Length: 29232Server: AmazonS3 !DOCTYPE html>html>head>meta namegenerator contentHexo 3.8.0> meta charsetutf-8> title>Mid-Career Developer/title> meta nameviewport contentwidthdevice-width, initial-scale1, maximum-scale1> meta namedescription contentMy development career to date, my current development career, and my future development career>meta namekeywords contentdeveloper, agile, tdd, career, software engineer, leadership, mentor>meta propertyog:type contentwebsite>meta propertyog:title contentMid-Career Developer>meta propertyog:url contenthttp://midcareerdeveloper.com/index.html>meta propertyog:site_name contentMid-Career Developer>meta propertyog:description contentMy development career to date, my current development career, and my future development career>meta propertyog:locale contenten>meta nametwitter:card contentsummary>meta nametwitter:title contentMid-Career Developer>meta nametwitter:description contentMy development career to date, my current development career, and my future development career> link relalternate href/atom.xml titleMid-Career Developer typeapplication/atom+xml> link relicon href/favicon.png> link href//fonts.googleapis.com/css?familySource+Code+Pro relstylesheet typetext/css> link relstylesheet href/css/style.css>/head>/html>body> div idcontainer> div idwrap> header idheader> div idbanner>/div> div idheader-outer classouter> div idheader-title classinner> h1 idlogo-wrap> a href/ idlogo>Mid-Career Developer/a> /h1> h2 idsubtitle-wrap> a href/ idsubtitle>From intern to team lead and beyond/a> /h2> /div> div idheader-inner classinner> nav idmain-nav> a idmain-nav-toggle classnav-icon>/a> a classmain-nav-link href/>Home/a> a classmain-nav-link href/archives>Archives/a> a classmain-nav-link href/contact>Contact/a> /nav> nav idsub-nav> a idnav-rss-link classnav-icon href/atom.xml titleRSS Feed>/a> a idnav-search-btn classnav-icon titleSearch>/a> /nav> div idsearch-form-wrap> form action//google.com/search methodget accept-charsetUTF-8 classsearch-form>input typesearch nameq classsearch-form-input placeholderSearch>button typesubmit classsearch-form-submit>/button>input typehidden namesitesearch valuehttp://midcareerdeveloper.com>/form> /div> /div> /div>/header> div classouter> section idmain> article idpost-Iteration-0 classarticle article-type-post itemscope itempropblogPost> div classarticle-meta> a href/2019/01/21/Iteration-0/ classarticle-date> time datetime2019-01-22T00:15:38.000Z itempropdatePublished>2019-01-21/time>/a> /div> div classarticle-inner> header classarticle-header> h1 itempropname> a classarticle-title href/2019/01/21/Iteration-0/>Iteration 0/a> /h1> /header> div classarticle-entry itemproparticleBody> p>We know what it takes to succeed. We need to set ourselves up to succeed. We do this by creating a plan and getting ready to execute. This is iteration 0./p>p>What should we be doing? On the project management side, we need to determine lines of communication, time lines, user stories, outstanding unknowns, feedback, risk, risk mitigation, and the medium of communication. There’s a lot to do./p>p>strong>Lines of communication/strong>br>Why is that important? Simple. If there’s a question. Who answers it? If there’s a problem. Who needs to know (people don’t like surprises), and who can help with a solution? Who are you celebrating your successes with? This is important, especially in long term projects. Without celebrating successes (even minor ones) a project becomes a grind. And when are these successes being celebrated?/p>p>strong>Time lines/strong>br>Is this project going to take a week? Month? Year? Decade? The overhead associated with a week long project is much less than a decade long project. What if one stakeholder sees the time line as a month and another sees it as many months. See the issue there? Most likely different expectations. Talk them out. Where did the month long time line come from? Where did the multi-month long time line come from? Maybe the user stories are not well understood?/p>p>strong>User storiessup>a href#orwhateveryoucallthem>*/a>/sup> are important/strong>br>Collectively, they are what needs to be done to succeed. Individually, they’re a short simple description of a feature without all the required details. Purposefully. They’re meant to be an input to a conversation rather than an output. The level of details discussed depends on when the story will be worked on. Next week? All details needed to work a story to it’s done state. Sometime in the project cycle? High level details. Why? Because projects tend to start with a lot of unknowns./p>p>strong>Outstanding unknowns/strong>br>How many pictures are we working with? I don’t know. What file extensions are we working with? I don’t know. Do the answers to these questions matter? Yes. Do they matter immediately? Probably not. At this stage it’s more important to make the unknowns visible to avoid surprises later. Why not spend time answering them right now? Answering these questions is making a decision. Maybe there isn’t enough information to make a decision yet. Always leave the decision making to the last responsible moment. Why? Because the unknowns might not need to become know. Don’t waste effort on anything that doesn’t need to be done. Any story can be dropped, re-prioritized, and adjusted according to feedback./p>p>strong>Feedback/strong>br>How is feedback addressed? Do not ignore. Ignoring feedback is dangerous. Stakeholders can feel marginalized when their feedback is ignored. Marginalization leads to distrust. Distrust leads to micromanaging, fear, and apathy. Plus, the wrong thing might be being built. Always address and discuss feedback. Hopefully immediately but that’s not always feasible. Address feedback as soon as feasible. Properly address. “I’ll get back to you” is an acknowledgment not an addressment. Fast feedback also helps deal with risks./p>p>strong>Risks/strong>br>A risk is anything that can derail the solution to your problem. Schedule risks, assumption risks, information risks, safety risks, resource risks, security risks, the list goes on and on. But don’t let risks discourage. Discuss them. Discuss how likely they are to occur. Discuss how you can lesson the impact of the risk (should it occur). The outputs of these discussions are used to decide what, if anything, needs to be done about the risks. Keep the risk discussions. Revisit them often. Make sure everyone knows where to find them./p>p>strong>Communication mediums/strong>br>How is all this information being stored? Where can individuals go to access this information? How is it organized? As long as there’s a general consensus, the actual medium itself doesn’t matter. Use stickies. Use an on-line tool with thousands of features. Use something in between. What really matters is that there is one and everyone knows what it is./p>p>Daunting? Shouldn’t be. For most projects, most of the foundation can be setup in under an hour. User stories are generally the long pole in the tent. But don’t let that stop you from setting the project up for success. The picture cleanup project needs to succeed so:/p>p>strong>Lines of communication/strong>br>Easy. One person on the task. One person to go to for everything./p>p>strong>Time lines/strong>br>The mountains are getting a lot of snow. The weekend crowds will ski out the good fresh powder. Sets a time line of 2 days (an arbitrary deadline from an external source adds authenticity)/p>p>strong>User stories/strong>br>The user story workshop held beside my coffee maker this morning with my dog and I produced the following output:/p>ul>li>As a photo pack rat (PPR), I can remove duplicate photos from my local computer so I can upload all my photos to the cloud and use the least amount of space./li>li>As a PPR, I can provide a directory to start searching for photos/li>li>As a PPR, I can choose what photo types to look at/li>li>As a PPR, I am shown a list of duplicate photos/li>li>As a PPR, I am shown a list of remaining photos/li>li>As a PPR, I am given the option of keeping duplicates so that I can keep my reputation as a PPR/li>/ul>p>Important to note: /p>ul>li>This list is not exhaustive. Work will be discovered as the project progresses./li>li>Some of these might never get worked on. /li>li>Some will get deleted./li>li>Some will get contradicted as more work is discovered./li>/ul>p>And that’s okay. em>Being flexible and adaptable breeds success./em>/p>p>strong>Outstanding unknowns./strong>br>None. Important to explicitly state rather than skip. Prevents future readers from asking em>“Were unknowns forgotten or were there none?”/em>/p>p>strong>Feedback/strong>br>Passing tests will be the main source of feedback. Disk space saved will be another source of feedback. Code self-reviewing will be used, but not relied upon./p>p>strong>Risks/strong>br>While this is a small project, it is not without a bit of risk./p>ol>li>I delete all photos on my computer.ul>li>em>Mitigation strategy:/em> Use tests to give high degree of confidence/li>li>em>Mitigation strategy:/em> Rename rather than delete (rename should identify where original came from)./li>li>em>Mitigation strategy:/em> Exploratory test on a small subset to gain even higher confidence./li>/ul>/li>li>I win the lottery and decide to stop work. ul>li>em>Mitigation strategy:/em> Don’t buy a lottery ticket/li>/ul>/li>/ol>p>strong>Communication mediums./strong>br>Paper scattered on my desk. Stickies on my monitors./p>p>Great. The project has been setup for success. Unless there’s something missing. Metrics? Maybe. They’re important but something bigger is missing. Right. The technical side. That should be next to setup for success …/p>p>a nameorwhateveryoucallthem>*/a> A rose by any other name/p> /div> footer classarticle-footer> a data-urlhttp://midcareerdeveloper.com/2019/01/21/Iteration-0/ data-idcjrgunsux0006o0fo4m8ixyu0 classarticle-share-link>Share/a> ul classarticle-tag-list>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Agile-project/>Agile project/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Iteration-0/>Iteration 0/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Picture-Cleanup/>Picture Cleanup/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Succeed/>Succeed/a>/li>/ul> /footer> /div> /article> article idpost-Starting-off-right classarticle article-type-post itemscope itempropblogPost> div classarticle-meta> a href/2018/12/14/Starting-off-right/ classarticle-date> time datetime2018-12-14T22:45:14.000Z itempropdatePublished>2018-12-14/time>/a> /div> div classarticle-inner> header classarticle-header> h1 itempropname> a classarticle-title href/2018/12/14/Starting-off-right/>Starting off right/a> /h1> /header> div classarticle-entry itemproparticleBody> p>We need to set ourselves up for success. To succeed, we need to know what it means to succeed. That’s the starting point. Define success. Not a simple task so let’s start with the problem statement and see where that goes./p>p>strong>Problem:/strong> Duplicate photos take up space/p>p>Thoughts? Questions? Good. The problem is vague. There are many solutions to the above problem. For instance, a few that quickly came to mind:/p>ol>li>Buy and install a new hard drive/li>li>Buy more cloud space/li>li>Delete all duplicate photos/li>li>Do nothing (are duplicate photos really a problem?)/li>/ol>p>Each solution is different. There are pros and cons to each one. The correct solution cannot be determined without asking questions and verbalizing thoughts. This is where the team discussion should occur. The goal of the discussion is to clarify the problem and create a shared understanding. This particular project is being done by a team of 1, but the discussion took place nonetheless./p>ul>li>strong>Q./strong> Can I buy a new hard drive?br>strong>A./strong> Yes, but then I’ll just have more files I can’t sort through/li>/ul>p>A simple question with a simple answer, but the answer gives us more than a first glance reveals. em>more files I can’t sort through/em> is the key phrase. The answer gives a clue about what is important about duplicate photos taking up space. Sorting photos is difficult with a lot of duplicates. That’s fair. But /p>ul>li>strong>Q./strong> Why is “duplicate photos taking up space” an issue?br>strong>A./strong> It makes my backup strategy difficult. I never know if I’ve uploaded a photo to the cloud or not/li>li>strong>Q./strong> So the problem isn’t really that duplicates take up too much space, it’s that you only want to upload one instance of a photo to the cloud for backup?br>strong>A./strong> Yes, I want to switch to a lower storage tier to save a little bit of money./li>li>strong>Q./strong> Can the duplicate photos be deleted?br>strong>A./strong> Yes, I don’t see why not./li>li>strong>Q./strong> On your local computer or in the cloud or both?br>strong>A./strong> Ideally I’d want the cloud to alert me when I was uploading a duplicate file, but we don’t control that. How about just delete the duplicates on the local computer, and we can discuss a solution for the cloud problem later. Maybe I’ll just start a new cloud account and upload all my photos once the duplicates have been removed./li>/ul>p>Perfect. Now rephrase the problem and present to the group./p>p>strong>Problem:/strong> There are duplicate photo files on my local computer that need to be removed so that I can upload all my photos to the cloud at once and use the least amount of space necessary./p>p>Great. That can be done. The success criteria for the project has also been implicitly defined with this problem statement. If all duplicate photos have been deleted from the local computer, success has been achieved./p>p>Remember this success criteria. Discuss it often. Revisit if necessary. Projects that lose sight of (or never have) success criteria will fail. They fail because there is no clear target. Create a target, create success criteria./p>p>Now that we know what it means to succeed, let’s move onto the next step./p>p>Side question for later: What would have happened if we immediately dove into one of the 4 solutions from above?/p> /div> footer classarticle-footer> a data-urlhttp://midcareerdeveloper.com/2018/12/14/Starting-off-right/ data-idcjrgunsuy0007o0folofklany classarticle-share-link>Share/a> ul classarticle-tag-list>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Agile-project/>Agile project/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Iteration-0/>Iteration 0/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Picture-Cleanup/>Picture Cleanup/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Project-planning/>Project planning/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Success-criteria/>Success criteria/a>/li>/ul> /footer> /div> /article> article idpost-A-project-begins classarticle article-type-post itemscope itempropblogPost> div classarticle-meta> a href/2018/12/07/A-project-begins/ classarticle-date> time datetime2018-12-07T20:06:29.000Z itempropdatePublished>2018-12-07/time>/a> /div> div classarticle-inner> header classarticle-header> h1 itempropname> a classarticle-title href/2018/12/07/A-project-begins/>A project begins/a> /h1> /header> div classarticle-entry itemproparticleBody> p>Photos are fun. Easy to take. Easy to look through. Easy to store. Storage is so easy that I just import everything into a directory and sort them later. Two issues with that:/p>ol>li>I never actually sort them later/li>li>I’ve imported the same photos many times/li>/ol>p>Now I know there are picture management apps out there to solve my problems, but I also need a project to work on. I also know problem #2 could be solved with a quick python script. But let’s indulge a little and take the chance to explore deeper. Deep into my realm of expertise:/p>img src/2018/12/07/A-project-begins/MindMap.JPG classcenter width300 height300>p>Not legible? That’s okay. Legible printing is not an area of expertise. It’s a mind map I created after meeting with a “career transition specialist”. An interesting exercise with interesting results. The map tells me I believe I have a diverse skill set. The map tells you that I strong>think/strong> I have a diverse skill set. The map doesn’t prove to you I have the skills I believe I possess. To prove I have the skills, I’ll have to show you. How? By cleaning up the pictures on my computer. /p>p>Let’s begin a hrefhttps://github.com/seanbrown888/PicCleanup relexternal nofollow noopener noreferrer target_blank>Picture Cleanup/a>/p> /div> footer classarticle-footer> a data-urlhttp://midcareerdeveloper.com/2018/12/07/A-project-begins/ data-idcjrgunsuf0000o0fojg0g6lvl classarticle-share-link>Share/a> ul classarticle-tag-list>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Agile-project/>Agile project/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Mind-map/>Mind map/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Picture-Cleanup/>Picture Cleanup/a>/li>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Prove-it/>Prove it/a>/li>/ul> /footer> /div> /article> article idpost-I-got-fat classarticle article-type-post itemscope itempropblogPost> div classarticle-meta> a href/2018/12/04/I-got-fat/ classarticle-date> time datetime2018-12-04T18:52:33.000Z itempropdatePublished>2018-12-04/time>/a> /div> div classarticle-inner> header classarticle-header> h1 itempropname> a classarticle-title href/2018/12/04/I-got-fat/>I got fat/a> /h1> /header> div classarticle-entry itemproparticleBody> p>42 minutes. My fastest 10km run. /p>p>26 minutes. My current 5km run. That should mean my current 10km time is roughly 52 minutes. But that’s not how it works. I’d be lucky to make it to 7km before I had to stop at a bench and “bird watch” for a while. What happened?/p>p>For starters, I got older. Time caught up to me. Injuries started to slow me down. Additionally, demands on my time caught up to me. I had to prioritize. Do the dishes or go for a run? Take the dog for a walksup>a href#dogwalksinstead>*/a>/sup> or go for a run? Spend some quiet time with my wife after the kids go to bed or go for a run?/p>p>I prioritized based on my constraints and desires, weighed those against the trade offs, and here I am./p>p>But the kids are getting older. They generally sleep through the night and are getting better at going to bed. They can even play amongst themselves for a short period of time. My constraints are changing and if I so desire, I could bring my 10km time down. I just need to hit the gym. Muscle memory is powerful./p>hr>p>Have you ever tried to calculate the longest increasing subsequence in an array? I have. I used to be able to rattle off a fairly good dynamic programming solution and with patience and thought, optimize to a more ideal solution. But I haven’t used those muscles in a long time. They atrophied. And that’s putting it nicely./p>p>As my career progressed, the demands and responsibilities of my job changed. I wasn’t responsible for writing algorithms. That was delegated. I was responsible for my team performing. Responsible for making my team (and the individuals of the team) better. Responsible for ensuring my team produced what was needed, was safe, maintainable, and met our standards. As my career progressed, the problems got different, but they didn’t get easier. They involved people. They involved business cases. They involved the greater vision. The scope was larger. I wasn’t responsible for optimizing an individual piece of code, I was responsible for helping optimize the whole. /p>p>And the algorithms fell to the wayside./p>hr>p>In the last month, I’ve hit the gym./p>img src/2018/12/04/I-got-fat/introToAlgo.jpg titleServes a dual purpose>p>Muscle memory is indeed powerful. I’ve lost a few steps but my goal isn’t to become a master algorithmersup>a href#itsprobablyaword>**/a>/sup>. I’m simply going back to the basics and keeping my mind in the right space./p>p>But discussing algorithms is not my goal here. There are plenty of sources out there telling you how to optimize an algorithm. Don’t get me wrong, I will still write about the exercises I’m doing, because I still love discussing the gritty details. /p>p>My goal here is to discuss how to grow and transition from optimizing an algorithm to optimizing the whole and (hopefully) where to go next./p>p>a namedogwalksinstead>*/a> My dog used to run with me, but she also got older and now prefers a nice long leisurely walk.br>a nameitsprobablyaword>**/a> Not a word but I like it/p> /div> footer classarticle-footer> a data-urlhttp://midcareerdeveloper.com/2018/12/04/I-got-fat/ data-idcjrgunsun0002o0folukrgs1d classarticle-share-link>Share/a> /footer> /div> /article> article idpost-It-Begins-Again classarticle article-type-post itemscope itempropblogPost> div classarticle-meta> a href/2018/11/30/It-Begins-Again/ classarticle-date> time datetime2018-11-30T15:57:53.000Z itempropdatePublished>2018-11-30/time>/a> /div> div classarticle-inner> header classarticle-header> h1 itempropname> a classarticle-title href/2018/11/30/It-Begins-Again/>It Begins Again/a> /h1> /header> div classarticle-entry itemproparticleBody> p>15 years was a long time. /p>p>I knew something was going on that day. There were rumors and whispers. The rumors became reality when I was pulled into a quick private meeting. The words were indirect: “For business reasons we are separating from your employment”. The shock was direct: I was just laid off. /p>p>I went home, had lunch, and zoned out with the TV. Sometime during my second episode of em>House of Cards/em> it donned on me: /p>p>strong>I need to figure out what’s next/strong>/p>p>That’s a very scary realization, yet very liberating. For the first time since I graduated university, I get to choose where I go next. Now I realize that choice has always been available. But with a family, decent income, and challenging projects to work on, there was never anything pushing me to take that leap./p>p>strong>And then I got pushed/strong>/p>p>In the month I’ve had off I’ve had a lot of time to reflect. My dog has gotten a lot of exercise and I’m averaging 13,000 steps a day. During that time this is what I’ve realized. I enjoy solving problems. Coding problems. People problems. Business problems. Doesn’t really matter. This realization directly lines up with my career path thus far. Unfortunately (something else I realized), I wasn’t self-aware as I walked my career path. Luckily my unconscious had my back and took me where I should have gone. /p>p>strong>But it’s time to be a little more deliberate/strong>/p>p>Deliberate in where I’m going means knowing where I want to go. And therein lies the problem. Where do I want to go? That’s a good question, and one that I hope to answer soon. Since I consider myself a pragmatic agile practitioner, I’m going to rephrase the problem:/p>p>strong>As an adult, I need to provide for my family./strong>/p>p>A user story. A bit of an epic. Add in a few constraints: /p>ul>li>I need to enjoy what I’m doing/li>li>I need to spend the time with my family that I want/li>li>I need to afford the quality of life that my family wants /li>/ul>p>And I’ve got a starting point. Perfect. Time to get started./p> /div> footer classarticle-footer> a data-urlhttp://midcareerdeveloper.com/2018/11/30/It-Begins-Again/ data-idcjrgunsuu0005o0foc50cdbtg classarticle-share-link>Share/a> ul classarticle-tag-list>li classarticle-tag-list-item>a classarticle-tag-list-link href/tags/Agile-beginning/>Agile beginning/a>/li>/ul> /footer> /div> /article> /section> aside idsidebar> div classwidget-wrap> h3 classwidget-title> Projects on Github /h3> div classwidget> ul> li> a classlevel is-mobile hrefhttps://github.com/seanbrown888/PicCleanup target_blank> span classlevel-right> span classlevel-item tag>Picture Cleanup/span> /span> /a> /li> /ul> /div>/div> div classwidget-wrap> h3 classwidget-title>Categories/h3> div classwidget> ul classcategory-list>li classcategory-list-item>a classcategory-list-link href/categories/Projects/>Projects/a>/li>li classcategory-list-item>a classcategory-list-link href/categories/Ramblings/>Ramblings/a>/li>/ul> /div> /div> div classwidget-wrap> h3 classwidget-title>Tags/h3> div classwidget> ul classtag-list>li classtag-list-item>a classtag-list-link href/tags/Agile-beginning/>Agile beginning/a>/li>li classtag-list-item>a classtag-list-link href/tags/Agile-project/>Agile project/a>/li>li classtag-list-item>a classtag-list-link href/tags/Iteration-0/>Iteration 0/a>/li>li classtag-list-item>a classtag-list-link href/tags/Mind-map/>Mind map/a>/li>li classtag-list-item>a classtag-list-link href/tags/Picture-Cleanup/>Picture Cleanup/a>/li>li classtag-list-item>a classtag-list-link href/tags/Project-planning/>Project planning/a>/li>li classtag-list-item>a classtag-list-link href/tags/Prove-it/>Prove it/a>/li>li classtag-list-item>a classtag-list-link href/tags/Succeed/>Succeed/a>/li>li classtag-list-item>a classtag-list-link href/tags/Success-criteria/>Success criteria/a>/li>/ul> /div> /div> /aside> /div> footer idfooter> div classouter> div idfooter-info classinner> © 2019 Sean Brownbr> Powered by a hrefhttp://hexo.io/ target_blank>Hexo/a> /div> /div>/footer> /div> nav idmobile-nav> a href/ classmobile-nav-link>Home/a> a href/archives classmobile-nav-link>Archives/a> a href/contact classmobile-nav-link>Contact/a> /nav> script src//ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js>/script> link relstylesheet href/fancybox/jquery.fancybox.css> script src/fancybox/jquery.fancybox.pack.js>/script>script src/js/script.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
]