Software Engineer / SRE
I am a passionate woman fond of octopuses 🐙🐙 It took me a while to find my path, but as soon as I started programming, I knew it would define me for the rest of my life. I love everything that challenges my brain and can keep it interested. I was involved in projects in numerous domains, from quantum computing for particle physics to retail store interfaces. I don't know what I enjoy the most (as long as I can crunch code), so I try everything I come up with. Currently working as a software engineer / SRE, I always have ongoing side projects and try to give back to the community through open-source and tech platforms (dev.to, StackOverflow). Aside from my work, I love reading (especially time travel fiction) and spending time with other passionate people. To make the latter even easier, I co-founded the GDG Fribourg, which I hope you will check out if you are in Switzerland.
Markdown supported · ⌘↵ to post
Very interesting!
I have started to massively use type hints in 2023 (after almost 11 years of coding with Python). I couldn't agree more with these 2 sentences:
a Python project should be developed with type checks in mind from the start
and:
I can't help but feel the types revolution will drastically change how we code in Python
I am still using the integrated feature of PyCharm for checking type hints. I haven't tried MyPy yet, but I will try one day!
Attila Gulyas
This is great writing: It's
To think that I almost gave up my research before stumbling upon this article.. Thank you!
(Thank you also for saving us at least a month! Inherited a legacy (undocumented) Django 2 project running in production, and bringing it up to date took almost 2 weeks, so we were thinking about adding static type checking. After reading your thorough write-up though, I think we should be happy that the upgrade and subsequent migration went well..:)