Domain > hannohinsch.com

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2019-10-08	52.219.105.36 (ClassC)
2019-10-17	52.219.101.21 (ClassC)
2019-10-20	52.219.105.4 (ClassC)
2019-10-24	52.219.97.28 (ClassC)
2024-05-17	52.219.176.240 (ClassC)
2024-05-30	16.12.65.224 (ClassC)
2024-06-09	52.219.109.104 (ClassC)
2024-09-13	52.219.177.96 (ClassC)
2024-10-08	52.219.105.44 (ClassC)
2024-12-26	52.219.178.32 (ClassC)
2024-12-30	3.5.128.3 (ClassC)
2025-01-12	3.5.128.14 (ClassC)
2025-01-22	52.219.110.64 (ClassC)
2025-06-06	16.12.64.240 (ClassC)
2025-07-03	3.5.128.113 (ClassC)
2025-07-11	3.5.128.118 (ClassC)
2025-09-06	3.5.131.223 (ClassC)
2025-09-19	52.219.178.88 (ClassC)
2025-12-14	52.219.93.168 (ClassC)
2026-03-07	3.5.130.176 (ClassC)

HTTP/1.1 200 OKx-amz-id-2: KmdQ7WTO7DiKMNh8lXRF8i16EeXZ9n4UWnNx1DV/uF7D5AGHP3UfWj/VhCTv23KfmHhvuxjp8qwx-amz-request-id: 4KTXDS4ZV31B71F6Date: Fri, 17 May 2024 23:15:47 GMTLast-Modified: Sat, 13 Jul 20

!DOCTYPE html>html langen-us>head>meta nameviewport contentwidthdevice-width, initial-scale1.0>link relstylesheet typetext/css hrefcommon.css />meta nameDescription contentHanno Hinsch - Notes on software development />title>soft.dev.etc/title>/head>body>www.hannohinsch.comh1 stylewhite-space:nowrap>soft.dev.etc/h1>p>/p>h2>Managing software development projects/h2>p>Back around 2005 I was thinking a lot about how to manage uncertainty in software development projects. This became a more popular topic a few years later, with pretty much everyone eventually converging on the same core ideas./p>ul>li>BDUF or incremental? UML, CRC cards or ...? For at least the last 40 years, software development methodologists have been arguing about when and how to design software. Examining the principles motivating software design helps make sense of the conflicting camps and choosing the right alternative. Seea hrefdesign.html>How much design?/a>/li>li>Strategically structuring a project is obviously important, but not much has been written about it. Given a long list of things that need to be done, how should the list be structured? What is the optimal order of tasks? On what basis do you decide what to do next? Seea hrefstructure.html>Structuring a Project/a>/li>li>Process development and improvement is a lot like software development: Just incrementally fixing whats broken works pretty well. See a hrefprocess.html>Process Improvement/a>/li>/ul>h2>Bioinformatics/h2>p>From my time at UPenn./p>ul>li>Free download: b>a hrefjavagene.html>JavaGene/a>/b> is a set of Java foundation classes for genomic sequence analysis you can learn to use in an afternoon. Its good for doing low level sequence manipulations -- just the thing for writing gene finders, analyzing gene structure, modeling molecular evolution and similar projects./li>li>a hrefhttp://www.biomedcentral.com/1471-2148/6/90>Recurring genomic breaks in independent lineages support genomic fragility/a>br />Hanno Hinsch and Sridhar Hannenhallibr />BMC Evolutionary Biology 2006,

View on OTX | View on ThreatMiner

Data with thanks to AlienVault OTX, VirusTotal, Malwr and others. [Sitemap]

Domain > hannohinsch.com

Is this malicious?

DNS Resolutions

Port 80