Thermal infrared remote sensing has reached a turning point. A status audit completed for this review identifies 55 operational satellite platform deployments on 18 August 2026. The resulting dataset contains 174 named thermal infrared instrument designs mapped to 306 historical, operational and planned satellite platform deployments. Across the orbital record, the finest reported nominal spatial sampling decreased from 55 km for the Medium Resolution Infrared Radiometer aboard TIROS-2 in 1960 to 3.5 m for the mid-wave infrared imager aboard HotSat-2 in 2026, an improvement of more than four orders of magnitude. Public continuity missions are now complemented by specialized instruments on the International Space Station, commercial small satellites, aircraft, stratospheric balloons, drones and terrestrial systems. This review links that platform history to the governing physics of emitted radiation, detector and cooling technologies, calibration, atmospheric effects, emissivity and spatial resolution. It also examines the transition from classical machine learning to convolutional, recurrent, transformer, diffusion, foundation and vision–language approaches. The selected examples indicate that adoption in thermal applications has been uneven rather than uniformly delayed relative to other areas of Earth observation. These methods support image interpretation and reconstruction as well as quantitative retrieval, for which radiometric calibration, physical consistency and independent validation remain necessary. As sensor availability expands, scientific comparability increasingly depends on harmonization, cross-sensor transfer, uncertainty characterization and validation in physical units. We recommend three priorities: (i) open, cross-calibrated thermal archives; (ii) models that preserve the distinct physical meanings of thermal variables; and (iii) validation across sensors, regions and seasons using physical units, independent observations and quantified uncertainty.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors, and shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context.
Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al.· Journal of Systems and Softw...· 78 citations· ⚡6
The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.
Marko Ikonen, Petri Kettunen, Nilay V. Oza et al.· EUROMICRO Conference on Soft...· 67 citations· ⚡9
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.