112 karma · joined July 10, 2014
.NET Standard is a standard that the 3 different implementations of .NET try implement (.NET, .NET Core and Mono). Any implementation of .NET Standard can add in extra functionality, hence superset, it's a bit silly.
.NETFX = .net framework.
their naming is a mess.
However other times things like browsers do dumb stuff:
docx files and silverlight files are both just zip files with completely different structures meaning they can live together in the same file.
IE used to look at txt files that contained html tags and say hmm maybe i should display that as html
that meant on sites that accepted txt and docx uploads (a lot of recruitment sites etc) you could upload a txt file that simply embed the docx as a silverlight component. When the admin looked at the txt file it would run the code as the currently logged in (admin) user.
It does sound like you've never worked with a good PM, I'm not sure if I have either as I do struggle a lot with what value they actually add to projects.
99% of the time its better for people to speak directly and not relay information through other (probably non technical) people.
Of course you do need to limit distractions but I think you can set expectations with people about what distractions do and how often they should distract you.
Also find that a lot of PMs try play power games, I really think they need a new job title like Project Coordinator or something that sounds a little less in charge.
Interesting to see this thread has a very mixed idea of what a PM is, a number of people mention things I'd expect as part of a sales or BA role. I wonder if this is part of the reason people find PMs useless is that no one really knows what they should be doing.
It basically boils down to Leave things tidier than when you arrived.
No massive refactor projects, just fix up little things when you're in the area. Sure you never end up with a particularly nice codebase but it's not getting worse and it's not costing the business massive amounts to make something prettier for little benefit.
Also works well with backlogs, especially for client projects, you want a new feature? what are you willing to drop off the backlog to get it?
It's generally well known that most products contain a crap tonne of unused features and removing them reduces technical debt (eg potential bugs, overweight/slow apps).
I don't see it as a hard rule to sell in software.
Maybe just a personal thing.
note: i've changed your example to show code inside html tags, i'm aware it does something different to yours.
conditionals
<div>
@if(cond1 && cond2) {
<div>foo</div>
}
</div>
loops <div>
@for(var i in collection) {
<div></div>
}
</div>
variables <div>
@variable
</div>
ternary/longer statement <div>
@(variable ? 1 : 2)
</div>What I like about linq/EF is that it doesn't force you into other anti patterns (active record, repository etc) but that's probably just a matter of opinion.
for(var i = 1; i <= 100; i++) {
a[fizz +=3] = "fizz" + (a[fizz] || "");
a[buzz +=5] = "buzz";
print(a[i] || i);
}Rewriting code that works and doesn't need new features is pure waste.
Used some google and found a stackexchange answer that I thought was clearer
https://stats.stackexchange.com/questions/165/how-would-you-...
jQuery basically already has support for this exact thing, and it's only a few lines of pure JS.
$.extend({a:'b', b:2, c: [1,2]}, { a: null, b: 0})