Jyri Matti Lähteenmäki
About Jyri Matti Lähteenmäki
Jyri Matti Lähteenmäki is a Senior Software Designer at Solita, where he has worked since 2016. He has a background in software design and telecommunications, with a preference for static type systems and Haskell over dynamic languages.
Work at Solita
Jyri Matti Lähteenmäki has been employed at Solita since 2016, currently holding the position of Senior Software Designer. His tenure at Solita spans eight years, during which he has contributed to various software design projects. Prior to his current role, he worked at Solita in different capacities, including Software Designer from 2010 to 2016 and Junior Software Designer from 2007 to 2010. His extensive experience at Solita reflects a deep understanding of software design principles and practices.
Education and Expertise
Jyri Matti Lähteenmäki studied at Tampereen Ammattiopisto, where he achieved a Telecommunications engineer qualification and Matriculation from 1998 to 2002. He furthered his education at Tampere University of Technology from 2003 to 2010, earning a Master of Science degree with a focus on Computer Science, Hypermedia, and Physics. His educational background provides a strong foundation for his work in software design, particularly in advocating for sophisticated static type systems.
Background
Before his long-term association with Solita, Jyri Matti Lähteenmäki gained experience as a Summer Trainee at Metso Automation in 2006 for two months. This early exposure to the industry contributed to his development as a software designer. His career trajectory includes progressive roles at Solita, where he has built a comprehensive skill set in software design and development.
Technical Preferences and Perspectives
Jyri Matti Lähteenmäki expresses a strong preference for avoiding dynamic languages and Oracle products in his work. He has a critical view of technologies such as JavaScript, JavaEE, and JDK, indicating a belief that these may reflect a decline in industry standards. He advocates for the use of Haskell due to its type safety and structure, while also expressing skepticism towards Scala as a substitute for Haskell on the JVM. His nuanced perspective on Java suggests a preference for unconventional applications of the language.