3 ms·

I'm super embarrassed as a dotNet developer, at times 'engineer', that I don't know this.. I can't list how many time's I've ran into this kind of issue when t

I'm super embarrassed as a dotNet developer, at times 'engineer', that I don't know this.. I can't list how many time's I've ran into this kind of issue when trying to explain to a peer/intern.. (Only know I probably messed up a bit now) And HN links like this just remind me that I would love to take a 'bus mans holiday' just to catch up on the framework. This is a huge plus to the benefits of sending employees and me (please send me) to those release conferences. 'New dotNet Core coming ?' : I want to be there, but I have to live in Europe and not able to take holidays, so the stream is saved; I'll watch it later (I rarely do). :( Whatever about patterns and higher level issues, knowing the framework is also damn key important and often overlooked as a given. Really knowing the framework, all the way down to the compile time really offers some incredible results, I have been fortunate to work with some who really knew the framework versions that we were in and it was always so much fun to put bets on how much time that team would save from ours and other teams from even just a light refactor. Most important is that developers should know the framework, not because of high time savers, but so that nobody is re-writing the wheel (intentionally did not say : 'not reinventing') I wish I had the time to always dig through the release notes of the latest framework abilities, not to mention 'Core'.. I might bring this up as a task for the team, but does anyone genuinely have good suggestions on how to drill into fellow team mates that its important to check up on framework functionality.. I really feel kinda insulting to say: 'maybe google it to see if there is a simular issue that could shine a light?' God bless HN. Edit: ReSharper is my best colleague.. I'll copy an important note from below: >Note : I am not fighting against tools, just that sometimes, me included, the tools make us not go and search why resharper is screaming: 'you're an idiot'!

GordonS 7y ago
It's OK, C# is a living thing, don't feel bad! I'm guessing you use Visual Studio and don't have ReSharper? If so, I have 2 recommendations to make: 1. Get ReSharper! When it sees code that could benefit from language features, it will suggest it 2. Get JetBrains Rider - seriously, try it - it's an alternative IDE with all the ReSharper stuff built-in. I personally find it a better experience than Visual Studio, and it makes my laptop fans whine far less!
- bilekas 7y ago
  1) I do have resharper, I made a comment here about how it makes me lazy because it does it for me, and how I get nervous even jumping on a VS without it 2)Rider though.. It's new to me.. I'll certainly give it a go. But one of my main points was : 'Hey, we work with this language, we should know it' Get me ? Note : I am not fighting against tools, just that sometimes, me included, the tools make us not go and search why resharper is screaming: 'you're an idiot'!
- henrikschroder 7y ago
  Visual Studio also does code suggestions for when you can replace a pattern with a newer language construct. I suspect ReSharper is better at it, but I haven't tried VS2019 yet.
flatline 7y ago
Keeping a code base up to date is a cultural thing. Keep up to pace yourself. Suggest new features during code review. Encourage curiosity. Hire developers who are interested in technology, from diverse backgrounds. Be enthusiastic and evangelize about new things, it will inspire others even if you don’t realize it.
james_s_tayler 7y ago
Usually there are blog posts that do a good job at summarizing what's new in a given release. I find it helpful to read over them even when picking up a new language / framework to see how it has evolved over time.

GordonS 7y ago

It's OK, C# is a living thing, don't feel bad! I'm guessing you use Visual Studio and don't have ReSharper? If so, I have 2 recommendations to make: 1. Get ReSharper! When it sees code that could benefit from language features, it will suggest it 2. Get JetBrains Rider - seriously, try it - it's an alternative IDE with all the ReSharper stuff built-in. I personally find it a better experience than Visual Studio, and it makes my laptop fans whine far less!

bilekas 7y ago
1) I do have resharper, I made a comment here about how it makes me lazy because it does it for me, and how I get nervous even jumping on a VS without it 2)Rider though.. It's new to me.. I'll certainly give it a go. But one of my main points was : 'Hey, we work with this language, we should know it' Get me ? Note : I am not fighting against tools, just that sometimes, me included, the tools make us not go and search why resharper is screaming: 'you're an idiot'!
henrikschroder 7y ago
Visual Studio also does code suggestions for when you can replace a pattern with a newer language construct. I suspect ReSharper is better at it, but I haven't tried VS2019 yet.

flatline 7y ago

Keeping a code base up to date is a cultural thing. Keep up to pace yourself. Suggest new features during code review. Encourage curiosity. Hire developers who are interested in technology, from diverse backgrounds. Be enthusiastic and evangelize about new things, it will inspire others even if you don’t realize it.

james_s_tayler 7y ago

Usually there are blog posts that do a good job at summarizing what's new in a given release. I find it helpful to read over them even when picking up a new language / framework to see how it has evolved over time.