151–160 of 299 posts
I didn't see the word "legacy" technology used in the article, but I think a lot of the stuff in the weekday column is exactly what people associate with the word legacy. I mean soap and xslt !? That is straight from the darkest era of bloated J2EE apps.
The funnel shape of the scatter plot immediately reminded me of an article on the insensitivity to sample size pitfall [0], which points out that you'll expect entities with smaller sample sizes to show up more often in the extremes because of the higher variance. Looks like the tags with the biggest differences exemplify this pretty well. [0]- http://dataremixed.com/2015/01/avoiding-data-pitfalls-part-2...
Can you normalise data like that based on a confidence interval? Just rescaling the graph to unify them seems wrong, (it would answer something like "what do we think the distribution would look like if we distrusted the low end?") but maybe there's a better way?
Using an (empirical) Bayesian multilevel model can both attach uncertainty intervals to the point estimates and appropriately "shrink" the estimates towards zero at the low-sample-size end.
The latter is more directly interpretable, at the cost of slightly more complex modelling (/assumptions).
> We defined weekends using UTC dates... ...which means quite a few Saturday mornings in Asia have been counted as weekdays and many late Friday nights in the Americas have been counted as weekends. It would be great if StackOverflow had information on the local timezone that the question was asked in. Seeing Mon-Fri 9-5 vs other times would be interesting.
Earlier quoted context omitted.
I was expecting to see Rust - I thought it was a considerably 'hotter' language than reflected by its current use in the wild. Also, I find SO's coverage of it lacking. So maybe it's more about people sourcing the information elsewhere - relatively good docs, active and helpful community in IRC, and more Q&A on Reddit (albeit mostly - again, anecdotally - out of date, but still) than SO.
> I was expecting to see Rust - I thought it was a considerably 'hotter' language than reflected by its current use in the wild. Rust is pretty hot on Hacker News and r/programming, but even working in a systems-language-heavy field, I haven't seen too much mindshare (outside of some friends at Mozilla). It is kind of a shame, both Rust and D are doing really cool things, and I'd love to see more penetration!
https://www.rust-lang.org/en-US/friends.html has very many non-Mozilla organizations :)
I didn't see the word "legacy" technology used in the article, but I think a lot of the stuff in the weekday column is exactly what people associate with the word legacy. I mean soap and xslt !? That is straight from the darkest era of bloated J2EE apps.
Actually back in the day, it was Microsoft who was pushing SOAP the hardest. Don Box, one of SOAP's creators, is a "technical fellow" at Microsoft. This is the same guy who coined the term "COM is love". Dark days indeed.
Earlier quoted context omitted.
Sharepoint should have been a great product for small to medium businesses, as well as government departments but yeah, it had horrible, horrible implementation and deployment issues. How I wish it had less .Net centricity and more adaptability to build or consume services in other languages and protocols - it could have been a killer business platform...
Even when you know .net it still feels alien. When it comes to custom development it's much easier to create an app from scratch than it is to integrate with sharepoint.
Microsoft should really take note of that. That's a huge tick on their woefully uncool meter. Developers, developers, developers, developers don't want to use Microsoft gear unless they're being paid, it would seem.
Earlier quoted context omitted.
Can you normalise data like that based on a confidence interval? Just rescaling the graph to unify them seems wrong, (it would answer something like "what do we think the distribution would look like if we distrusted the low end?") but maybe there's a better way?
A confidence interval won't adjust the points (point estimates) but will give those points with a lower sample size wide confidence intervals (often covering zero). Using an (empirical) Bayesian multilevel model can both attach uncertainty intervals to the point estimates and appropriately "shrink" the estimates towards zero at the low-sample-size end. The latter is more directly interpretable, at the cost of slightl…
Looking for explanation of multilevel model, I found http://mc-stan.org/documentation/case-studies/radon.html which seems to do exactly that in "Partial pooling model". (see graph)
Earlier quoted context omitted.
Even when you know .net it still feels alien. When it comes to custom development it's much easier to create an app from scratch than it is to integrate with sharepoint.
Unfortunately, when you move on to another job, your "much easier" app becomes an orphan. I have seem this happen multiple times. The hot shot developer creates his own thing because it is too much of a hassle to do in SharePoint. Then the developer moves on. And the "much easier" app slides into a slow decline and one day dies because nobody know how to fix it.