(I wasn't really kidding, so many times I was looking at a program's code and at its behaviour being inexplicably different no matter how many times I'd try to nudge it, only to recognize that either I didn't save it or I was saving it to the wrong place.)
@TimStone could you please scream "I HAVE A FIX FOR THIS" when you, well, have a fix for something? This is the second time that after fixing an issue when going through dupes to find everything to tag [status-completed], I find an answer by you that had already debugged the issue
@YiJiang And I'm not sure whether they should be bolded or not. You could always put the tooltip text alongside the badges, that would fill up some space ;)
@YiJiang, and the more I think about it, the more I wonder whether there shouldn't be a disclaimer on the rep/post stat: "Note: this may include bounties"
I read the other day too that the Patent Office is trying to make good on its promise to reduce backlog by paying even less attention to the crap it passes. Meh.
They are doing a patent swap. A company can get one patent application looked at faster, if they drop another application that they have in the pipeline. That's how huge that backlog is.
I forked pyStackExchange to make my cloud tool out of it and found a bug with the library. I fixed it in one commit and so I'd like to pull request just that one
> What happened to the Ancient Egyptians? They invented flight, electricity, casinos in the desert shaped like pyramids, and then they started sharing cat videos with everyone. Thus began the stone age. Cat hieroglyphics were just an extension of those cat related videos when there was no more technology. Pass this along as a reminder to your friends that they don't need to follow the path of the Ancients. #CatVideos
SO Chat participation : rooms, posts, last seen
Meta Chat participation : rooms, posts, last seen
Include StackFlair?
Don't expose live version, just saved-as-html (in case of 'tricky' data)
Disclaimer on rep/post statistic
Meta 'last seen' date
@Moshe ok. I didn't figure you were anymore, I figured you lost interest in it, as most would've done. Just that I was downvoted rather maliciously so took a personal interest in it ;)
> Now comes the fun part, because executing a stored procedure that uses table-valued parameters is somewhat trickier than one might think. According to the documentation it should be possible to pass a System.Data.DataTable, System.Data.Common.DbDataReader or an object that derives from IEnumerable as the value of the table-valued parameter.
> Pretty neat, however only the first two options actually work. Jeroen (a colleague) and I have been breaking our brains on this one for quite some time and discovered that the documentation contains a rather nasty error.
> So the best option when using table-valued parameters is passing the data in the form of a datatable. It's a bit of overhead, but it gets the job done pretty well.
on the fly conversion of lists to datatables ... joy
is in an interesting mood. They just fired my QC woman because "they are downsizing". She's the single most valuable person here. What an utter shame. I'm really thinking about going in and telling him to fire me too because I'm going to go look for another job immediately if he keeps me on.
The amount and quality of work that she does. The amount of errors she saves from the client are astounding (that's why she's the most valuable, everyone else is an idiot, and she stops the client from finding out about it)
is just ranting. I'm so pissed right now that it's not even funny...
@ircmaxell Then it sounds like you need to take an early lunch and go for a drive, then go mull things over, then go talk to the wife, then go back to the office