Joined devRant on 6/25/2017
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
96 build errors?
When I refactor I often get more than a thousand 🤣
There is no such thing as a perfect IDE. I too have spent entire days damning VS to hell, but in daily use it does it's job well. And there is no getting around the fact that if you want to do serious business, you use .Net, and if you use .Net, you use Visual Studio.
So just embrace it.
@steaksauce Same server. Good question though :-)
True. I'm just getting... flashbacks...
Me: 'Please, boss, nooo! Let me write a nice .Net program in stead of this foul mess from beyond the 9th circle of hell!'
Me: *strapping on the armor*
Here be dragons...
@jibberdev919 No offence taken, I understood what you were saying :-)
@jibberdev919 (and every acknowledged best practice guru's word of course ;-))
@jibberdev919 Yes, I worded it that way specifically because I do not have any statistics to support the claim. I do have 12 years of experience though :-)
@TobiSGD When using always using var, you have these three situations:
1. The type is obvious from the right hand side of the declaration
2. The type is obvious from usage or context
3. The type is found with a very quick lookup (usually a mouse-hover)
So only in 1 of 3 situations do we need an extra step to know the type. And in that situation, you would most likely need a deeper understanding of the context anyway.
The cost of not using var, in terms of how much unnecessary extra reading is required by anyone looking at the code, I would say is higher than the cost of looking up the type in those few situations.
@TobiSGD When dealing with long type names, assuming audience 2 knows:
1. What var means
2. How to use the IDE or common sense to find the type
the code is more readable with var. Always.
If anyone in audience 2 does not know either 1 or 2, they need to be taught this. There is no shame in not knowing something, but there is in knowingly writing more verbose code because of a personal preference.
@TobiSGD Not utilizing the IDE or using common sense to figure out what the return type of an assignment is is a lot more stupid than cluttering up the code with redundant declarations.
MyClass myClass = new MyClass();
var myClass = new MyClass();
In the first statement, the MyClass type name on the left side of the declaration is redundant, since the right side also specifies the type. The second statement is shorter, and thus more readable. This is especially apparent when you have long or more convoluted types, like nested generics etc.
@TobiSGD You need a better IDE. Visual Studio tells me the type of a var 100% of the time. Using var is not lazy. It is best practice because it avoids redundancy.
I change any explicit declaration I see to var. If you don't like var, you don't understand it. By not writing out a verbose declaration, you will almost always make the code more condensed, less cluttered and thus more readable.
If you require an explicit declaration to understand the code, then you need to get better at understanding code in general.
Var does not mean dynamic. Var just means that you already declared the type on the right side of the statement, and doing it again would be redundant.
@gitpush I am out of poops to give
@electrineer I would send you photo evidence that the poop was, in fact, not small. But that would be in poop taste. I mean poor. I mean poop.
Sql is useful. Sql is necessary. But I wouldn't call it cool. As a C#-developer, I find it much easier to write complex logic in linq, as the sql equivalent is often very verbose.
If we could bridge the performance gap, in a .net world, we wouldn't need sql at all.
Not for everyone. But I love it :-)
Probably because I just CANNOT abide shitty, redandant, messy code.
@Pogromist It's well hidden ;-)
@Jilano Alright, I'll see what I find out :-)
The Melancholy of a Lovelorn Swede.
Fellow Scandinavian here - I'm Danish :-)
I write poems and songs; lately mostly songs. I find that actually creating something to express my feelings through has a therapeutic effect. Especially since I started putting my songs on youtube so I could get some feedback.
@pleuph Update: At least Avid support is fast. Per my request, they have now deleted my account :-)
They have asked me to take a survey on how they can improve themselves. I might just link to this rant 😅
BTW: I have now discovered that neither Avid nor iLok have ANY way to request an account deletion through their website. And iLok doesn't have any way to contact them at all, EXCEPT for an 'Order Inquiry'.
@RememberMe I will definitely try it :-)
@RememberMe Okay, sounds cool!
I do like trying out a lot of weird sounds, but right now I need a faster way to record my instruments and vocals.
@pleuph @RememberMe Oh. I see Reaper has loads of tutorials on their own site :-P
@RememberMe Thanks for the advice :-)
Pro Tools First smells an awful much like a very, very poor and misguided attempt to make a 'My First DAW'. They just don't get that you have to make something simple, yet flexible, if you want to appeal to amateurs.
I already know FL Studio, and I actually have it installed right now. However, I find it difficult to really try it out because of the weird limitations of the trial version.
I also know about Reaper, and I will definitely try it out. I had it installed a few years ago but found it hard to get started with. Can you recommend some good tutorials to get me started?
I am also eyeing Reason, but I don't know if a 30 day trial will be enough to get the hang of it with the limited time a day I have.
@dandrei279 Well, I didn't want to shamelessly promote myself, but here is the link if you really want it ;-)
@dandrei279 The video?
Yes. A thousand times yes!