|
|
|
|
|
|
by hakanderyal
1341 days ago
|
|
|
Agreed on all the points. Re: IDE, I see this as an advantage. As a lifelong user of editors (emacs, Sublime Text, VS Code) other than checking some IDE out here and there, I've committed to using an IDE (Rider) for the first time while working with C#. When the platform and the language you are using allows good IDE support (static typing and friends), the experience is leaps and bounds ahead of using an editor in a dynamically typed languages. I was also using all kinds of meta programming magic to bend Python to my will, so an IDE had nothing more to offer. I'm also employing the same ideas with C#, but this time they are encapsulated to a few input/output locations and supplemented by design-time code generation where possible, resulting in nearly everything is type safe. Now Rider can work as a partner, instead of being a hindrance. Always embrace the powers of the platform you are using. If it's a statically typed language, learn to work with the IDE, don't fight with it. |
|
|
Very much agree! For me as a big fan of IDEs for all my work, my biggest adjustments have been learning all the .Net specific things, how to do them in the otherwise familiar JetBrains Rider (I use PyCharm for my python work), and a slow acceptance that while there are ways to "work more explicitly" (fully specifying names and not touching the "using statements") the IDE does indeed have all the power it needs to understand what I cant see because of the powerful type system and all the .Net machinery under the hood that I don't yet know to the level of my deep python knowledge.