3 ms·
As someone who came from the Ruby/Rails stack to a C#/.NET MVC stack, I have to say it was eye opening. The stack has alot of bells and whistles and arguably be
by slackstation 11y ago
As someone who came from the Ruby/Rails stack to a C#/.NET MVC stack, I have to say it was eye opening. The stack has alot of bells and whistles and arguably benefits from the deep integration between the tools (Visual Studio) and the platform. I came in wanting to hate it and actively looking for things to bemoan but, it was rather a pleasant experience.
One last thing is the importance of writing code in a static/typed language. It allows you to write and build things in a different style. It changed how I looked at programming and once I had learned another paradigm, I became far more interested in others. It led me to functional programming which in turn led me back to Object Oriented Programming and reading a bit more deeply about the theory of architecture. It made realize that most of my career, I was either using someone else's architecture or just hacking together the bare minimum for the task at hand without any thought of how the system could change and grow over time.