Office Automation is problematic -- because it literally opens up a hidden window of your Office app and simulates clicking around the UI to do what you need, if something unexpected happens it can unhide the window to show the user a message. This might be good enough for a desktop app, but if you're running it on a server it'll just freeze up your process with noone there to click it.
For Office->PDF conversion of word docs, Aspose.Words has a fairly easy API and generally very accurate rendering. I highly recommend it.
At least on the C# side of things, the three libraries I've used (iTextSharp, PdfSharp, and Aspose.Pdf) are all a bit of an unintuitive mess with inconsistencies all over the place and very little documentation. In the case of iText, their revenue stream is putting all their documentation into a book for people to buy, so it's not uncommon to get an intentionally vague response when asking for help.
I cycle between each depending on what I need to do, because they all have their own quirks and supported features. I've even piped from one to another to get certain parts of the process working.
Bose and Beats are both highly brand-focused. Bose targets the more mature quality-seeking crowd, while Beats targets the bass-hungry and fashion-conscious youth. There's some overlap, but generally I'd say their targets kept competition to a minimum, and they've pretty much cornered those targets
Apple has the best of both worlds being viewed both as high quality and a status symbol. If they start using their monster marketing teams to align peoples' view of Beats with that of Apple, Bose stands a chance of being pushed out of the market by a frightening direct competition. They've got good reason to try to stall the acquisition as much as possible
If this order still stands, why hasn't the FCC fined practically every ISP under this rule?
It seems they've got quite a lot of bark, but not enough bite. Unless it comes to boobs on TV.
Meanwhile, the bank will take anything.
Really? I'm so used to "6-8 characters, no symbols, etc.". You'd think these things would be regulated.
Stack Overflow reputation indicates that you're a 1337 documentation writer, not necessarily that you know how to program.
SO reputation indicates a number of things -- that you can understand and dissect problems and code from others, that you have intimate knowledge of the platforms you're answering about, that you can code reasonably well, and that you can communicate well.
Basically, someone with a high rep is very likely to be enthusiastic, knowledgable, and great to work with. Does this mean Jon Skeet can out-code an elite like John Carmack? No. Does it mean he's a good coder? Probably. One of the "top" programmers? Not enough data.
This whole article is a bit of a bonkers idea. What makes a good dev? Is it the ability to work quickly, elegantly, and robustly? Being able to pull innovative algorithms out of thin air? Is it the ability to hack together important, complicated projects even if the code itself is a mess? How about less direct things, like overall contribution to the dev community and enthusiasm for helping other people grow?
I own a HDHomeRun, and it was a bitch to set up because even Comcast customer support had never heard of it (at one point, they told me to call TiVo!)
When was the last time you did this?
I've had a HDHomeRun Prime for about three years now, and have never had an issue with Comcast's CableCard activation line. The other side of the call is seated by a weird androgynously-voiced Indian following a script, but I've never been on the phone more than about 5 minutes before my card was working.
But some say he is less hands-on in developing products than his predecessor.
The best leaders will see their own shortcomings and delegate to trusted experts to pick up their slack. Perhaps this is Cook's strategy.
I think the best way we could handle it is to create a standard high-level bytecode and package format. Then any number of languages could be translated to it easily and efficiently.